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/severity1/claude-code-plugin-creator/plugin-creatornpx skills add severity1/claude-code-plugin-creator --skill plugin-creatorgit clone --depth 1 https://github.com/severity1/claude-code-plugin-creatorWhat 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.00064 | $0.01461 |
| Opus 5 | $0.00032 | $0.00731 |
| Sonnet 5 | $0.00013 | $0.00292 |
| Haiku 4.5 | $0.00006 | $0.00146 |
Grade A, and why
plugin-creator 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Creator
Purpose
This skill guides the creation of Claude Code plugins - modular packages that extend Claude Code with custom slash commands, specialized agents, reusable skills, event hooks, and external service integrations. Use this skill to build plugins ranging from simple utilities to complex development toolkits.
When to Use This Skill
Apply this skill when the user wants to:
- Create a new Claude Code plugin from scratch
- Add components to an existing plugin (commands, agents, skills, hooks, MCP servers)
- Set up a plugin development environment
- Understand plugin structure and best practices
- Test or distribute a plugin
Common usage patterns:
- "Create a plugin with /deploy and /rollback commands"
- "Build a Python development toolkit plugin"
- "Add a code formatter hook to my existing plugin"
- "Create a plugin that integrates with the GitHub API"
- "Help me scaffold a new Claude Code plugin"
How to Use This Skill
Development Workflow
Follow the core development workflow:
- Understanding - Gather 2-3 concrete examples of how the plugin will be used
- Planning - Determine which components are needed (commands, agents, skills, hooks, MCP servers)
- Implementation - Execute
python scripts/init_plugin.py <plugin-name>to scaffold the structure - Customization - Customize generated components, remove unused ones, update metadata
- Testing - Install via local marketplace, validate, and iterate
For detailed procedures (Phases 0-5), example scenarios, and distribution guidance, consult references/development-workflow.md.
Component Types:
- Commands - User-invoked operations (
/deploy,/test) - Skills - Reusable workflows with bundled resources
- Agents - Automatic delegation to specialized tasks
- Hooks - Automatic responses to events
- MCP servers - External service integration
Consult references/component-specifications.md for detailed component guidance.
Iteration and Refinement
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/agent-template.md 1.1 KB
- assets/command-template.md 922 B
- assets/hooks-template.json 1.3 KB
- assets/marketplace-template.json 482 B
- assets/mcp-template.json 731 B
- assets/skill-template.md 1.2 KB
- references/component-examples.md 7.4 KB
- references/component-specifications.md 6.9 KB
- references/development-workflow.md 9.7 KB
- references/marketplace-guide.md 7.7 KB
- references/pattern-library.md 5.7 KB
- references/plugin-json-examples.md 2.2 KB
- references/troubleshooting.md 5.2 KB
- scripts/init_plugin.py 6.9 KB runs code
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 · 151 lines · 64 tokens per session scan A 8bf58c1daf02
plugin-creator is a skill published in the GitHub repository severity1/claude-code-plugin-creator (5 stars, last pushed 9mo ago), licensed MIT. It adds 64 tokens to every session and 1,461 once invoked, about $0.0003 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.
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…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…