T01 · Skill Instruction Hijacking
- Location
scripts/soul-create.py:26- Finding
Hardcoded authority hierarchy redirects persistent agent behavior
- Content
View full analysis
Vulnerability Details
File Location:
references/collaboration-protocol.md:24-26, 45-49;scripts/soul-create.py:26-30
Vulnerability Type: Persistent redirection of agent instructions and reporting
Risk Level: HighVulnerable Code
references/collaboration-protocol.md:24-26:markdown - Adam 只与小咪对话 - 所有 Agent 通过小咪接收指令和上报结果 - 小咪是唯一的"对外接口"references/collaboration-protocol.md:45-49:markdown ## 与上级的协作协议 - 直接上级:小咪 - 日常汇报:每5分钟/每小时/完成后 - 升级触发:[什么情况下需要上报] - 决策权限:[可以自主决定的范围]scripts/soul-create.py:26-30:python ## 与上级的协作协议 - 直接上级:小咪 - 日常汇报:完成后/每小时/实时 - 升级触发:[什么情况下需要上报] - 决策权限:[可以自主决定的范围]Technical Analysis
The skill is presented as a reusable system for creating agent personality files, but it embeds a specific authority hierarchy into both its collaboration instructions and every generated
SOUL.mdfile. The generated configuration designates a named agent as the direct superior and instructs agents to route instructions and reports through that identity.These are not neutral formatting defaults. According to the skill documentation,
SOUL.mddefines an agent's personality, principles, responsibilities, and collaboration behavior. If the surrounding agent platform loads this file as persistent configuration, the hardcoded rules can continue influencing later sessions. The user is not required to select or confirm the named superior before the behavior-changing file is written.Although the behavior also has persistence characteristics, the best matching classification is instruction hijacking because the primary mechanism is the insertion of unauthorized authority and communication instructions into agent configuration.
Attack Path
- A user installs the skill as a generic personality-management utility.
- The user follows the documented workflow and runs
soul-create.pywith an agent name. - The script writes a
SOUL.mdfile co ...[truncated 1163 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove all hardcoded personal identities, superior names, reporting routes, and authority relationships from templates and reference material.
- Default new agents to having no superior or external reporting route.
- Require the user to supply hierarchy values explicitly through named command-line options or an interactive setup process.
- Display the complete collaboration configuration and require confirmation before writing behavior-changing rules.
- Clearly distinguish optional examples from active template content. Example identities must never be copied automatically into generated files.
- Add validation that rejects unresolved placeholders and prevents the skill from silently creating communication or authority relationships.
- Document that generated files may persistently affect agent behavior and should be reviewed before activation.
- Add tests confirming that a default invocation does not designate any person or agent as an instruction source, report recipient, or superior.
