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/samibs/skillfoundry/blitzgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/commands/samibs/skillfoundry/blitz)<a href="https://agentmods.dev/commands/samibs/skillfoundry/blitz"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/blitz.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 | $0.00000 | $0.00358 |
| Opus 5 | $0.00000 | $0.00179 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
blitz 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 yesterday.
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
/blitz - Blitz Mode Commander
/blitz is a thin alias for /go --mode=semi-auto --parallel --tdd. It runs the full /go pipeline at maximum speed: semi-auto remediation + parallel wave execution + TDD enforcement. Blitz is for well-defined PRDs with independent stories.
Persona: See agents/fixer-orchestrator.md for auto-remediation and agents/_parallel-dispatch.md for wave planning.
Reflection Protocol: See agents/_reflection-protocol.md.
Dispatch
/blitz [args] → /go --mode=semi-auto --parallel --tdd [args] with full argument passthrough.
/blitz genesis/auth.md → /go --mode=semi-auto --parallel --tdd genesis/auth.md
/blitz --dry-run → preview the wave plan without executing
When blitz applies
Blitz only adds value when stories can run in parallel. Readiness check — all must hold, or use /gosm instead:
- The PRD is well-defined and validated
- Stories are mostly independent (wave planning needs independence)
- At least 2 stories are independent — otherwise parallelism has no value
Wave planning is defined in agents/_parallel-dispatch.md: stories are grouped into dependency-ordered waves, same-wave stories are checked for file-overlap conflicts, and all stories in a wave are dispatched simultaneously (RED→GREEN→REFACTOR under TDD). Run --dry-run to preview the wave plan before executing. Everything else — phases, Anvil gates, delivery audit — is /go's behavior unchanged.
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.
- yesterday First seen · 30 lines · 0 tokens per session scan A 8bdfb45a0e2e
blitz is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 358 tokens. 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-09-03.
Other commands, from other repositories
act
Execute the implementation plan with TDD.
implement-tdd
Execute TDD workflow following Red → Green → Refactor cycle with .ai-rules standards.
testarch-atdd
Generate failing acceptance tests using TDD cycle. Use when the user says ""lets write acceptance tests"" or ""I want to do ATDD"".
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.