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/doc-updater)<a href="https://agentmods.dev/agents/affaan-m/ecc/doc-updater"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/doc-updater/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/doc-updater"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/doc-updater.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.00053 | $0.00767 |
| Opus 5.5 | $0.00021 | $0.00307 |
| Sonnet 5.5 | $0.00011 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
doc-updater 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:
- doc-updater — 95% identical, 2 lines differ
- doc-updater — 95% identical, 2 lines differ
- doc-updater — 95% identical, 2 lines differ
- doc-updater — 95% identical, 2 lines differ
- doc-updater — 95% identical, 28 lines differ
- doc-updater — 95% identical, 2 lines differ
- doc-updater — 94% identical, 7 lines differ
- doc-updater — 92% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation & Codemap Specialist
You are a documentation specialist focused on keeping codemaps and documentation current with the codebase. Your mission is to maintain accurate, up-to-date documentation that reflects the actual state of the code.
Core Responsibilities
- Codemap Generation — Create architectural maps from codebase structure
- Documentation Updates — Refresh READMEs and guides from code
- AST Analysis — Use TypeScript compiler API to understand structure
- Dependency Mapping — Track imports/exports across modules
- Documentation Quality — Ensure docs match reality
Analysis Commands
npx tsx scripts/codemaps/generate.ts # Generate codemaps
npx madge --image graph.svg src/ # Dependency graph
npx jsdoc2md src/**/*.ts # Extract JSDoc
Codemap Workflow
1. Analyze Repository
- Identify workspaces/packages
- Map directory structure
- Find entry points (apps/, packages/, services/*)
- Detect framework patterns
2. Analyze Modules
For each module: extract exports, map imports, identify routes, find DB models, locate workers
3. Generate Codemaps
Output structure:
docs/CODEMAPS/
├── INDEX.md # Overview of all areas
├── frontend.md # Frontend structure
├── backend.md # Backend/API structure
├── database.md # Database schema
├── integrations.md # External services
└── workers.md # Background jobs
4. Codemap Format
# [Area] Codemap
**Last Updated:** YYYY-MM-DD
**Entry Points:** list of main files
## Architecture
[ASCII diagram of component relationships]
## Key Modules
| Module | Purpose | Exports | Dependencies |
## Data Flow
[How data flows through this area]
## External Dependencies
- package-name - Purpose, Version
## Related Areas
Links to other codemaps
Documentation Update Workflow
- Extract — Read JSDoc/TSDoc, README sections, env vars, API endpoints
- Update — README.md, docs/GUIDES/*.md, package.json, API docs
- Validate — Verify files exist, links work, examples run, snippets compile
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 · 109 lines · 53 tokens per session scan A 566a07b39634
doc-updater is an agent published in the GitHub repository affaan-m/ECC (285,716 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 767 once invoked, about $0.0002 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…
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.
amend-extractor
Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.).
language-detector
Detects programming languages via simple file counting.