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 skills add KevinZai/commander --skill ccc-testinggit 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/skills/kevinzai/commander/ccc-testing)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-testing"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-testing/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/skills/kevinzai/commander/ccc-testing"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-testing.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.00068 | $0.01385 |
| Opus 5.5 | $0.00027 | $0.00554 |
| Sonnet 5.5 | $0.00014 | $0.00277 |
| Haiku 4.5 | $0.00007 | $0.00138 |
Grade A, and why
ccc-testing 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-testing — the right test lane
CC Commander · $ccc-testing · one entry to the testing domain; routes to the specialist lane and keeps test work out of your working tree.
When to use / when not to
- Use when the request is about writing, planning or running tests and the right specialist is not obvious.
- Go straight to
$ccc-qafor a QA pass over an existing suite, and to$ccc-e2efor a parallel pre-release assessment. - Use
$ccc-systematic-debuggingwhen a test fails and the cause is unknown.
What happens
1. Match the intent to a lane
An argument or a clear request picks the lane directly:
| Intent | Lane (toolkit sub-skill) | Plugin fallback |
|---|---|---|
| "Write tests first", TDD | tdd-workflow |
Red-green-refactor inline: write the failing test, run it and show the failure, implement, rerun to green |
| "E2E tests", Playwright | e2e-testing + webapp-testing |
$ccc-e2e e2e-only |
| "Verify my work", "is this done?" | verification-loop, then verification-before-completion |
Run the test, lint and build commands the project declares (package.json scripts, Makefile, pyproject.toml) with Bash and quote each exit status |
| "QA this", find and fix bugs | qa |
$ccc-qa |
| Find bugs, report only | qa-only |
$ccc-qa, stopping at the report |
| "What should I test?", test strategy | test-strategy |
qa-engineer agent: a strategy with test types, priorities and coverage targets |
| Visual regression, screenshot tests | visual-regression |
$ccc-e2e e2e-only |
| Load or performance testing | load-testing |
performance-engineer agent: k6 or Artillery script plus a baseline run plan |
| "Check for regressions" | ai-regression-testing |
$ccc-review quick on the diff, then $ccc-qa unit |
| Evals, eval-driven development | eval-harness |
For a Claude Code plugin: claude plugin eval . (scaffold with claude plugin eval init) |
| Python tests, pytest | python-testing |
$ccc-qa unit |
| Code quality while writing | plankton-code-quality |
$ccc-review quick |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +6 lines · +26 tokens per session 8db18f111908
- 1mo ago First seen · 92 lines · 42 tokens per session scan A 992fadea94bb
ccc-testing is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 1,385 once invoked, about $0.0003 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-03.
Other skills, from other repositories
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
tdd
Use before implementation when behavior can be verified by automated tests and regression coverage has clear value. For bugs with an unknown root cause, use systematic-debugging first, then return for red-green. Follow red-green-refactor—write a failing test first, add only enough code to pass it, then refactor. Do…
execute
Execute the next available tracked task with TDD, pre-commit validation, PR workflow, AI code review, and issue tracker bridge sync. Primary execution interface for multi-session feature work.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
tdd
Build this test-first, one behavior at a time: $ARGUMENTS.