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-pr)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-pr"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-pr/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-pr"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-pr.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.00034 | $0.00635 |
| Opus 5.5 | $0.00014 | $0.00254 |
| Sonnet 5.5 | $0.00007 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
ccc-pr 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-pr — pull request for the current branch
CC Commander · /ccc-pr · commits, tests, pushes and opens a PR with gh, then reports the URL.
Arguments: $ARGUMENTS (optional: PR title override, target branch).
What happens
-
Inspect the branch:
gh auth status git branch --show-current git status --short git remote show origin | sed -n 's/.*HEAD branch: //p'The last line is the default base; a target branch in
$ARGUMENTSoverrides it. If the current branch is the base branch, stop and offer to create a feature branch first. -
If there are uncommitted changes, show them and ask with AskUserQuestion:
- 🟢 Commit them — stages the listed files by name and commits with a conventional message.
- Leave them out — opens the PR from existing commits only.
- Cancel — nothing is committed or pushed.
git add <file> <file> git commit -m "<type>: <description>" -
If the project has tests, run them (take the command from
package.jsonscripts or the project's CLAUDE.md) and keep the actual result for the PR body. A failure goes in the body as a failure; ask whether to continue. -
Push:
git push -u origin "$(git branch --show-current)" -
Build the PR:
- Title: the
$ARGUMENTSoverride, else the last commit subject, else the branch name. - Body: summary of changes, files modified (from
git diff --stat <base>...HEAD), test command and result. - Labels: detect from changed paths (frontend, backend, docs, and so on); apply only labels that already exist in the repository (
gh label list).
gh pr create --base <base> --title "<title>" --body-file <body-file> --label <label> - Title: the
-
Verify and report:
gh pr view --json url,state,baseRefName,headRefNameOutput the PR URL from this command.
Done when
gh pr view returns the PR in OPEN state and its URL is reported.
Guardrails
- Invoking
/ccc-prauthorizes the push and PR for this branch only; ask before committing changes the user has not seen. - Never push to the base branch, force-push, or skip hooks with
--no-verify. - Stage files by name; never
git add -Aon a tree with unrelated 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.
- 6d ago Changed · +56 lines · +14 tokens per session a3001974ed20
- 1mo ago First seen · 18 lines · 20 tokens per session scan A 960f62509fd0
ccc-pr is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 635 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
commit
Split the changes into atomic commits, preflight and push them. Pass --skip-preflight or --no-push to skip a step.
autocommit
Toggle auto git commits on/off for this project. Run without args to see status, or with "on"/"off" to set.
commit-message
Generate a conventional commit message from staged changes.