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 skills/kevinzai/commander/ccc-testingnpx 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.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.1 | $0.00042 | $0.00952 |
| Opus 5 | $0.00021 | $0.00476 |
| Sonnet 5 | $0.00008 | $0.00190 |
| Haiku 4.5 | $0.00004 | $0.00095 |
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 2d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ccc-testing
Load ONE skill. Get the entire testing domain. 15 skills in one.
Default isolation: worktree — test dispatches run in an isolated worktree to avoid polluting the working tree.
What's Inside
| Category | Skills |
|---|---|
| Foundation | testing-router, test-strategy |
| Unit & TDD | tdd-workflow, plankton-code-quality, python-testing |
| Integration & E2E | e2e-testing, webapp-testing |
| Visual & Performance | visual-regression, load-testing |
| Quality Assurance | qa, qa-only, ai-regression-testing |
| Verification | verification-loop, verification-before-completion, eval-harness |
No expressed intent? Present the top 3 sub-skills + "More…" as an AskUserQuestion picker (≤4 options).
Routing Matrix
| Your Intent | Route To |
|---|---|
| "Write tests first" / "TDD" | tdd-workflow |
| "E2E tests" / "Playwright" | e2e-testing + webapp-testing |
| "Verify my work" / "Is this done?" | verification-loop |
| "QA this" / "Find bugs and fix" | qa |
| "Find bugs but don't fix" | qa-only |
| "Test strategy" / "What should I test?" | test-strategy |
| "Visual regression" / "Screenshot tests" | visual-regression |
| "Load testing" / "Performance test" | load-testing |
| "Check for regressions" | ai-regression-testing |
| "Build evals" / "Eval-driven" | eval-harness |
| "Python tests" / "pytest" | python-testing |
Campaign Templates
Full Testing Strategy (New Project)
test-strategy→ analyze project, recommend test types + coverage targetstdd-workflow→ set up framework, write first testse2e-testing→ critical user flow testsvisual-regression→ screenshot baselinesload-testing→ performance benchmarksverification-loop→ verify everything passes
Bug Fix with Tests (TDD Protocol)
qaorqa-only→ identify the bugtdd-workflow→ write failing test reproducing the bug- Fix → test goes green
ai-regression-testing→ check for related regressionsverification-before-completion→ prove the fix works
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.
- 2d 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 42 tokens to every session and 952 once invoked, about $0.0002 per session on Opus 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
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
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.
test-first
Drive one feature through a strict TDD Red-Green-Refactor cycle with checklists for each phase. Use when implementing new functionality test-first, or when the user runs /test-first.
linked-intent-dev
Guide for linked-intent development (LID). Consult for ALL code changes. Walks changes through a mode-aware six-phase workflow (HLD → LLD → EARS → intent-narrowing edge audit → tests-first → code) with mandatory stops between each phase. Bugs walk the arrow like any other change — no short-circuit. Enforces cascade…
plan
Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.
write-e2e
Generate Playwright E2E tests from codebase analysis. Discovers routes, scores user flows by criticality, writes .spec.ts files that assert causality, and reports what was actually proven: GENERATED, STATICCHECKED, VERIFIEDLOCAL or VALIDATEDLIVE. Modes: --scope , --flow , --output , --base-url , --max-flows N, --live…