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 huuanh20/awesome-ai-agent-skills --skill ck-testgit clone --depth 1 https://github.com/huuanh20/awesome-ai-agent-skillsWrote 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/huuanh20/awesome-ai-agent-skills/ck-test)<a href="https://agentmods.dev/skills/huuanh20/awesome-ai-agent-skills/ck-test"><img src="https://agentmods.dev/badge/skills/huuanh20/awesome-ai-agent-skills/ck-test/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/huuanh20/awesome-ai-agent-skills/ck-test"><img src="https://agentmods.dev/badge/skills/huuanh20/awesome-ai-agent-skills/ck-test.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.00151 | $0.01716 |
| Opus 5 | $0.00076 | $0.00858 |
| Sonnet 5 | $0.00030 | $0.00343 |
| Haiku 4.5 | $0.00015 | $0.00172 |
Grade A, and why
ck:test 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 12d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ck:test — Standalone Verification & TDD Orchestration
ck:test owns all verification. It never touches production code and never calls ck:fix itself — a failure always hands control back to the user.
Modes (pick exactly one; --tdd further requires --prepare or --verify):
- default
<plan-or-phase>— analyze the changed scope, write any missing tests, run the relevant unit + integration suites. --unit <target>/--integration <target>/--e2e <target>— run only that test type against<target>.--all <target>— run every applicable suite for<target>'s scope (not necessarily the whole repo).--verify <target>— rerun exactly the tests that previously failed, plus directly related regression tests; does not redesign the suite.--all-phases <plan-path>— regression sweep across every already-completed phase in the plan.--tdd --prepare <phase-file>— write failing tests beforeck:cookimplements anything; confirm RED (failure is due to missing implementation, not a broken test); save aRED_READYartifact.--tdd --verify <phase-file>— afterck:cookimplements, rerun; confirm GREEN plus regression; detect tests that were weakened, deleted, or modified to dodge a failure rather than fixed by the implementation.
Step 1 — Quality Gate Check
Skip only for --tdd --prepare, or for --unit/--tdd --verify explicitly orchestrated by the active ck:cook phase after its Phase Checkpoint recorded tests=yes. This scoped exception lets tests and quality remain independent user choices; it does not apply to standalone test requests.
For every other mode, resolve the phase(s) in scope and verify each has a valid, current quality receipt:
python {ck-quality-skill-root}/scripts/receipt.py verify plans/{slug}/quality/{phase}-receipt.json
Resolve {ck-quality-skill-root} from the installed ck:quality skill directory for the active client; do not hardcode skills/ or .claude/skills/.
A missing or invalid receipt stops the run before any test is written or executed:
What ships with it
2 files 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.
- 12d ago First seen · 101 lines · 151 tokens per session scan A 793bac36bef9
ck:test is a skill published in the GitHub repository huuanh20/awesome-ai-agent-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 151 tokens to every session and 1,716 once invoked, about $0.0008 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-08-31.
Other skills, from other repositories
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
laravel-tdd
Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.
testing
TDD/BDD testing principles. Use when writing tests, reviewing test coverage, setting up testing, or discussing test strategy and test architecture.