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/verify)<a href="https://agentmods.dev/commands/cristhianzl/claude-skills-czl/verify"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/verify/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/verify"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/verify.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.00032 | $0.00339 |
| Opus 5 | $0.00016 | $0.00169 |
| Sonnet 5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
verify 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.
What it actually says
Run the project's checks in order and report a short verdict. This is a gate you invoke (not an automatic block) — run it before declaring a task done or opening a PR.
Use the project's actual commands (e.g. uv run … where the repo requires it). Run in this order; stop at the first hard failure and report it:
- Build — the project builds/compiles cleanly.
- Types — type checker passes (0 errors).
- Lint / format — linter and formatter clean.
- Tests — full suite green; branch coverage meets the gate.
- Secrets / debug scan — no secrets or credentials, no debug
print()/console.log, no.envin the diff. - Diff self-review — re-read the whole diff: every change is intended, no leftover scaffolding or stray
TODO, docs updated if behavior changed (theStopdoc-sync check helps here). - Runtime validation (when a server / user-provided cURL applies) — prove it against the live system per
skills/validating-in-reality: run the acceptance request, check DB state, E2E the UI flow. Static gates green + runtime proof = done.
Report a one-line PASS/FAIL per step and an overall verdict. On any FAIL, name the step and the fix — don't claim done. Never run git.
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 · 18 lines · 32 tokens per session scan A 239c4768a8e1
verify is a command published in the GitHub repository Cristhianzl/claude-skills-czl (5 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 339 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-08-31.
Other commands, from other repositories
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.
evaluate
Execute Evaluate stage to validate generated framework artifacts.
generate-tests
Generate comprehensive tests for specified code.
color-palette
Generate an accessible colour palette from a hex value.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
verify
Run lint, type-check, tests, and a security scan before committing.