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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/affaan-m/ECCnpx agentmods add commands/affaan-m/ecc/epic-decomposeWrote 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/epic-decompose)<a href="https://agentmods.dev/commands/affaan-m/ecc/epic-decompose"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/epic-decompose.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.00011 | $0.00117 |
| Opus 5 | $0.00005 | $0.00059 |
| Sonnet 5 | $0.00002 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
epic-decompose 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 3d 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
/epic-decompose
Reconcile the task breakdown for one epic issue.
node scripts/github-coordination.js decompose <issue-number> --repo <owner/repo>
What this does:
- Reads the epic issue body for task checklists and dependency references.
- Stores the decomposition in the coordination block.
- Leaves task branches out of the workflow.
- Appends a concise audit comment.
Compatibility aliases:
/plan/prp-plan
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.
- 3d ago First seen · 24 lines · 11 tokens per session scan A cc5ddee38eb6
epic-decompose is a command published in the GitHub repository affaan-m/ECC (251,781 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 117 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
dev
You are an experienced Tech Lead overseeing multiple AI Worker Agents on software projects. The user is the PM / product owner. You drive all technical execution and communicate in natural language.
t00-new-pj
A command for starting a new T00 project by asking planning questions, assigning a project number, creating a folder and project file, and updating the project index. T00 appears to be a local project-management setup.
t00-estimate
A command that estimates whether a requested software task is practical before implementation and reports what was completed afterward. It uses different report formats depending on whether the user asks to start work or review the result.
t00-status
A status-report command for a T00 task workspace, using files that record communication, tasks, and the previous session's next steps.
t00-pj-status
A command that reads project files and lists the status and next step for each active project. You can also request a detailed to-do list for one project.
org-status
Show the org at a glance — roles, folder counts, drift (unmapped/missing folders), adoption progress, and which role brains are stale or have pending activity due for /role-promote.