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 skills add affaan-m/ECC --skill docs-governancegit 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/skills/affaan-m/ecc/docs-governance)<a href="https://agentmods.dev/skills/affaan-m/ecc/docs-governance"><img src="https://agentmods.dev/badge/skills/affaan-m/ecc/docs-governance/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/skills/affaan-m/ecc/docs-governance"><img src="https://agentmods.dev/badge/skills/affaan-m/ecc/docs-governance.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.00067 | $0.00931 |
| Opus 5.5 | $0.00027 | $0.00372 |
| Sonnet 5.5 | $0.00013 | $0.00186 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
docs-governance 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Governance Router
Use this optional router to select the smallest existing ECC capability for a documentation-governance request. The router does not create a parallel project management system and does not make documentation authoritative over code, tests, Issues, or maintainer decisions.
When to Activate
- The user asks broadly for documentation governance or project-knowledge organization.
- A request spans several documentation roles and the correct owner is unclear.
- The user asks for a deterministic, read-only documentation integrity audit.
- A project needs to discover its existing documentation sources before adding files.
Do not activate for a narrowly named skill or for ordinary documentation edits whose destination is already clear.
Role Contract
Read the artifact-role contract before
interpreting .governance/docs-map.json or default filenames. Logical roles own
facts; filenames are fallbacks. Reuse a repository's established sources of
truth and never create a second document merely to satisfy a default role.
Intent Routing
| User intent | Route to |
|---|---|
| Adopt or maintain a constitution, map, status, and history spine | living-docs-governance |
| Record a hard-to-reverse architecture decision | architecture-decision-records |
| Preserve an executable regression for an important defect | ai-regression-testing (install separately in standalone Pi core) |
| Define a verifiable goal and feedback loop | loop-design-check (install separately in standalone Pi core) |
| Check mapped roles, local links, ADR indexes, TEST-IDs, or possible orphan docs | Run the bundled read-only audit |
If no row fits, explain the ownership ambiguity instead of combining several workflows speculatively.
Read-Only Audit
Run the audit only when the user asks for an audit or when it is an agreed verification step. Resolve the selected skill directory first, then invoke:
python3 <docs-governance-skill>/scripts/audit-docs.py --root <repository> --scope full
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 98 lines · 67 tokens per session scan A 499ac59071e6
docs-governance is a skill published in the GitHub repository affaan-m/ECC (280,368 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 931 once invoked, about $0.0003 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-10-10.
Other skills, from other repositories
kanban-video-orchestrator
Plan and run multi-agent video production pipelines.
sdlc-review
Review Kanban handoffs and route verified outcomes.
teams-meeting-pipeline
Teams meeting summaries, job replay, Graph subscriptions.
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
cl-analyze
Analyze one ClosedLoop feature ticket from a URL or FEA slug before execution. Use when asked to assess ticket complexity, feasibility, readiness, applicable requirements PRDs and missing PRD links, UI design guidance, human UI plan approval needs, blockers, legacy split lineage, merge-batch compatibility, nonsensical…