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/commit)<a href="https://agentmods.dev/commands/cristhianzl/claude-skills-czl/commit"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/commit/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/commit"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/commit.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.00015 | $0.00260 |
| Opus 5 | $0.00008 | $0.00130 |
| Sonnet 5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
commit 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 9d 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
/commit
Provided message: $ARGUMENTS (use it directly if not empty).
Flow:
- Detect modified areas (
git diff --name-only) - Run lint on the affected areas; if it fails, try
--fix; if it still fails, STOP - Run the relevant tests (see
/test); if they fail, STOP with an error git addonly the modified files (never a blindgit add -A)- Message in English, format
type: description(max 50 chars, imperative, no trailing period) - Types: feat, fix, refactor, docs, test, chore, ui
- Confirm with the user before committing (unless a message was already passed)
Rules
- Never add a
Co-Authored-By(or any AI-attribution) trailer to the message - Never commit
.envor credentials - No
--no-verifyunless the user asks - No
--amendunless the user asks (create a new commit)
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.
- 9d ago First seen · 27 lines · 15 tokens per session scan A d9df56789bb7
commit is a command published in the GitHub repository Cristhianzl/claude-skills-czl (5 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 260 once invoked, about $0.0001 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.