T09 · Insecure Skill Coding Practices
- Location
SKILL.md:97- Finding
Unredacted Session Data May Be Persisted in Handoff Files
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill matches its handoff purpose, but it can persist detailed session history and modify handoff files without redaction or path-safety checks.
Install only if you are comfortable with session details being saved to project files. Review generated handoffs before committing or sharing them, avoid invoking it after secrets appeared in the session, and check any CURRENT file before letting the skill update an existing handoff.
SKILL.md:97Unredacted Session Data May Be Persisted in Handoff Files
SKILL.md:65Unvalidated CURRENT Pointer May Cause Writes Outside the Handoff Directory
The trigger phrases are broad, conversational, and overlap with common user language like 'summarize this session' or 'hand this off'. That increases the chance of accidental invocation, which can cause unintended file creation or updates and expose session details into project artifacts without explicit user confirmation.
The instruction to 'Do not ask the user questions' forces autonomous inference from conversation history and git state, then proceeds to write files. That removes an important consent and validation checkpoint, increasing the risk of incorrect summaries, unintended persistence of sensitive data, or writes to the wrong handoff stream.
Use this skill when the user says "handoff", "summarize this session", "create a handoff", "hand this off", or invokes `/handoff`.
Produce a precise handoff document and write it to a file. Do not ask the user questions — derive everything from conversation history and git state.
If the user provides arguments, treat them as the intended focus of the next session and prioritize that focus in **Goal**, **Current State**, and **Next Steps**.
If the user says "update handoff" or similar, update the most recent handoff file in place instead of creating a new one.
The skill is instructed to write artifacts and may overwrite the most recent handoff in place, but it provides no warning or confirmation before modifying repository files. In practice this can silently alter tracked documentation, clobber an existing handoff, or create persistence for sensitive session content the user did not intend to save.
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.
## Anti-patterns
- Do not ask the user "what did we work on?" — derive from conversation.
- Do not write vague entries like "various files updated" — be specific.
- Do not skip the git commands — they provide objective ground truth.
- Do not create a new handoff if the user says "update handoff" — overwrite the most recent one.