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/checkpointgit 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/checkpoint)<a href="https://agentmods.dev/commands/affaan-m/ecc/checkpoint"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/checkpoint.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 | $0.00006 | $0.00329 |
| Opus 5 | $0.00003 | $0.00164 |
| Sonnet 5 | $0.00001 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
checkpoint 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 yesterday.
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:
- checkpoint — 100% identical, 2 lines differ
- checkpoint — 98% identical, 2 lines differ
- checkpoint — 97% identical, 2 lines differ
- checkpoint — 94% identical, 2 lines differ
- checkpoint — 94% identical, 2 lines differ
- checkpoint — 94% identical, 2 lines differ
- checkpoint — 94% identical, 2 lines differ
- checkpoint — 94% identical, 2 lines differ
What it actually says
Checkpoint Command
Save current verification state and create progress checkpoint: $ARGUMENTS
Your Task
Create a snapshot of current progress including:
- Tests status - Which tests pass/fail
- Coverage - Current coverage metrics
- Build status - Build succeeds or errors
- Code changes - Summary of modifications
- Next steps - What remains to be done
Checkpoint Format
Checkpoint: [Timestamp]
Tests
- Total: X
- Passing: Y
- Failing: Z
- Coverage: XX%
Build
- Status: PASS: Passing / FAIL: Failing
- Errors: [if any]
Changes Since Last Checkpoint
git diff --stat [last-checkpoint-commit]
Completed Tasks
- Task 1
- Task 2
- Task 3 (in progress)
Blocking Issues
- [Issue description]
Next Steps
- Step 1
- Step 2
Usage with Verification Loop
Checkpoints integrate with the verification loop:
/plan → implement → /checkpoint → /verify → /checkpoint → implement → ...
Use checkpoints to:
- Save state before risky changes
- Track progress through phases
- Enable rollback if needed
- Document verification points
TIP: Create checkpoints at natural breakpoints: after each phase, before major refactoring, after fixing critical bugs.
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.
- yesterday First seen · 68 lines · 6 tokens per session scan A 17c275584724
checkpoint is a command published in the GitHub repository affaan-m/ECC (246,988 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 329 once invoked, about $0.0000 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
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
gh-triage
GitHub OSS maintainer lifecycle triage, review, and approval management.
fire-3-execute
Execute a phase with breath-based parallelism and honesty protocols.
fire-todos
Capture, list, and manage todos during work sessions.
fire-execute-plan
Execute a single plan with segment-based routing, per-task atomic commits, and test enforcement.
init
Initialize goal-flight state for a project.