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/eval)<a href="https://agentmods.dev/commands/affaan-m/ecc/eval"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/eval/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/eval"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/eval.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.00005 | $0.00445 |
| Opus 5.5 | $0.00002 | $0.00178 |
| Sonnet 5.5 | $0.00001 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
eval 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
8 near-identical copies found in the catalogue:
What it actually says
Eval Command
Evaluate implementation against acceptance criteria: $ARGUMENTS
Your Task
Run structured evaluation to verify the implementation meets requirements.
Evaluation Framework
Grader Types
-
Binary Grader - Pass/Fail
- Does it work? Yes/No
- Good for: feature completion, bug fixes
-
Scalar Grader - Score 0-100
- How well does it work?
- Good for: performance, quality metrics
-
Rubric Grader - Category scores
- Multiple dimensions evaluated
- Good for: comprehensive review
Evaluation Process
Step 1: Define Criteria
Acceptance Criteria:
1. [Criterion 1] - [weight]
2. [Criterion 2] - [weight]
3. [Criterion 3] - [weight]
Step 2: Run Tests
For each criterion:
- Execute relevant test
- Collect evidence
- Score result
Step 3: Calculate Score
Final Score = Σ (criterion_score × weight) / total_weight
Step 4: Report
Evaluation Report
Overall: [PASS/FAIL] (Score: X/100)
Criterion Breakdown
| Criterion | Score | Weight | Weighted |
|---|---|---|---|
| [Criterion 1] | X/10 | 30% | X |
| [Criterion 2] | X/10 | 40% | X |
| [Criterion 3] | X/10 | 30% | X |
Evidence
Criterion 1: [Name]
- Test: [what was tested]
- Result: [outcome]
- Evidence: [screenshot, log, output]
Recommendations
[If not passing, what needs to change]
Pass@K Metrics
For non-deterministic evaluations:
- Run K times
- Calculate pass rate
- Report: "Pass@K = X/K"
TIP: Use eval for acceptance testing before marking features complete.
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 · 89 lines · 5 tokens per session scan A b090a6524c94
eval is a command published in the GitHub repository affaan-m/ECC (283,276 stars, last pushed 4d ago), licensed MIT. It adds 5 tokens to every session and 445 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
t00-playwright-test
A command for testing a locally running web app in a real browser with Playwright, a browser automation and testing tool. It checks normal user flows and selected edge cases, then reports results with screenshots.
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.
openrouter-live-smoke
Run an honest, credit-careful, key-safe LIVE real-boundary smoke against OpenRouter (a single model via councilinference, a council via deepseekreview preset, or the GUI proxy). Probe reachability first, gate the live call, leak-check the key, capture honest attrition, and record real-boundary-smoke in the reality…
bench-oracle
Empirically measure an agent/prompt/process change instead of asserting it works — build a task corpus, run a deterministic mutation oracle (sabotage the code, see which tests catch it), and write an honest report including negative results. Use to compare two agent variants (e.g. baseline vs. a DNA/prompt change) or…
export-closedloop-learnings
Exports pending ClosedLoop learnings to global location with deduplication.
verify
Run lint, type-check, tests, and a security scan before committing.