Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add sjarmak/agent-workflows --skill prd-build-cancelgit clone --depth 1 https://github.com/sjarmak/agent-workflowsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sjarmak/agent-workflows/prd-build-cancel)<a href="https://agentmods.dev/skills/sjarmak/agent-workflows/prd-build-cancel"><img src="https://agentmods.dev/badge/skills/sjarmak/agent-workflows/prd-build-cancel.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00013 | $0.00443 |
| Opus 5 | $0.00006 | $0.00221 |
| Sonnet 5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade D, and why
prd-build-cancel scanned grade D with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/prd-build.state.json Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .claude/prd-build.state.json .claude/prd-build.log.md .claude/prd-build-artifacts/ What it actually says
PRD Build Cancel
Check for an active run:
if [ -f .claude/prd-build.state.json ]; then
cat .claude/prd-build.state.json
else
echo "NO_STATE_FILE"
fi
If NO_STATE_FILE: tell the user there's no active run to cancel.
Otherwise, present the current status and ask the user which action they want:
-
Pause — Update
.claude/prd-build.state.jsonstatus to"paused". State is preserved. Resume later with/prd-build-resume.Also append a timestamped line to
.claude/prd-build.log.md: "Run paused by user". -
Cancel (clean) — Remove all worktrees, branches, and state files:
# Remove worktrees git worktree list --porcelain | grep -oP 'worktree \K.*prd-build.*' | while read wt; do git worktree remove --force "$wt"; done # Remove branches git branch --list 'prd-build/*' | xargs -r git branch -D # Remove state files rm -rf .claude/prd-build.state.json .claude/prd-build.log.md .claude/prd-build-artifacts/ -
Cancel (keep branches) — Remove worktrees and state but keep git branches for manual inspection:
# Remove worktrees only git worktree list --porcelain | grep -oP 'worktree \K.*prd-build.*' | while read wt; do git worktree remove --force "$wt"; done # Remove state files rm -rf .claude/prd-build.state.json .claude/prd-build.log.md .claude/prd-build-artifacts/
WAIT for the user to choose before taking any action.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 49 lines · 13 tokens per session scan D ae7cbf861966
prd-build-cancel is a skill published in the GitHub repository sjarmak/agent-workflows (9 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 443 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
incident-postmortem-report
Produce a thorough incident post-mortem report after an outage or customer-impacting event. Covers executive summary, impact, detailed timeline, root cause, contributing factors, corrective and preventive actions, and lessons learned. Use when the user asks to write, draft, or complete a post-mortem, blameless review…
aws-cost-analysis
Analyze AWS costs by service, account, and time period. Identifies top spenders, cost anomalies, and optimization opportunities. Use when reviewing cloud spend, preparing cost reports, or investigating unexpected charges.
release-readiness-check
Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.
afrexai-compliance-engine
Your AI compliance officer. Guides startups and scale-ups through SOC 2, ISO 27001, GDPR, HIPAA, and PCI DSS — from zero to audit-ready. No consultants needed.
competitive-offer-architect
Design irresistible offer packages with real salary benchmarks, negotiation playbooks, and competitive counter-strategies. Co-designed with Siku (司库). Includes total compensation calculator, negotiation scripts, and BATNA analysis.