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/summarybotng/summarybot-ngWrote 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/summarybotng/summarybot-ng/tdd)<a href="https://agentmods.dev/commands/summarybotng/summarybot-ng/tdd"><img src="https://agentmods.dev/badge/commands/summarybotng/summarybot-ng/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.00000 | $0.00286 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
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 3d 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.
This is a copy
100% identical to tdd — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
SPARC TDD Mode
Purpose
Test-driven development with TodoWrite planning and comprehensive testing.
Activation
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "tdd",
task_description: "shopping cart feature",
options: {
coverage_target: 90,
test_framework: "jest"
}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run tdd "shopping cart feature"
# For alpha features
npx claude-flow@alpha sparc run tdd "shopping cart feature"
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run tdd "shopping cart feature"
Core Capabilities
- Test-first development
- Red-green-refactor cycle
- Test suite design
- Coverage optimization
- Continuous testing
TDD Workflow
- Write failing tests
- Implement minimum code
- Make tests pass
- Refactor code
- Repeat cycle
Testing Strategies
- Unit testing
- Integration testing
- End-to-end testing
- Performance testing
- Security testing
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.
- 3d ago First seen · 55 lines · 0 tokens per session scan A fd48e2e17900
tdd is a command published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 286 tokens. A static security scan graded it A with 0 findings. It is 100% identical to tdd, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
test
Design or run focused test validation for a task, bug, or diff.
refactor-sprint
Parallel refactor sprint — fires refactor-cleaner + code-simplifier + type-design-analyzer + tdd-guide simultaneously. Full cleanup in one pass.
tests
Generate unit/integration tests from architecture design. Tests written AFTER architecture, BEFORE implementation.
p5-impl-red
Writes unit tests for a feature BEFORE production code exists. Tests must fail.
rust-test
Rust TDD workflow with unit and property tests.
rust-test
Rust TDD workflow with unit and property tests.