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/verify)<a href="https://agentmods.dev/commands/affaan-m/ecc/verify"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/verify/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/verify"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/verify.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.00006 | $0.00399 |
| Opus 5.5 | $0.00002 | $0.00160 |
| Sonnet 5.5 | $0.00001 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
verify 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
Verify Command
Run verification loop to validate the implementation: $ARGUMENTS
Your Task
Execute comprehensive verification:
- Type Check:
npx tsc --noEmit - Lint:
npm run lint - Unit Tests:
npm test - Integration Tests:
npm run test:integration(if available) - Build:
npm run build - Coverage Check: Verify 80%+ coverage
Verification Checklist
Code Quality
- No TypeScript errors
- No lint warnings
- No console.log statements
- Functions < 50 lines
- Files < 800 lines
Tests
- All tests passing
- Coverage >= 80%
- Edge cases covered
- Error conditions tested
Security
- No hardcoded secrets
- Input validation present
- No SQL injection risks
- No XSS vulnerabilities
Build
- Build succeeds
- No warnings
- Bundle size acceptable
Verification Report
Summary
- Status: PASS: PASS / FAIL: FAIL
- Score: X/Y checks passed
Details
| Check | Status | Notes |
|---|---|---|
| TypeScript | PASS:/FAIL: | [details] |
| Lint | PASS:/FAIL: | [details] |
| Tests | PASS:/FAIL: | [details] |
| Coverage | PASS:/FAIL: | XX% (target: 80%) |
| Build | PASS:/FAIL: | [details] |
Action Items
[If FAIL, list what needs to be fixed]
NOTE: Verification loop should be run before every commit and PR.
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 · 68 lines · 6 tokens per session scan A ce51914ed79f
verify is a command published in the GitHub repository affaan-m/ECC (284,906 stars, last pushed today), licensed MIT. It adds 6 tokens to every session and 399 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
fix-test
Auto-diagnose and fix failing tests — identifies root causes and applies fixes.
p5-bugfix
Systematically analyzes a found bug, identifies the root cause and fixes it with an accompanying regression test. Goal: the bug is fixed, secured by a test, and cannot be silently reintroduced.
svelte:test-fix
Troubleshoot and fix failing tests in Svelte/SvelteKit projects, including debugging test issues and resolving common testing problems.
test-suite
Run comprehensive test suite with coverage analysis.
debug
Systematic root-cause investigation, then fix with TDD — never proposes a fix before finding the cause; resumable diagnosis + regression test in .orc/ state. Workspace-aware. For a quick one-off look without session state, prefer the bundled /debug.
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.