T02 · Agent Memory Poisoning
- Location
SKILL.md:55- Finding
Unvalidated External Feedback Can Influence Persistent Agent Memory and Workflows
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is meant to manage PR reviews, but it asks the agent to autonomously change branches, commit work, and write persistent memory/state without clear user approval.
Install only if you are comfortable with an agent actively monitoring PRs and making repository changes. Before use, constrain it to specific repositories and PRs, require approval before commits or pushes, store tracking state in a user-approved skill-specific location, and disable automatic updates to core memory, skills, or workflows.
SKILL.md:55Unvalidated External Feedback Can Influence Persistent Agent Memory and Workflows
SKILL.md:35Reviewer-Controlled Content Can Trigger Autonomous Code Changes and Commits
SKILL.md:64Hard-Coded Cross-Workspace Path Violates Filesystem and Repository Boundaries
Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
- **Remove from active tracking list**
- **Add to merged records** for success tracking
- **Celebrate the contribution!**
- **Update skills and workflows** based on successful patterns
## Real-time Tracking List Synchronization
The skill explicitly instructs the agent to automatically commit changes to the PR branch in response to reviewer feedback, but it does not require explicit user confirmation before modifying repository state. In the context of an autonomous agent skill, silent commits can cause unintended code changes, commit sensitive data, or alter a branch in ways the user did not authorize.
The skill mandates immediate persistence to a fixed local file path under the user's home directory and continuous synchronization after PR state changes, without clear consent or scope restrictions. This creates a risk of unauthorized local data modification, state corruption, or overwriting user-maintained files, especially under concurrent or repeated execution.
The manifest description states the skill will 'actively monitor, respond to, and drive Pull Request reviews to completion with real-time tracking list synchronization,' which implies broad, ongoing automation and action-taking without specifying clear activation boundaries, user consent, or scope limits. In an agent ecosystem, this can cause the skill to be invoked too broadly or granted implicit authority to act on repositories and review workflows beyond a narrowly defined user request.