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-loop-startgit 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-loop-start)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-loop-start"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-loop-start.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.00242 |
| Opus 5 | $0.00009 | $0.00121 |
| Sonnet 5 | $0.00004 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
ccc-loop-start 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.
This is a copy
91% identical to loop-start — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Loop Start Command
Start a managed autonomous loop pattern with safety defaults.
Usage
/loop-start [pattern] [--mode safe|fast]
pattern:sequential,continuous-pr,rfc-dag,infinite--mode:safe(default): strict quality gates and checkpointsfast: reduced gates for speed
Flow
- Confirm repository state and branch strategy.
- Select loop pattern and model tier strategy.
- Enable required hooks/profile for the chosen mode.
- Create loop plan and write runbook under
.claude/plans/. - Print commands to start and monitor the loop.
Required Safety Checks
- Verify tests pass before first loop iteration.
- Ensure
ECC_HOOK_PROFILEis not disabled globally. - Ensure loop has explicit stop condition.
Arguments
$ARGUMENTS:
<pattern>optional (sequential|continuous-pr|rfc-dag|infinite)--mode safe|fastoptional
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 · 37 lines · 18 tokens per session scan A 3bc7969696d7
ccc-loop-start is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 242 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to loop-start, differing in 4 lines, and is treated as a copy.
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).
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
adv-codex
Send a prompt to Codex CLI and return the response.
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]".