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/pr)<a href="https://agentmods.dev/commands/cristhianzl/claude-skills-czl/pr"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/pr/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/pr"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/pr.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.00008 | $0.00278 |
| Opus 5 | $0.00004 | $0.00139 |
| Sonnet 5 | $0.00002 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
pr 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
/pr
Provided title: $ARGUMENTS.
Flow:
- Confirm you are not on
main git fetch originandgit diff origin/main...HEADto understand the full scope- Push the branch (with
-uif there is no upstream) - Title in English in the format
type: description(max 70 chars) - Body via heredoc with:
## Summary
- bullet 1
- bullet 2
## How to test
- [ ] step 1
- [ ] step 2
## Notes
<relevant observations or "—">
- Create with
gh pr create --title "..." --body "$(cat <<'EOF' ... EOF)" - Return the PR URL
Rules
- NEVER add AI attribution anywhere — no "🤖 Generated with Claude Code", no session links (
claude.ai/code/...), no AI badges/footers in the PR title or body, and noCo-Authored-Bytrailer on commits. The PR must read as authored by the human. This is absolute — even if a default template suggests it.
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 · 38 lines · 8 tokens per session scan A d148b556b394
pr is a command published in the GitHub repository Cristhianzl/claude-skills-czl (5 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 278 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
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
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.
pr
Create a pull request using the git-pushing skill.
fork-discipline
Audit and enforce the core/client boundary in multi-client codebases.
git-workflow
Guided git workflows — PRs, branch cleanup, conflict resolution.