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 skills add jared833/claude-code-hooks --skill ship-skillgit clone --depth 1 https://github.com/jared833/claude-code-hooksWrote 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/skills/jared833/claude-code-hooks/ship-skill)<a href="https://agentmods.dev/skills/jared833/claude-code-hooks/ship-skill"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/ship-skill/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/skills/jared833/claude-code-hooks/ship-skill"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/ship-skill.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.00089 | $0.01216 |
| Opus 5.5 | $0.00036 | $0.00486 |
| Sonnet 5.5 | $0.00018 | $0.00243 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
ship-skill 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Put a finished skill where it belongs
~/.claude/skills/ and ~/.claude/hooks/ are gitignored. ~/.claude/.gitignore is *
with exceptions only for .gitignore, CLAUDE.md and settings.json, so a skill that lives
only there exists in exactly one place on one machine. That is the reason this runs, and the
backup is the same action as the publish.
A skill is not done when it runs. It is done when it is public, backed up and findable.
0. Does it go public at all
Most do. The ones that do not are the seats and anything whose content is one business's pricing, roadmap, refund policy or private accounts. If a skill is private on purpose, say so in your output and stop here; do not sanitize it into something meaningless.
The published set already keeps real names, real dates and real business specifics on purpose. The repo README argues for that: a sanitized example with every specific removed teaches nothing. So sanitizing is narrow. It removes ids and secrets, nothing else.
1. Sanitize, then have a cold agent check it
Replace, and nothing more:
| Real | Placeholder |
|---|---|
| A Notion data source id | collection://YOUR-<NAME>-DATA-SOURCE-ID |
| Your real home directory in a path | <HOME> |
| A Buffer org id | YOUR-BUFFER-ORG-ID |
| A Canva design id | <CANVA-DESIGN-ID> |
| Any other account id, topic string or token | an <angle-bracket> name |
Then dispatch one cold agent, pointed at the exact files, told to scan for secrets, real
home directory paths, personal email addresses, private ids and any file that should never be
in a repo, and to return PASS or FAIL rather than fixing anything. See
review-prompts/ for the two prompts this is the third of. It is the
review anything public gets on top of the two normal ones. Its dispatch prompt carries the no-spawn line and
the verify-before-reporting rule. Do not push before it comes back.
2. Into the public repo
Your public repo. Here that is claude-code-hooks, MIT.
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.
- 2mo ago First seen · 95 lines · 89 tokens per session scan A 9d2087d1ec9f
ship-skill is a skill published in the GitHub repository jared833/claude-code-hooks (2 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 1,216 once invoked, about $0.0004 per session on Opus 5.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-09-04.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…