T01 · Skill Instruction Hijacking
- Location
SKILL.md:554- Finding
Agent Behavior and Output Format Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a Python-development guide, but it overreaches by claiming override authority, forcing chain-of-thought output, and broadening edits beyond the user's likely request.
Install only if you are comfortable with an opinionated Python style guide that may push broad formatting and documentation changes. Treat its response-format and chain-of-thought requirements as unsafe; users should prefer a version that keeps edits scoped to the request, avoids mandatory private reasoning disclosure, and pins container images by digest or reviewed version.
SKILL.md:554Agent Behavior and Output Format Hijacking
SKILL.md:424Mutable Latest Tag Used for a Build-Time Dependency
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
adduser --system --uid 1001 --ingroup appgroup appuser
# Copy passwd/group to distroless:
COPY --from=builder /etc/passwd /etc/passwd
COPY --from=builder /etc/group /etc/group
USER appuser
```
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
build/
.venv/
venv/
.env
*.sqlite3
.ruff_cache/
.pytest_cache/
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
build/
.venv/
venv/
.env
*.sqlite3
.ruff_cache/
.pytest_cache/
The skill metadata hard-codes that reasoning must be output in Russian, removing user choice over language and potentially forcing disclosure of internal deliberative content in a fixed format. This is risky because it normalizes exposing reasoning structure and can conflict with safety policies or user expectations in multilingual environments.
The response format explicitly mandates a 'Цепочка мыслей' section in Russian, which is effectively an instruction to reveal step-by-step internal reasoning. Requiring chain-of-thought disclosure is dangerous because it can expose sensitive internal decision processes and weaken downstream safety controls.
No suspicious patterns detected.