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 skills/ai-native-sys/claude-code-tools/releasenpx skills add ai-native-sys/claude-code-tools --skill releasegit clone --depth 1 https://github.com/ai-native-sys/claude-code-toolsWhat 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.00018 | $0.00576 |
| Opus 5 | $0.00009 | $0.00288 |
| Sonnet 5 | $0.00004 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
release 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 yesterday.
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Plugins
Guide the release process for this plugin marketplace: review changes, bump versions, verify consistency, and push to GitHub.
Step 1: Code review current changes
Run git diff main (or git diff HEAD if on main with uncommitted changes) to identify all changed files.
Review the changes for:
- Correctness and code quality
- Potential bugs or regressions
- Security concerns
Summarize findings to the user. If there are significant issues, flag them and ask if the user wants to proceed or fix first.
Step 2: Identify changed plugins
From the diff, determine which plugins under plugins/ have been modified. A plugin is considered changed if any file under its plugins/<name>/ directory was modified.
List the changed plugins for the user.
Step 3: Check and bump version numbers
For each changed plugin, check whether its version has already been bumped by comparing:
plugins/<name>/.claude-plugin/plugin.json→versionfield.claude-plugin/marketplace.json→ the matching entry inplugins[]→versionfield
If the version has NOT been updated for a changed plugin, ask the user what the new version number should be (suggest a semver bump based on the nature of the changes — patch for fixes, minor for features, major for breaking changes).
Only update versions for plugins that have actual changes. Do NOT touch versions for unchanged plugins.
Step 4: Update version numbers
Apply the new version to both locations for each changed plugin:
plugins/<name>/.claude-plugin/plugin.json→version.claude-plugin/marketplace.json→ the matchingplugins[]entry →version
Step 5: Verify version consistency
For every plugin listed in .claude-plugin/marketplace.json, verify that:
- The version in
marketplace.jsonmatches the version inplugins/<name>/.claude-plugin/plugin.json - The
namefields match - The plugin source directory exists
Report any mismatches and fix them before proceeding.
Step 6: Commit and 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.
- yesterday First seen · 62 lines · 18 tokens per session scan A ddfbcc3e4668
release is a skill published in the GitHub repository ai-native-sys/claude-code-tools (1 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 576 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…