Scoped Memory Manager
Security checks across malware telemetry and agentic risk
Overview
The skill is coherent, but it sets up a recurring background agent that can read logs and rewrite or prune persistent agent memory without an explicit review or rollback step.
Only install this if you want automated memory maintenance. Before enabling the cron job, confirm where memory logs are stored, require review before changes are written, keep backups of MEMORY.md and memory/topics files, and make sure you know how to disable the scheduled job.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
After installation, the agent may continue running weekly memory-maintenance tasks and change what future agents remember or forget.
This establishes recurring autonomous agent activity that persists beyond the initial setup and can change memory files. It is disclosed and purpose-aligned, but no approval, disable, backup, or rollback control is specified.
Automated REM Sleep: A scheduled background job (cron) that wakes up an isolated agent to compress daily logs, extract new patterns, prune outdated "trauma" constraints, and file the distilled knowledge into the correct topic files.
Require explicit opt-in for the cron job, show proposed memory changes before writing them, keep backups, and document how to pause or remove the scheduled job.
Incorrect, sensitive, or maliciously influenced log content could become long-lived agent memory, while useful constraints could be deleted.
The skill promotes content from logs into persistent memory and removes or rewrites existing memory. If logs contain sensitive data, stale assumptions, or prompt-like instructions, those may be retained or trusted in future sessions without a validation step.
Please read the current `MEMORY.md` and the daily log files (`memory/YYYY-MM-DD.md`) from the past 7 days... Extract new patterns... prune obsolete rules or constraints... Move domain-specific knowledge into the appropriate `memory/topics/*.md` files... Rewrite `MEMORY.md`
Use a dry-run review workflow, filter secrets and credentials, keep provenance for each memory entry, and require user approval before pruning or rewriting persistent memory.