T01 · Skill Instruction Hijacking
- Location
SKILL.md:1- Finding
Primary Skill Metadata Hijacks Broad Modification Requests
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The package advertises a research skill but its primary runtime file is a broadly triggered skill-creation workflow that can redirect ordinary edit requests into creating or modifying agent skills.
Install only if you intend to use a skill-authoring workflow and are comfortable with it influencing broad modification requests. The package should be corrected so the manifest and SKILL.md describe the same purpose, the trigger is limited to explicit skill-creation or skill-update requests, and memory storage requires clear consent and excludes sensitive or instruction-like content.
SKILL.md:1Primary Skill Metadata Hijacks Broad Modification Requests
prompt.txt:199Untrusted Session Content Can Be Written into Persistent Agent Memory
This section instructs the agent to create and edit skills, including writing SKILL.md and running initialization scripts. In the context of an agent skill, that is a self-modification capability: if the skill is triggered too broadly, it could authorize changes to agent behavior or create new persistent capabilities without sufficiently narrow guardrails.
1. Understand the skill with concrete examples
2. Plan reusable skill contents (scripts, references, templates)
3. Initialize the skill (run init_skill.py)
4. Edit the skill (implement resources and write SKILL.md)
5. Deliver the skill (send SKILL.md path via notify_user)
6. Iterate based on real usage
The 'Update SKILL.md' instruction directly guides modification of the skill's own instruction file. On its own this is normal documentation for a skill-authoring tool, but combined with broad activation conditions it becomes dangerous because it can lead the agent to rewrite its operational guidance during ordinary modification tasks.
Delete any unused example files from initialization.
#### Update SKILL.md
**Writing Guidelines:** Always use imperative/infinitive form.
The skill declares it is 'automatically engaged' for broad conditions like in-depth research, verification, debugging, or accuracy, which are subjective and expansive triggers. In an agent system, overly broad auto-activation can silently change behavior across many tasks, increasing prompt-scope, instruction precedence conflicts, and the chance that this skill interferes with unrelated workflows or causes excessive autonomous looping.
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.
- Technical accuracy is important
- Source comparison is necessary
Never assume tool outputs are correct without verification.
### Budget Control
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.
- Technical accuracy is important
- Source comparison is necessary
Never assume tool outputs are correct without verification.
### Budget Control
The description says the skill MUST be read and followed for any modification or improvement request, which is overly broad routing language. This can cause the skill to activate in many unrelated editing contexts and steer the agent into unnecessary file creation/modification workflows, increasing the chance of unintended self-modification or workflow hijacking.
The manifest identifies the skill as "infinite-research-hidden-no" and describes advanced research features, while the provided skill context is "skill-creator," which is supposed to guide creating or updating skills. This mismatch can mislead reviewers, users, or automated systems about the skill’s actual purpose, weakening trust boundaries and potentially concealing different behavior than expected.
The checklist explicitly instructs the agent to store reusable patterns, recurring user preferences, constraints, failed assumptions, and validated insights, but provides no guardrails for excluding sensitive, personal, or security-relevant data. In a skill-creation or agent workflow context, this can normalize over-retention of user data and lead to privacy leaks, unintended persistence of secrets, or unsafe cross-session memory use.
This is a plain text file, so vague-trigger rules apply. The text defines a behavior pattern in very broad terms but provides no concrete trigger phrases, scope limits, or exclusion conditions, which could cause the skill to be applied to many ordinary requests unintentionally.
Natural-language policy rules apply to all file types. The mandated output format hard-codes English response labels and does not offer any language or locale choice, which can conflict with language/locale flexibility requirements.