T02 · Agent Memory Poisoning
- Location
SKILL.md:61- Finding
Persistent Storage of User-Controlled Behavioral Rules
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a feedback-memory tool, but it can persist user feedback into agent behavior files and overwrite workspace agent instructions in ways that need review before installation.
Install only if you want this skill to make durable changes to your agent's memory and workspace instruction files. Review and constrain writes to AGENTS.md, MEMORY.md, memory/conclusions.md, and feedback-log.md, and avoid storing secrets, personal data, safety-policy changes, or broad tool-use instructions as feedback memory.
SKILL.md:61Persistent Storage of User-Controlled Behavioral Rules
SKILL.md:9Self-Declared Instruction Precedence Over Host Agent Configuration
The README explicitly promotes turning user feedback into long-term memory and writing it through a persistent chain of files, but it does not warn about privacy, retention, consent, or the risk of storing sensitive or adversarial user content. In an agent skill, persistent memory materially changes the security boundary: casual chat feedback can become durable behavior-shaping state, enabling privacy leakage, prompt-injection persistence, and unwanted policy drift.
The manifest description and the full skill instructions are written to prescribe behavior entirely in Chinese, with no indication that the user may choose another language or locale. This creates a natural-language policy concern because it implicitly enforces a specific language for operation without documented opt-in or justification.
The skill instructs writing user feedback and derived conclusions into multiple local files, but the upfront description does not clearly and explicitly warn users about the breadth of persistence. This creates a consent and privacy risk because users may believe they are giving ephemeral feedback while the system stores it across workspace, memory, and retrieval layers for later reuse.
The skill mandates cross-file, cross-session persistence and later retrieval of user feedback, conclusions, and behavioral rules. That creates a durable memory channel that can retain sensitive, contextual, or mistaken user data and resurface it later, potentially affecting future responses or leaking information across tasks if access boundaries are weak. The explicit redundancy into multiple files and retrieval verification makes the persistence especially sticky.
The skill goes beyond passive feedback logging and instructs the agent to create git snapshots and perform rollback operations on the workspace. That expands its authority from note-taking into repository state management, which can alter unrelated files, overwrite user work, or revert changes without clear task-scoped consent. In this context, a feedback skill should not be issuing version-control commands as part of its normal flow.
The file claims the skill does not call external scripts, yet it explicitly directs execution of git commands elsewhere. Even if git is not an external script per se, this is materially misleading because the skill still causes command execution and repository mutation, reducing operator awareness of its true behavior and increasing the chance of unsafe use.