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/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-complete)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-complete"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-complete/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/kevinzai/commander/ccc-complete"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-complete.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.00035 | $0.00688 |
| Opus 5.5 | $0.00014 | $0.00275 |
| Sonnet 5.5 | $0.00007 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
ccc-complete scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -o /dev/null -w '%{http_code}\n' -X PATCH "$TASK_TRACKER_URL/api/issues/$ISSUE_ID" \ How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-complete — signal delegated task done
CC Commander · /ccc-complete · a completion report the delegating orchestrator can read, plus an opt-in tracker update.
Usage
/ccc-complete [summary of what was done]
The summary is $ARGUMENTS. If it is empty, draft one from steps 1 and 2.
What happens
-
Gather evidence of the finished work:
git status --short git log --oneline -10Read the project's
tasks/todo.mdif it exists and note which items this task completed. -
Run the project's verification command (the test or check script named in
package.json,Makefileor the projectCLAUDE.md, for examplenpm test). Record pass or fail with the actual output line. Do not report the task as complete when it fails; report it as blocked with the failing line. -
If the task references a tracker issue id (for example
ABC-123) and the user has configured a tracker endpoint inTASK_TRACKER_URL, ask with AskUserQuestion (Codex: a plain-text question) at this moment:- 🟢 Mark the issue done — sends the summary as a comment and sets status
done - Comment only — posts the summary, leaves the status unchanged
- Skip the tracker — the report stays local
On a yes, send the update and check the response code:
curl -sS -o /dev/null -w '%{http_code}\n' -X PATCH "$TASK_TRACKER_URL/api/issues/$ISSUE_ID" \ -H "Content-Type: application/json" \ -d '{"status": "done", "comment": "Completed: <summary>"}'A
2xxcode is success. Any other code: report it and leave the issue unchanged. IfTASK_TRACKER_URLis unset or the tracker uses a different API, skip this step and say so; use the tracker's own tool (for example/ccc-linear) instead. - 🟢 Mark the issue done — sends the summary as a comment and sets status
-
Write the completion report to stdout:
TASK COMPLETE Summary: <one line> Changed: <files, or "none"> Tests: <command> — <pass/fail> Commits: <short hashes, or "uncommitted"> Tracker: <issue id and HTTP code, or "not updated">
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.
- 5d ago Changed · +43 lines · +16 tokens per session 87bc3ccaf847
- 1mo ago First seen · 27 lines · 19 tokens per session scan A fc4de33f4e84
ccc-complete is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 688 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
phase
Orchestrate a full roadmap phase. Designs features, imports to tracker, creates issues, then executes.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
sync
Reconcile coco tracker state with the configured issue tracker. Syncs task statuses and reports mismatches.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
status
Show current execution status with progress, dependencies, file ownership, and parallelization opportunities.