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/kevinzai/commander/ccc-retrogit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/ccc-retro)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-retro"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-retro.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.00018 | $0.00894 |
| Opus 5 | $0.00009 | $0.00447 |
| Sonnet 5 | $0.00004 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
ccc-retro 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 today.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro — Productivity Retrospective
Inspired by gstack by Garry Tan
You are generating a productivity retrospective report for the current project.
Parse Period
Determine the time range from {{input}}:
- Empty or
week→ last 7 days sprint→ last 14 daysmonth→ last 30 daysYYYY-MM-DD..YYYY-MM-DD→ explicit date range
Set $SINCE and $UNTIL accordingly (e.g. --since="7 days ago").
Gather Data
Run these in parallel:
1. Git History
git log --since="$SINCE" --oneline --stat
git shortlog -sn --since="$SINCE"
git log --since="$SINCE" --format="%H" | wc -l
git diff --stat $(git log --since="$SINCE" --reverse --format="%H" | head -1)^..HEAD 2>/dev/null
2. Change Hotspots
git log --since="$SINCE" --name-only --format="" | sort | uniq -c | sort -rn | head -10
git log --since="$SINCE" --name-only --format="" | xargs -I{} dirname {} | sort | uniq -c | sort -rn | head -5
3. Session Data
- Check
~/.claude/sessions/for session files modified within the period - Count total sessions and estimate duration from file timestamps if possible
- Look for cost data in session metadata (model usage, token counts)
Generate Report
Output the report using this structure:
RETRO: [period description]
Project: [repo name]
Branch: [current branch]
Period: [start date] → [end date]
Shipping Summary
| Metric | Value |
|---|---|
| Total commits | N |
| Files changed | N |
| Lines added | +N |
| Lines removed | -N |
| Net LOC | +/-N |
| Contributors | N |
What shipped — group commits by conventional commit type:
- feat: list key features
- fix: list key fixes
- refactor: list refactors
- docs/test/chore: summarize briefly
Productivity Metrics
| Metric | Value |
|---|---|
| Avg commits/day | N |
| Most active day | [day, count] |
| Largest commit | [hash — summary, +/-N lines] |
Most changed files (top 5):
path/to/file— N changes- ...
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.
- today First seen · 122 lines · 18 tokens per session scan A 1f7a50807b35
ccc-retro is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 894 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-04.
Other commands, from other repositories
debug
Systematic debugging with hypotheses and evidence gathering.
review
Run a Codex code review of your working tree or a branch (read-only).
adv-codex
Send a prompt to Codex CLI and return the response.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
planning-triage
Quick-score an enhancement, bug, or feedback item using the impact-first triage framework. Creates an issue if approved.
add-hook
Add a new hook to .claude/settings.json. Quick operation, no full interview needed. Trigger phrases: "add hook", "auto-format on save", "run tests after edit", "lint on write", "run [command] after [tool]".