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-syncWrote 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-sync)<a href="https://agentmods.dev/commands/affaan-m/ecc/epic-sync"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/epic-sync/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/epic-sync"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/epic-sync.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.00015 | $0.00116 |
| Opus 5.5 | $0.00006 | $0.00046 |
| Sonnet 5.5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00002 | $0.00012 |
Grade A, and why
epic-sync 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
/epic-sync
Run a deterministic sync for epic issues.
node scripts/github-coordination.js sync --repo <owner/repo>
What this does:
- Reads issue bodies as the canonical epic state.
- Reconciles the coordination block with labels.
- Writes a fresh local snapshot for each epic issue.
- Keeps the SQLite cache aligned with GitHub.
Compatibility aliases:
/projects/work-items sync-github
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 · 24 lines · 15 tokens per session scan A b191bedc4bfa
epic-sync is a command published in the GitHub repository affaan-m/ECC (286,530 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 116 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-09-03.
Other commands, from other repositories
caveman-commit
Generate a terse caveman-style commit message for staged changes.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
amend-plan
Plan Amend - Discuss and apply amendments to a plan.json implementation plan.
portfolio-status
Review the health of all projects in the portfolio.
weekly-review
Produce a weekly review from the evidence in the repository and the workspace: commits and pull requests merged or open, issues closed and opened, decisions logged, research log entries, action items done and overdue, and what stalled, then a short plan for next week; written to a dated file so reviews accumulate. Use…
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.