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/done)<a href="https://agentmods.dev/commands/cristhianzl/claude-skills-czl/done"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/done/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/done"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/done.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.00009 | $0.00197 |
| Opus 5 | $0.00005 | $0.00098 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
done 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
/done
Provided message: $ARGUMENTS.
Chains /review (quick) → /check → /commit. Stops immediately on any failure.
Quick review (over the diff)
Look for:
print()orconsole.log()in production code- Hardcoded credentials (tokens, passwords, URLs with auth)
.env*files in the diffdangerouslySetInnerHTMLwithout sanitizing- Python functions without type hints
- SQL with f-string instead of bind params
If you find something critical, STOP and report.
Check
Run lint and tests only on the areas with changes (see /check).
Commit
Follow /commit. Does not run git push (use /push).
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 · 33 lines · 9 tokens per session scan A 4a14d6b2d9f2
done is a command published in the GitHub repository Cristhianzl/claude-skills-czl (5 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 197 once invoked, about $0.0000 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
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
caveman-commit
Generate a terse caveman-style commit message for staged changes.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
pr
Create a branch, split changes into logical commits, and open a pull request.
quick-commit
Quick commit with automatic formatting, linting, and conventional commit message.