ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.
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/affaan-m/ECCWrote 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/affaan-m/ecc/tdd)<a href="https://agentmods.dev/commands/affaan-m/ecc/tdd"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/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/affaan-m/ecc/tdd"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/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.00012 | $0.00357 |
| Opus 5.5 | $0.00005 | $0.00143 |
| Sonnet 5.5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
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.
Copies of this mod
7 near-identical copies found in the catalogue:
What it actually says
TDD Workflow
Follow the RED → GREEN → IMPROVE cycle strictly. Do not write implementation code before a failing test exists.
Cycle
1. RED — Write the failing test
- Write a test that describes the desired behavior.
- Run it. It must fail before continuing.
- Use Arrange-Act-Assert structure.
- Name tests descriptively:
returns empty array when no items match filter, nottest itemFilter.
2. GREEN — Minimal implementation
- Write the minimum code needed to make the test pass.
- Do not over-engineer at this stage.
- Run the test again — it must pass.
3. IMPROVE — Refactor
- Clean up duplication, naming, structure.
- Keep all tests passing after each change.
- Check coverage: target ≥ 80%.
Test Layer Checklist
- Unit — pure functions, utilities, isolated components
- Integration — API endpoints, database operations, service boundaries
- E2E — at least one critical user flow covered
Quality Gates
Before marking the feature done:
- All tests pass
- Coverage ≥ 80%
- No skipped/commented-out tests
- Edge cases covered: empty input, nulls, boundary values, error paths
Anti-patterns to Avoid
- Writing implementation before tests
- Testing implementation details instead of behavior
- Mocking too deeply (prefer integration tests over excessive mocks)
- Assertions that always pass (
expect(true).toBe(true))
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 Changed · -19 lines · +1 tokens per session e69801884038
- 1mo ago First seen · 67 lines · 11 tokens per session scan A 0f57c5163f08
tdd is a command published in the GitHub repository affaan-m/ECC (284,130 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 357 once invoked, about $0.0000 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-03.
Other commands, from other repositories
agileteam
Orchestrate an autonomous, defense-in-depth TDD multi-agent team (requirements → spec-sanity gate → planner → coder/reviewer loop → verification/security/validation/judgment gates → human acceptance → retrospective) to build a feature end-to-end against fully verified, independently validated requirements.
tdd
A command for test-driven development, a method where you write a failing test first, then code to pass it, and finally improve the code.
test
Debug and fix failing tests using test-driven analysis and self-debugging methodology.
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
tdd
Run the test-driven development workflow: write failing tests first, then the minimal code to pass.