T02 · Agent Memory Poisoning
- Location
SKILL.md:12- Finding
Unvalidated Corrections Can Poison Persistent Agent Memory
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill has a coherent learning purpose, but it creates persistent agent rules from corrections and imports community guidance without enough approval, validation, or containment.
Install only if you are comfortable with the agent keeping workspace-level behavioral rules that affect later decisions. Review every new lesson before it is saved, avoid storing secrets or project-specific sensitive details, and pin or manually review any community rule files before using them as guidance.
SKILL.md:12Unvalidated Corrections Can Poison Persistent Agent Memory
SKILL.md:79Unpinned Community Rules Create an External Instruction Supply-Chain Risk
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
## How to Record
1. Stop. Don't apologize at length.
2. Identify the category.
3. Write the rule in imperative form.
4. Append to lessons.md (never overwrite).
The community-sharing feature encourages sending lessons to an external repository but does not require explicit user consent, preview, or strong safeguards against leaking sensitive operational details. 'Anonymized' is underspecified and can fail in practice, so mistakes, project names, internal paths, or user data could be disclosed externally.
The activation criteria are broad enough to trigger during many normal interactions, including generic corrections or routine decision-making. That increases the chance the skill will run unexpectedly, causing unsolicited file reads/writes and behavior changes without an explicit user request.
The skill instructs the agent to write to {workspace}/lessons.md automatically after errors or corrections, but it does not foreground that this modifies user workspace state. In environments where agents should minimize side effects, silent persistence can create integrity, privacy, and auditability issues.
No suspicious patterns detected.