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/ecc-guidegit 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/ecc-guide)<a href="https://agentmods.dev/commands/affaan-m/ecc/ecc-guide"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/ecc-guide.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.00023 | $0.00698 |
| Opus 5 | $0.00012 | $0.00349 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
ecc-guide 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
1 near-identical copy found in the catalogue:
- ecc-guide — 94% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ecc-guide
Use this command as a conversational map of Everything Claude Code. It should help the user discover the right ECC surface for their task without dumping the entire README or stale catalog counts.
Usage
/ecc-guide
/ecc-guide setup
/ecc-guide skills
/ecc-guide commands
/ecc-guide hooks
/ecc-guide install
/ecc-guide find: <query>
/ecc-guide <feature-or-file-name>
Operating Rules
- Read current repository files before answering when the checkout is available.
- Prefer current filesystem/catalog data over hard-coded counts.
- Keep the first answer short, then offer specific drill-down paths.
- Link users to canonical files instead of copying long sections.
- Do not invent commands, skills, agents, or install profiles that are not present.
What To Inspect
Use these files as the canonical map:
README.mdfor install paths, reset/uninstall guidance, and high-level positioningAGENTS.mdfor contributor and project-structure guidanceagent.yamlfor exported agent and command surfacecommands/for maintained slash-command shimsskills/*/SKILL.mdfor reusable skill workflowsagents/*.mdfor delegated agent roleshooks/README.mdandhooks/hooks.jsonfor hook behaviormanifests/install-*.jsonfor selective install modules, components, and profilesscripts/ci/catalog.js --jsonfor live catalog counts when running inside ECC
Response Patterns
No Arguments
Give a compact menu:
- setup and install
- choosing skills
- command compatibility shims
- agents and delegation
- hooks and safety
- troubleshooting an install
- finding a specific feature
Then ask what they want to do next.
Topic Lookup
For topics like skills, commands, hooks, install, or agents:
- Summarize the current surface in 3-6 bullets.
- Point to the canonical directories/files.
- Suggest one or two commands that can verify the state.
- Avoid exhaustive lists unless the user asks for one.
Search Mode
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 · 94 lines · 23 tokens per session scan A 1d1a16c9d034
ecc-guide is a command published in the GitHub repository affaan-m/ECC (250,130 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 698 once invoked, about $0.0001 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
explain
Explain code, concepts, or system behavior with adjustable depth levels.
explain
Generate an interactive one-module explainer for a topic — Riko gathers code scope, Senku plans a 3-5 screen teaching arc, Speedwagon authors the HTML, assembler produces explain-out/index.html.
t00-perf-check
检查 Claude 效率配置：自动加载量、token 估算、skills、hooks，输出优化建议.
t00-playwright-test
Playwright UI 测试 — 在真实浏览器中测试本地运行的 Web App，验证登录流程、功能路径、边缘案例。PJ90 等前端项目适用。.
t00-rules-check
检查 T00 规则是否符合 L1-L4 优先级系统，输出合规报告和优化建议.
t00-hot
热点话题搜索 — 查找当前热门话题，帮助发现产品创意和用户痛点。.