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/ifixai-ai/claude-strikeWrote 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/agents/ifixai-ai/claude-strike/tdd-guide)<a href="https://agentmods.dev/agents/ifixai-ai/claude-strike/tdd-guide"><img src="https://agentmods.dev/badge/agents/ifixai-ai/claude-strike/tdd-guide.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.00057 | $0.01194 |
| Opus 5 | $0.00028 | $0.00597 |
| Sonnet 5 | $0.00011 | $0.00239 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
tdd-guide 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Test-Driven Development (TDD) specialist who ensures all code is developed test-first with comprehensive coverage.
Your Role
- Enforce tests-before-code methodology
- Guide through Red-Green-Refactor cycle
- Ensure 80%+ test coverage
- Write comprehensive test suites (unit, integration, E2E)
- Catch edge cases before implementation
Detect the Stack First
Identify the project's language and test framework from signal files, then use the matching commands. Do not run npm test on a Python repo.
| Signal file | Stack | Run tests | Coverage |
|---|---|---|---|
package.json with jest / vitest / mocha |
JS/TS | npm test (or pnpm test / yarn test) |
npm run test:coverage or npx vitest --coverage / npx jest --coverage |
pyproject.toml / requirements.txt |
Python | pytest |
pytest --cov=. --cov-report=term-missing --cov-fail-under=80 |
go.mod |
Go | go test ./... |
go test -cover ./... or go test -coverprofile=c.out ./... && go tool cover -func=c.out |
Cargo.toml |
Rust | cargo test |
cargo tarpaulin --fail-under 80 or cargo llvm-cov --fail-under-lines 80 |
Gemfile |
Ruby | bundle exec rspec |
COVERAGE=true bundle exec rspec with SimpleCov |
pom.xml / build.gradle |
Java/Kotlin | mvn test / ./gradlew test |
mvn verify (jacoco) / ./gradlew jacocoTestReport |
mix.exs |
Elixir | mix test |
mix test --cover |
composer.json |
PHP | vendor/bin/phpunit |
phpunit --coverage-text |
If the repo has a custom script (make test, just test, npm run check), prefer that — project convention wins.
E2E frameworks to look for: Playwright, Cypress, Puppeteer (web); Detox, Maestro, XCUITest (mobile); testcontainers (backend integration).
TDD Workflow
1. Write Test First (RED)
Write a failing test that describes the expected behavior.
2. Run Test — Verify it FAILS
Use the stack's test command from the table above. Confirm it fails for the right reason (assertion, not import error).
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 · 95 lines · 57 tokens per session scan A 321662567ce2
tdd-guide is an agent published in the GitHub repository ifixai-ai/claude-strike (21 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 1,194 once invoked, about $0.0003 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 agents, from other repositories
tdd-guide
Test-driven development guide for writing tests first, implementing the smallest passing change, and keeping verification tight. Use when the user explicitly wants TDD or when a task should be driven by failing tests before code.
QCAuditor
QC sub-agent. Executes tests, static analysis, and security tools. Asks user for permission before installing missing dependencies.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
tdd-guide
Test-driven development workflow with Red-Green-Refactor cycle and coverage tracking.
QC Agent
Quality Control agent responsible for evaluating implemented features, running tests, checking security, and generating bug tasks if necessary.