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/Fmarzochi/EGCWrote 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/fmarzochi/egc/tdd)<a href="https://agentmods.dev/commands/fmarzochi/egc/tdd"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/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/fmarzochi/egc/tdd"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/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.00011 | $0.00424 |
| Opus 5.5 | $0.00004 | $0.00170 |
| Sonnet 5.5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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.
This is a copy
95% identical to tdd — 85 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
TDD Command
Implement the following using strict test-driven development: $ARGUMENTS
TDD Cycle (MANDATORY)
RED → GREEN → REFACTOR → REPEAT
- RED: Write a failing test FIRST
- GREEN: Write minimal code to pass the test
- REFACTOR: Improve code while keeping tests green
- REPEAT: Continue until feature complete
Your Task
Step 1: Define Interfaces (SCAFFOLD)
- Define TypeScript interfaces for inputs/outputs
- Create function signature with
throw new Error('Not implemented')
Step 2: Write Failing Tests (RED)
- Write tests that exercise the interface
- Include happy path, edge cases, and error conditions
- Run tests - verify they FAIL
Step 3: Implement Minimal Code (GREEN)
- Write just enough code to make tests pass
- No premature optimization
- Run tests - verify they PASS
Step 4: Refactor (IMPROVE)
- Extract constants, improve naming
- Remove duplication
- Run tests - verify they still PASS
Step 5: Check Coverage
- Target: 80% minimum
- 100% for critical business logic
- Add more tests if needed
Coverage Requirements
| Code Type | Minimum |
|---|---|
| Standard code | 80% |
| Financial calculations | 100% |
| Authentication logic | 100% |
| Security-critical code | 100% |
Test Types to Include
- Unit Tests: Individual functions
- Edge Cases: Empty, null, max values, boundaries
- Error Conditions: Invalid inputs, network failures
- Integration Tests: API endpoints, database operations
MANDATORY: Tests must be written BEFORE implementation. Never skip the RED phase.
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 · 67 lines · 11 tokens per session scan A fc0272cefdc4
tdd is a command published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11 tokens to every session and 424 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to tdd, differing in 85 lines, and is treated as a copy.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
spec-impl
Execute spec tasks using TDD methodology.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
test
A test-driven development workflow, or TDD, where tests describing the expected behavior are written before the implementation. For bugs, it first adds a test that reproduces the failure.
implement-approved-slice
Implement only the approved slice with minimal changes, then persist execution evidence in slice notes and TASKSTATE.md. The official execution path. Opt-in test-first mode via --tdd. Use when the plan and slice are approved, ambiguity is resolved and files in scope are known. Do not use during discovery or planning…
test-strategy
Define the smallest set of meaningful tests that protects behavior and reduces the regression risk for the active task, persisted as TESTSTRATEGY.md. Use when a change affects behavior, contracts, data flow or regression risk, or auth, biometric or runtime-risk scope lacks one, even if small. Do not use when the…