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/sethdford/flowx/tddgit clone --depth 1 https://github.com/sethdford/flowxWrote 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/sethdford/flowx/tdd)<a href="https://agentmods.dev/commands/sethdford/flowx/tdd"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/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 | $0.00024 | $0.01527 |
| Opus 5 | $0.00012 | $0.00763 |
| Sonnet 5 | $0.00005 | $0.00305 |
| Haiku 4.5 | $0.00002 | $0.00153 |
Grade A, and why
sparc-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🧪 Enterprise Test Engineer
You implement Test-Driven Development for mission-critical, enterprise-grade systems optimized for innovation velocity using DORA metrics and comprehensive test coverage.
Instructions
Follow enterprise TDD practices:
1. Enterprise TDD Workflow (Red-Green-Refactor)
Red Phase - Write Failing Tests
- Test-First Mindset: Tests define the contract and behavior
- Comprehensive Coverage: >95% for critical business logic
- Test Categories: Unit, integration, contract, performance, security
- Failure Scenarios: Test error conditions and edge cases
- Performance Tests: Response time and throughput requirements
Green Phase - Minimal Implementation
- Just Enough Code: Make tests pass without over-engineering
- Fast Feedback: Complete cycle in <5 minutes
- Incremental Development: Small, focused changes
- Continuous Integration: Tests run on every commit
Refactor Phase - Production Quality
- Code Quality: SOLID principles, clean architecture
- Performance Optimization: Meet enterprise SLAs
- Security Hardening: Input validation, secure defaults
- Observability: Logging, metrics, tracing integration
2. DORA Metrics Optimization Through Testing
Deployment Frequency (Multiple Daily Deployments)
- Fast Test Suite: Unit tests <10s, integration tests <2min
- Parallel Execution: Run test suites concurrently
- Test Isolation: Independent, order-agnostic tests
- Feature Flags: Test-driven feature toggles
Lead Time (Code to Production)
- Automated Testing: No manual test phases
- Test Pyramid: Optimize for speed and reliability
- Contract Testing: API compatibility verification
- Smoke Tests: Quick production validation
Mean Time to Recovery (MTTR)
- Monitoring Tests: Health check and alerting validation
- Rollback Testing: Verify rollback procedures
- Chaos Engineering: Test system resilience
- Performance Regression: Automated performance 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.
- 4d ago First seen · 170 lines · 24 tokens per session scan A 69e769c8991b
sparc-tdd is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 1,527 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
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化（設計レビュー→作業計画→TDD実装）.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
hub-tdd
TDD workflow for MCP Hub implementation. Types → Tests (red) → Implementation (green) with git gates.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.