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/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/tdd)<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/tdd"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/tdd/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/tdd"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/tdd.svg" alt="Reviewed on agentmods" width="80" 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.00448 |
| Opus 5.5 | $0.00005 | $0.00179 |
| Sonnet 5.5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
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 1mo 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
TDD Session
Implement the requested feature or fix using strict test-driven development.
For the full TDD methodology and patterns, see the skill at
skills/testing/tdd-workflow/SKILL.md.
The TDD Cycle
RED → Write a failing test
GREEN → Write minimal code to make it pass
REFACTOR → Improve code while keeping tests green
REPEAT → Next scenario
Instructions
Follow these steps in order — never skip a phase:
1. Define the Interface
Define types, function signatures, or API contracts for the feature. Stub implementations with throw new Error('Not implemented') or equivalent.
2. Write Failing Tests (RED)
Write tests that cover:
- Happy path — the expected behavior
- Edge cases — empty inputs, nulls, boundary values
- Error conditions — invalid arguments, missing data
Run the tests. Confirm they fail for the expected reason (not due to syntax errors).
3. Implement Minimal Code (GREEN)
Write the simplest code that makes all tests pass. Do not over-engineer. Do not add untested behavior.
Run the tests. Confirm they pass.
4. Refactor (REFACTOR)
Improve code quality while tests stay green:
- Extract constants and helper functions
- Improve naming and readability
- Remove duplication
Run the tests again. Confirm they still pass.
5. Check Coverage
Run tests with coverage enabled. If coverage is below 80%, add more test cases and repeat from step 2.
Rules
- Tests first — never write implementation before its test
- Run tests after every change — red, green, and refactor phases all end with a test run
- Minimal code — only write enough to pass the current tests
- Small steps — one test at a time, one behavior at a time
- Test behavior, not implementation — tests should not depend on internal details
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.
- 1mo ago First seen · 63 lines · 13 tokens per session scan A 82dc8dea017a
tdd is a command published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 448 once invoked, about $0.0001 per session on Opus 5.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-09-09.
Other commands, from other repositories
run
A command for implementing written software requirements using domain-driven design (DDD) and test-driven development (TDD). DDD structures code around the business domain, while TDD starts with tests before implementation.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
qa-pr
Device-test a GitHub pull request on iOS simulator, Android emulator, and/or physical device. Installs the PR head via rn-dev-agent and reports pass/fail with repro steps and screenshots.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
lock-e2e
Promote a verified action into a frozen, locked e2e regression test. Runs the action once strict (no repair) via cdplocke2etest and freezes it to .rn-agent/e2e/ .yaml only if it passes. v1 supports param-free actions only.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.