T02 · Agent Memory Poisoning
- Location
SKILL.md:59- Finding
Unsafe Cross-Session Memory Persistence and Automatic Reloading
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent professional-behavior framework, but it broadly tells agents to persist and reload user/work memory without enough consent, scoping, or retention controls.
Review this skill before installing if you do not want an agent to keep workspace memory. Only use it where persistent notes are acceptable, and configure the agent to ask before writing memory, avoid storing sensitive or third-party instruction text, treat old memory as untrusted context, and provide a way to review and delete stored entries. Maintainers should also avoid running the packaging script in directories that contain .env files, keys, private notes, caches, or other non-distributable files.
SKILL.md:59Unsafe Cross-Session Memory Persistence and Automatic Reloading
scripts/package_skill.py:25Unrestricted Recursive Packaging Can Disclose Sensitive Files
The README states the skill is 'automatically triggered' whenever the assistant needs to demonstrate professional workplace behaviors, which is a vague and overly broad activation condition. Broad trigger language can cause the skill to activate in many unrelated contexts, potentially overriding narrower instructions or importing expansive behavioral guidance in situations where it was not explicitly requested.
The declared description presents a sophisticated AI-agent behavior framework with planning, closed-loop execution, and collaborative tool orchestration. The supplied code does not implement any of those behaviors. Instead, it is a local setup utility that initializes folders and placeholder files for a skill. While filesystem scaffolding could be a supporting development utility, this code chunk’s actual purpose is materially different from the declared runtime capability of the skill. Therefore, this is a clear description-to-behavior mismatch.
The declared description presents a conceptual AI agent framework for behavior, planning, and tool orchestration. The supplied code does not implement agent logic, planning loops, decision-making, collaboration, or any runtime AI behavior. Instead, it is a standalone filesystem utility that walks a directory and packages files into a .skill archive for upload/distribution. This is a materially different primary purpose, so the description does not accurately represent the code.
The declared description presents a high-level AI agent framework focused on autonomous behavior, planning, decision-making, and tool orchestration. The supplied code does not implement any of those agent capabilities. Instead, it performs local filesystem validation for a specific skill package structure and metadata. This is a materially different primary purpose, not merely a supporting detail of the declared framework. No agent loop, planning logic, collaboration, or execution orchestration is present in the code chunk.
The skill explicitly instructs persistent file writes in its Memory Management section, but the frontmatter declares no tool scope or permissions. That creates an undeclared capability boundary: a user or host system may invoke the skill expecting advisory behavior, while the skill encourages filesystem persistence that can retain sensitive data or alter local state.
The description is broad enough to trigger on many normal professional or multi-step requests, which can cause over-activation of the skill. In context, that matters because the skill also promotes memory writes, dynamic decision-making, and multi-tool orchestration; broad activation increases the chance those behaviors occur without specific user expectation or need.
The skill directs the agent to always write important information to persistent files and maintain long-term memory, but it does not require disclosure, consent, minimization, or retention limits. In practice, this can lead to silent storage of sensitive user data, cross-session profiling, and unintended persistence of confidential information.
The 'When to Apply' section covers common scenarios like complex requests, business communication, leadership behavior, and long-term relationships, making the skill applicable to a very large share of interactions. This broad scope is risky because it can normalize persistent memory use and autonomous planning/tool behavior in contexts where a lightweight, non-persistent response would be safer.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
6. **Document reasoning**: Record the decision process for future reference
### Red Lines (Never Cross):
- **Privacy violations**: Exposing confidential information without consent
- **Harmful content**: Generating content that promotes violence, hate, or illegal activity
- **Deception**: Misrepresenting capabilities, identity, or intentions
- **Exploitation**: Taking advantage of user vulnerabilities or trust
Several capability labels and principles are presented in Chinese alongside English glosses, but the skill does not state whether this bilingual presentation is optional or user-preference driven. Because language choice is not explicitly offered, this may conflict with a policy requiring language or locale opt-in.