building-plugins

building-plugins is a skill for Claude Code from C0ntr0lledCha0s/claude-code-plugin-automations. It costs 44 tokens per session (6,489 once invoked), scanned A, original, MIT.

A set of instructions for creating Claude Code plugins, which are packages that bundle related agents, skills, commands, and hooks.

In plain words
What is it for?
Use it when creating plugin folders, manifests, component structures, or a distributable toolkit with several related parts.
Why use it?
It helps organize related coding-agent components into a package that can be installed, shared, and maintained together.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions subagents; positional $N argument.

Part of the claude-component-builder plugin — 6 skills, 4 commands, 6 agents, 3 plugins shipped together

Install

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.

agentmods
npx agentmods add skills/c0ntr0lledcha0s/claude-code-plugin-automations/building-plugins
Any agent
npx skills add C0ntr0lledCha0s/claude-code-plugin-automations --skill building-plugins
Clone the repo
git clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations

Made for: Claude Code.

Or install claude-component-builder, the plugin that ships this one along with the rest of its 6 skills, 4 commands, 6 agents, 3 plugins.

Wrote 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.

agentmods badge for building-plugins

README.md
[![agentmods](https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/building-plugins.svg)](https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/building-plugins)
Your own site
<a href="https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/building-plugins"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/building-plugins.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,489 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.06489
Opus 5 $0.00022 $0.03245
Sonnet 5 $0.00009 $0.01298
Haiku 4.5 $0.00004 $0.00649

Measured 6d ago against content hash 36c4b492b04f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

building-plugins 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 6d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/validate-plugin.py, templates/full-plugin-template/hooks/scripts/validate-bash.sh, templates/standard-plugin-template/scripts/helper.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

claude-component-builder/skills/building-plugins/SKILL.md · 996 lines

How it starts

The opening of the file, as written. The whole thing — 996 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Building Plugins Skill

You are an expert at creating Claude Code plugins. Plugins are bundled packages that combine agents, skills, commands, and hooks into cohesive, distributable units.

What is a Plugin?

A plugin is a package that bundles related Claude Code components:

  • Agents: Specialized subagents for delegated tasks
  • Skills: Auto-invoked expertise modules
  • Commands: User-triggered slash commands
  • Hooks: Event-driven automation

Plugins enable users to install complete functionality with a single command.

When to Create a Plugin vs Individual Components

Use a PLUGIN when:

  • You want to distribute multiple related components together
  • You're building a cohesive feature set or domain expertise
  • You want users to install everything with one command
  • You need to maintain version compatibility across components
  • You're creating a reusable toolkit for a specific domain

Use INDIVIDUAL COMPONENTS when:

  • You only need a single agent, skill, or command
  • Components are unrelated and can be used independently
  • You're customizing for a specific project
  • You don't plan to distribute or share

Plugin Creation Process

Creating a plugin involves:

  1. Gathering requirements (name, components, metadata)
  2. Creating the directory structure
  3. Writing the plugin.json manifest
  4. Creating each component (agents, skills, commands, hooks)
  5. Writing comprehensive README.md
  6. Validating the complete plugin

Component Creation: Each component type (agents, skills, commands, hooks) should follow its respective best practices. Use the corresponding building-* skills for expertise on creating each type.

Plugin Structure & Schema

Directory Structure

plugin-name/
├── .claude-plugin/
│   └── plugin.json          # Required: Plugin manifest
├── agents/                  # Optional: Agent definitions
│   ├── agent1.md
│   └── agent2.md
├── skills/                  # Optional: Skill directories
│   ├── skill1/
│   │   ├── SKILL.md
│   │   ├── scripts/
│   │   ├── references/
│   │   └── assets/
│   └── skill2/
│       └── SKILL.md
├── commands/                # Optional: Slash commands
│   ├── command1.md
│   └── command2.md
├── hooks/                   # Optional: Event hooks
│   ├── hooks.json
│   └── scripts/
├── scripts/                 # Optional: Helper scripts
│   └── setup.sh
├── .mcp.json               # Optional: MCP server configuration
└── README.md               # Required: Documentation

Read the full file on GitHub · 996 lines

Changes

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.

  1. 6d ago First seen · 996 lines · 44 tokens per session scan A 36c4b492b04f

Subscribe to this mod's changes

building-plugins is a skill published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 44 tokens to every session and 6,489 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens