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-quality-gate)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-quality-gate"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-quality-gate/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-quality-gate"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-quality-gate.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.00041 | $0.00775 |
| Opus 5.5 | $0.00016 | $0.00310 |
| Sonnet 5.5 | $0.00008 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
ccc-quality-gate 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 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.
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
89% identical to quality-gate — 61 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-quality-gate — format, lint and type checks on demand
CC Commander · /ccc-quality-gate · runs the checks the post-edit quality hooks run, on a scope you choose, and returns a remediation list.
Arguments
/ccc-quality-gate [path|.] [--fix] [--strict] — parsed from $ARGUMENTS:
[path|.]— target; defaults to the current directory--fix— allow auto-format and auto-fix where the tool supports it--strict— treat warnings as failures where the tool supports it
What happens
-
Detect tooling for the target. Prefer the project's own scripts in
package.json,pyproject.toml,Makefileorjustfileover the defaults below, and only run tools that are installed (command -v <tool>or a localnode_modules/.bin/<tool>). Record every tool that is configured but missing.Stack Formatter check ( --fixform)Lint / type check ( --strictform)JS/TS npx prettier --check <path>(--write) ornpx biome check <path>(--write)npx eslint <path>(--max-warnings 0;--fix),npx tsc --noEmitPython ruff format --check <path>(ruff format <path>) orblack --check <path>(black <path>)ruff check <path>(--fix),mypy <path>(--strictonly if the project config allows it)Go gofmt -l <path>(gofmt -w)go vet ./...,staticcheck ./...when installedRust cargo fmt --check(cargo fmt)cargo clippy(-- -D warnings)Shell — shellcheck <files> -
Run formatter checks. Without
--fix, run check-only forms. With--fix, run the write forms. -
Run lint and type checks. Apply
--strictflags only when--strictwas passed. Capture exit code and the first lines of each failure. -
Verify after
--fix. Re-run the check-only forms from steps 2 and 3, then show what changed:git status --short git diff --stat -
Report a remediation list grouped by severity: errors (non-zero exit), warnings, then missing tools. Each item is
path:line — rule — one-line fix.
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 · +19 lines · +20 tokens per session 5e1971da2dc6
- 1mo ago First seen · 34 lines · 21 tokens per session scan A aca199fd8f78
ccc-quality-gate is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 775 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to quality-gate, differing in 61 lines, and is treated as a copy.
Other commands, from other repositories
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
work-flow-bugfix
Complete workflow to fix a bug, from diagnosis to deployment.
dev-debug
Methodical and systematic bug diagnostic and resolution.
planning-triage
Quick-score an enhancement, bug, or feedback item using the impact-first triage framework. Creates an issue if approved.
p6-bugfix
Fixes bugs and vulnerabilities found during the QA phase (functional tests, exploratory tests, accessibility check, security audit, pentest). Each fix is secured by a regression test.