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.
npx agentmods add commands/jezweb/claude-skills/releasegit clone --depth 1 https://github.com/jezweb/claude-skillsWrote 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/jezweb/claude-skills/release)<a href="https://agentmods.dev/commands/jezweb/claude-skills/release"><img src="https://agentmods.dev/badge/commands/jezweb/claude-skills/release.svg" alt="Measured on agentmods" 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 | $0.00007 | $0.00092 |
| Opus 5 | $0.00003 | $0.00046 |
| Sonnet 5 | $0.00001 | $0.00018 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade B, and why
release scanned grade B with 1 finding 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 5d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
allowed-tools: "*" What it actually says
Load the github-release skill and prepare a release.
If $ARGUMENTS contains a version (e.g. v1.2.0), use it. Otherwise, determine the next version from git tags.
Workflow: secrets scan → personal artifact check → LICENSE/README validation → create tag → publish via gh CLI.
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.
- 5d ago First seen · 12 lines · 7 tokens per session scan B e34bdc1d65cb
release is a command published in the GitHub repository jezweb/claude-skills (996 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 92 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
ship
Seen on their staging, then live. Rollback you have run.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
git-npm-release
IMPORTANT: This command ONLY runs when explicitly invoked via /git-npm-release. Do NOT auto-release.
ship
Pre-release gate — run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
snr-ship
Run the go/no-go release gate and produce an explicit ship or do-not-ship verdict with named blockers, accepted risks and a rollback plan.
ship-and-observe
Take merged, green code to a verified, monitored production release — deploy, confirm the revision is live, smoke-test, observe, and roll back if needed.