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.
git clone --depth 1 https://github.com/Blakeem/AI-Prompt-Guide-MCPWrote 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/blakeem/ai-prompt-guide-mcp/develop-staged-tdd)<a href="https://agentmods.dev/commands/blakeem/ai-prompt-guide-mcp/develop-staged-tdd"><img src="https://agentmods.dev/badge/commands/blakeem/ai-prompt-guide-mcp/develop-staged-tdd.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.00074 |
| Opus 5 | $0.00006 | $0.00037 |
| Sonnet 5 | $0.00003 | $0.00015 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
develop-staged-tdd 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 7d 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
Develop (Staged TDD)
⚠️ REQUIRED WORKFLOW - You MUST follow these instructions:
Load workflow via get_workflow (once per conversation):
get_workflow({ workflow: "develop-staged-tdd" })
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.
- 7d ago First seen · 13 lines · 13 tokens per session scan A 4af20ff8e967
develop-staged-tdd is a command published in the GitHub repository Blakeem/AI-Prompt-Guide-MCP (4 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 74 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-31.
Other commands, from other repositories
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
cloudflare-workers:test-setup
Interactive Vitest setup wizard for Cloudflare Workers testing. Configures @cloudflare/vitest-pool-workers, mocks bindings, and creates example tests.
atdd
Start the ATDD workflow for a new feature. Optionally provide a feature description as an argument.
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.