T09 · Insecure Skill Coding Practices
- Location
references/flow.ts:13- Finding
Command and Instruction Injection Through Unquoted Child-Task Construction
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill’s publishing purpose is clear, but it can perform an irreversible external publish without a clear human approval gate and includes unsafe reference patterns for constructing child-agent commands.
Review this skill carefully before installing or using it for real publishing. Only run it with trusted, reviewed skill folders and sanitized slug/name/version/changelog values, and require an explicit manual approval immediately before the live publish command. Prefer structured argument passing over child-agent command strings, and avoid the node -e slug interpolation pattern in the verification script.
references/flow.ts:13Command and Instruction Injection Through Unquoted Child-Task Construction
references/inspect.sh:19JavaScript Code Injection Through Slug Interpolation in node -e
The code generally matches the stated orchestration and publishing purpose: it uses TaskFlow to create a managed flow, performs a dry-run validation command, executes a publish command to ClawHub, and records final state. However, the description explicitly says the flow validates, packages, publishes, and then verifies the published artifact. In the provided code, there is no separate packaging action and no post-publication verification step. The flow is finished immediately after the publish task is launched/recorded, with no evidence of artifact verification. Therefore the description overstates the implemented behavior in material ways.
Referenced artifact was not completely inspected
contains a valid `SKILL.md` frontmatter block.
Referenced artifact was not completely inspected
contains a valid `SKILL.md` frontmatter block.
Referenced artifact was not completely inspected
for the verification commands, and `references/flow.ts` for the TaskFlow
The skill describes performing a live, irreversible publish to an external registry but does not prominently require explicit user confirmation immediately before the write. In agentic contexts, this increases the risk of unintended publication, supply-chain mistakes, or accidental release of sensitive or unreviewed content because the action cannot be cleanly rolled back.