T01 · Skill Instruction Hijacking
- Location
SKILL.md:13- Finding
Safety and Approval Constraint Override
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a plain Markdown autonomy guide, but it broadly encourages agents to use credentials, take tasks, fix systems, and persist those rules across sessions without enough user-control boundaries.
Install only if you deliberately want a strong autonomy bias and have separate guardrails requiring confirmation before using credentials, touching production systems, sending external messages, modifying account/business data, or changing persistent agent files. Review and narrow the SOUL.md, AGENTS.md, HEARTBEAT.md, and nightly-audit integration snippets before copying them.
SKILL.md:13Safety and Approval Constraint Override
examples/SOUL-integration.md:7Persistent Poisoning of Agent Identity and Control Files
SKILL.md:31Credential Availability Treated as Authorization for Service and Production Actions
This section frames core safety behaviors such as asking permission, hedging, and caution as regressions that must be actively overridden. That is a direct safety-degrading pattern because it pressures downstream agents to suppress protective behaviors that normally prevent overreach, unauthorized actions, and unsafe assumptions.
The 'CTO Test' semantically grants broad discretion to act based on an imagined executive role rather than actual permissions, policies, or user intent. This is dangerous because it substitutes role-play for authorization and can rationalize taking sensitive actions without proper approval.
The embedded template propagates the same safety-override behavior into downstream agent configuration files, increasing persistence and spread of the unsafe policy. This is more dangerous than a one-off instruction because it operationalizes the behavior across sessions and agents, making unsafe autonomy a durable default.
These sections frame permission-seeking as regression and encourage the agent to counteract 'safe' behavior, which can suppress legitimate consent checks. Because the messaging is broad and identity-shaping, it can cause an agent to override user preference boundaries and act in higher-risk situations without confirmation.
The README explicitly normalizes autonomous use of a browser plus credentials without any guardrails about scope, consent, or sensitive-data handling. In a skill whose purpose is to reduce permission-seeking, this increases the chance an agent will access private systems or perform authenticated actions without clear user authorization.
The 'CTO Test' is a vague self-authorization heuristic that substitutes roleplay for explicit policy boundaries. In practice, it can rationalize actions the user did not opt into, especially when combined with the skill's anti-permission framing and emphasis on acting first.
The cumulative override list repeatedly instructs the agent to stop explaining, stop asking, log in, fix things, research immediately, and act whenever work exists. In aggregate, these patterns normalize bypassing caution and create a strong behavioral gradient toward autonomous execution even when tasks may be sensitive, ambiguous, or high impact.
The skill explicitly tells agents to open browsers and log into services whenever credentials are available, without requiring confirmation, scope checks, or consideration of privacy and side effects. In an autonomous agent context, this can trigger real-world actions against user accounts and external systems with little friction, increasing the chance of unauthorized access, data exposure, or unintended state changes.
The guidance normalizes automatically fixing problems, researching, and executing tasks without warning that such actions may modify files, systems, or user data. That is dangerous because it encourages agents to make autonomous state-changing decisions without approval gates, rollback planning, or clear boundaries on what is safe to change.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Read skills/anti-regression/SKILL.md every session for full context.
## Full Integration (Maximum Effect)
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Read skills/anti-regression/SKILL.md every session for full context.
## Full Integration (Maximum Effect)
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Read skills/anti-regression/SKILL.md every session for full context.
## Full Integration (Maximum Effect)
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Read skills/anti-regression/SKILL.md every session for full context.
## Full Integration (Maximum Effect)
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Read skills/anti-regression/SKILL.md every session for full context.
## Full Integration (Maximum Effect)
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Read skills/anti-regression/SKILL.md every session for full context.
## Full Integration (Maximum Effect)
This section explicitly instructs the agent to autonomously log into services, claim tasks, fix issues, and perform research immediately, while framing permission-seeking as regression. In an agent identity file, that materially weakens human approval boundaries and can drive unauthorized or high-impact actions without adequate confirmation, especially around external services and production systems.
The instruction 'Response > 5 lines? → Cut it' imposes a fixed communication policy regardless of user preference. This is a natural-language policy constraint on interaction style and does not offer the user a choice or opt-in.
The override rule says responses longer than five lines should be cut to 1-3 sentences unless they are code or data. This enforces a specific response-style policy without indicating that the user can choose a different level of detail.
No suspicious patterns detected.