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 agentmods add commands/fall-out-bug/sdp/buildgit clone --depth 1 https://github.com/fall-out-bug/sdpWhat 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 | $0.00013 | $0.00159 |
| Opus 5 | $0.00006 | $0.00079 |
| Sonnet 5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
build scanned grade A with 0 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 2d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
/build — Execute Workstream
When calling /build {WS-ID}:
- Load skill:
@.claude/skills/build/SKILL.md - Run pre-build hook:
hooks/pre-build.sh {WS-ID} - Read WS plan
- Execute steps using TDD
- Run post-build hook:
hooks/post-build.sh {WS-ID} - Append Execution Report to WS file
Quick Reference
Input: workstreams/backlog/WS-XXX-*.md
Output: Code + tests + Execution Report
Next: /build WS-XXX-02 or /review F{XX}
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.
- 2d ago First seen · 22 lines · 13 tokens per session scan A 720997a0b647
build is a command published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 159 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
tdd-workflow
Implement the behavior described in $ARGUMENTS using strict TDD. Follow this exact sequence. Do not collapse phases. Each gate requires actual test runner output.
code-review
Review the code changes in this project. For each file changed.
refactor-file
Refactor the file specified in $ARGUMENTS following project conventions.
api-add-endpoint
Create a new API endpoint. $ARGUMENTS should describe the endpoint (e.g., "POST /api/users - create a user").
api-test-endpoint
Test the API endpoint specified in $ARGUMENTS.
debug-error
Debug the following error. $ARGUMENTS should contain the error message or stack trace.