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/elct9620/claudekit/create-pluginnpx skills add elct9620/claudekit --skill create-plugingit clone --depth 1 https://github.com/elct9620/claudekitWhat 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.00015 | $0.00477 |
| Opus 5 | $0.00008 | $0.00238 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
Create Claude Plugin 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 3d 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
Create Claude Plugin
Instruction
- Use the
Globtool to check if plugin is existing - Use Ask Question Tool to confirm overwriting if plugin already exists
- Create a new directory for the plugin
- Create a minimal plugin structure for plugin
- Update the plugin metadata file with basic information
- Update root README.md to include the new plugin
- Update
.claude-plugin/marketplace.jsonto include the new plugin - Update release please config to include the new plugin
Plugin Structure
|- .claude-plugin/
|- plugin.json
|- commands/ # Omit if no commands
|- example.md
|- agents/ # Omit if no agents
|- example-agent.md
|- skills/ # Omit if no skills
|- example-skill/
|- SKILL.md
|- hooks/ # Omit if no hooks
|- hooks.json
|- src/ # Omit if no hook script is needed
|- example.ts
|- dist/ # Auto-generated, omit
|- example.js
|- README.md
|- rolldown.config.js # Omit if no src
|- package.json # Omit if no src
|- tsconfig.json # Omit if no src
The minimal plugin.json is
{
"name": "plugin-name",
"version": "0.1.0",
"description": "A brief description of the plugin",
"author": {
"name": "Author Name"
}
}
Reference
For detailed information on creating Claude plugins, refer to following documentation:
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.
- 3d ago First seen · 65 lines · 15 tokens per session scan A b0fc58c2a605
Create Claude Plugin is a skill published in the GitHub repository elct9620/claudekit (9 stars, last pushed 9d ago), licensed MIT. It adds 15 tokens to every session and 477 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…