T06 · System Persistence
- Location
SKILL.md:25- Finding
Persistent Weekly Agent Execution Through a Scheduled Cron Job
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is review-worthy because it sets up an ongoing background agent that can rewrite long-term memory without clear limits or approval safeguards.
Only install this if you intentionally want a recurring background memory-consolidation job. Prefer running it on demand or as a dry-run that produces a diff, keep backups of MEMORY.md and memory/topics, review deletions and new long-term rules before applying them, and make sure you know how to list and remove the cron entry.
SKILL.md:25Persistent Weekly Agent Execution Through a Scheduled Cron Job
SKILL.md:36Untrusted Log Content Can Be Promoted Into Persistent Agent Memory
The description says to use this skill when the user asks to 'organize an agent's memory into domain-specific topics to save context window tokens,' which is a broad natural-language condition rather than a narrowly scoped trigger. It lacks explicit boundaries or negative examples, so ordinary requests about organizing memory could unintentionally invoke this skill.
The skill instructs the agent to create a recurring automated job that reads and rewrites MEMORY.md and related memory files on an ongoing basis, but it does not require an explicit warning or renewed user consent about persistent background modification. In an agent environment, scheduled autonomous file mutation can surprise users, overwrite valuable context, or silently reshape long-term memory beyond the original request.
The instruction to proactively offer reading and partitioning a bloated MEMORY.md encourages immediate reorganization of user data, but it does not require a clear warning that files may be moved, split, or rewritten. While framed as helpful, this can lead to unexpected modification of important memory content and potential loss of structure or meaning if the migration is performed incorrectly.
No suspicious patterns detected.