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.
npx agentmods add commands/affaan-m/ecc/test-coveragegit 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/test-coverage)<a href="https://agentmods.dev/commands/affaan-m/ecc/test-coverage"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/test-coverage.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.00005 | $0.00427 |
| Opus 5 | $0.00003 | $0.00214 |
| Sonnet 5 | $0.00001 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
test-coverage 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 2d 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:
- test-coverage — 100% identical, 0 lines differ
- test-coverage — 100% identical, 0 lines differ
- test-coverage — 100% identical, 0 lines differ
- test-coverage — 100% identical, 0 lines differ
- test-coverage — 94% identical, 2 lines differ
- test-coverage — 92% identical, 2 lines differ
- test-coverage — 92% identical, 2 lines differ
What it actually says
Test Coverage Command
Analyze test coverage and identify gaps: $ARGUMENTS
Your Task
- Run coverage report:
npm test -- --coverage - Analyze results - Identify low coverage areas
- Prioritize gaps - Critical code first
- Generate missing tests - For uncovered code
Coverage Targets
| Code Type | Target |
|---|---|
| Standard code | 80% |
| Financial logic | 100% |
| Auth/security | 100% |
| Utilities | 90% |
| UI components | 70% |
Coverage Report Analysis
Summary
File | % Stmts | % Branch | % Funcs | % Lines
---------------|---------|----------|---------|--------
All files | XX | XX | XX | XX
Low Coverage Files
[Files below target, prioritized by criticality]
Uncovered Lines
[Specific lines that need tests]
Test Generation
For each uncovered area:
[Function/Component Name]
Location: src/path/file.ts:123
Coverage Gap: [description]
Suggested Tests:
describe('functionName', () => {
it('should [expected behavior]', () => {
// Test code
})
it('should handle [edge case]', () => {
// Edge case test
})
})
Coverage Improvement Plan
-
Critical (add immediately)
- file1.ts - Auth logic
- file2.ts - Payment handling
-
High (add this sprint)
- file3.ts - Core business logic
-
Medium (add when touching file)
- file4.ts - Utilities
IMPORTANT: Coverage is a metric, not a goal. Focus on meaningful tests, not just hitting numbers.
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.
- 2d ago First seen · 81 lines · 5 tokens per session scan A bb3542aeec9d
test-coverage is a command published in the GitHub repository affaan-m/ECC (248,541 stars, last pushed yesterday), licensed MIT. It adds 5 tokens to every session and 427 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
write-fixtures
../../skills/write-fixtures/SKILL.md.
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
test
Generate comprehensive tests.
test
运行测试并分析失败原因.
fix-test
Auto-diagnose and fix failing tests — identifies root causes and applies fixes.