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/Cristhianzl/claude-skills-czlWrote 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/cristhianzl/claude-skills-czl/test)<a href="https://agentmods.dev/commands/cristhianzl/claude-skills-czl/test"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/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/commands/cristhianzl/claude-skills-czl/test"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/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.00007 | $0.00105 |
| Opus 5.5 | $0.00003 | $0.00042 |
| Sonnet 5.5 | $0.00001 | $0.00021 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
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 1mo 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.
What it actually says
/test
Steps:
- List changes:
git diff --name-only HEAD - Map each changed source file to its test by the project's convention
- Run only the relevant tests
- If any fail, show the error and suggest a fix
- If there is no test for a modified file, warn about it
Commands
<test command> <paths or pattern>
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.
- 1mo ago First seen · 21 lines · 7 tokens per session scan A 2eca2b453778
test is a command published in the GitHub repository Cristhianzl/claude-skills-czl (5 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 105 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
review-pr
Review a pull request or the current branch with four specialist agents in parallel (code-reviewer for correctness and security, silent-failure-hunter, test-gap-analyzer, type-design-reviewer), then merge their findings into one severity-ranked review with file:line anchors and no duplicates, optionally posted to the…
write-tests
Generate a focused, production-quality test suite for a source file, detecting the project's existing test runner and conventions. Use when a source file needs a test suite that matches the project's existing conventions.
feature
Take a feature from a one-line description to a reviewed, tested change through a fixed pipeline: orient with the code-explorer agent, clarify requirements, write a task-by-task plan with the writing-plans skill, execute it with test-driven development, simplify with the code-simplifier agent, verify completion, and…
test-strategy
Write a test strategy as Markdown in the user's repository. Produce designed HTML or PDF only when asked.
evaluate
Execute Evaluate stage to validate generated framework artifacts.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.