T01 · Skill Instruction Hijacking
- Location
SKILL.md:128- Finding
Persistent Output-Control Instruction Injection
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This markdown-only skill is mostly about agent harness planning, but it also encourages persistent agent behavior changes, broad commits, and self-updates without clear user approval.
Review this skill carefully before installing. Treat its generated CLAUDE.md, AGENTS.md, output-gate, progress-file, and self-improvement snippets as drafts only; avoid the NO_REPLY output gate, replace git add -A with explicit file staging after diff review, and require human approval before any persistent agent configuration, learning log, or skill/template change.
SKILL.md:128Persistent Output-Control Instruction Injection
SKILL.md:113Persistent Agent State and Instruction Modification
SKILL.md:145Overbroad Git Staging May Commit Unrelated Sensitive Files
The description promises auto-generated, directly deployable artifacts without clearly warning that these outputs may alter project behavior or persist state. In practice, users or agents may apply these files mechanically, introducing unreviewed operational changes into repositories or runtime workflows.
The trigger condition includes broad phrases like optimizing an agent architecture, which can cause the skill to activate for generic requests not intended for this workflow. Over-broad activation increases the chance of irrelevant instructions being injected into unrelated tasks, leading to unintended process or state modifications.
The session protocol instructs repeated git commits after each task without an explicit warning or approval checkpoint, encouraging repository mutation as a default behavior. In automated environments, this can create noisy history, commit sensitive intermediate data, or persist accidental changes without human review.
The self-improvement section instructs the skill to write learning logs and update itself when certain conditions occur, expanding behavior beyond the user-requested harness diagnosis and artifact generation. In an agent setting, this can cause unauthorized state changes, persistence, and scope creep, especially if the agent has filesystem access or can modify skill artifacts.
The user-facing instructions and examples are presented in Chinese, but the file does not state that the skill is Chinese-only or allow the user to choose another language. This can violate a language/locale policy if users are expected to receive content in their preferred language unless they opt in.
No suspicious patterns detected.