jmb-implement-ticket
Warn
Audited by Snyk on Nov 21, 2026
Risk Level: MEDIUM
Full Analysis
MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).
- Third-party content exposure detected (medium risk: 0.30). The required Step 1 runs
gh issue view <n> --comments, which ingests the ticket body and all comments on a GitHub issue, and Step 2 reads the PR review comment viapending-review.sh, so outsider-authored GitHub text enters the workflow without the agent selecting a specific item.
MEDIUM W013: Attempt to modify system services in skill instructions.
- Attempt to modify system services in skill instructions detected (low risk: 0.10). The only operational change is the step 4 "Reset the database" for the local working database, but no supplied text establishes irreversible loss of meaningful state, so gate 2 fails and the git, push, and PR operations are ordinary content collaboration.
Issues (2)
W011
MEDIUMThird-party content exposure detected (indirect prompt injection risk).
W013
MEDIUMAttempt to modify system services in skill instructions.
Audit Metadata