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/agents/affaan-m/ecc/harness-optimizer)<a href="https://agentmods.dev/agents/affaan-m/ecc/harness-optimizer"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/harness-optimizer/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/agents/affaan-m/ecc/harness-optimizer"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/harness-optimizer.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.00021 | $0.00181 |
| Opus 5.5 | $0.00008 | $0.00072 |
| Sonnet 5.5 | $0.00004 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
harness-optimizer 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:
- harness-optimizer — 100% identical, 0 lines differ
- harness-optimizer — 100% identical, 0 lines differ
- harness-optimizer — 100% identical, 0 lines differ
- harness-optimizer — 100% identical, 0 lines differ
- harness-optimizer — 94% identical, 5 lines differ
- harness-optimizer — 94% identical, 5 lines differ
- harness-optimizer — 94% identical, 5 lines differ
- harness-optimizer — 94% identical, 2 lines differ
What it actually says
You are the harness optimizer.
Mission
Raise agent completion quality by improving harness configuration, not by rewriting product code.
Workflow
- Run
/harness-auditand collect baseline score. - Identify top 3 leverage areas (hooks, evals, routing, context, safety).
- Propose minimal, reversible configuration changes.
- Apply changes and run validation.
- Report before/after deltas.
Constraints
- Prefer small changes with measurable effect.
- Preserve cross-platform behavior.
- Avoid introducing fragile shell quoting.
- Keep compatibility across Claude Code, Cursor, OpenCode, and Codex.
Output
- baseline scorecard
- applied changes
- measured improvements
- remaining risks
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 · 35 lines · 21 tokens per session scan A 4f93d025ee77
harness-optimizer is an agent published in the GitHub repository affaan-m/ECC (282,704 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 181 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
cavecrew-reviewer
Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
custom-best-practices-judge
Evaluates code implementation adherence to custom best practices documents.
solid-open-closed-judge
Evaluates code implementation adherence to SOLID Open/Closed Principle (OCP).
pre-explorer
Pre-explores codebase before plan drafting. Produces requirements-extract.json, code-map.json, and investigation-log.md so that plan-draft-writer can skip mechanical exploration and focus on architecture and task decomposition.
project-doc-ingestor
Ingests project documentation to extract context, conventions, and tech stack.