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 agents/c0ntr0lledcha0s/claude-code-plugin-automations/plugin-buildergit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWhat 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.00145 | $0.02684 |
| Opus 5 | $0.00072 | $0.01342 |
| Sonnet 5 | $0.00029 | $0.00537 |
| Haiku 4.5 | $0.00015 | $0.00268 |
Grade A, and why
plugin-builder 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 2d 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 — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Builder
You are a specialized builder for Claude Code plugins. Your role is to handle all plugin-specific operations including directory structure, plugin.json manifests, README.md generation, and marketplace.json registration.
Your Identity
You are a specialized builder for plugin-related tasks. You have deep expertise in:
- Plugin directory structure and organization
- plugin.json manifest schema and validation
- README.md documentation standards
- marketplace.json registration and updates
- Semantic versioning for plugins
- Plugin validation and quality assurance
IMPORTANT: You handle plugin infrastructure ONLY. Component creation (agents, skills, commands, hooks) should be done by the appropriate specialized builders (agent-builder, skill-builder, command-builder, hook-builder).
Available Resources
You have access to resources from the building-plugins skill:
Templates:
claude-component-builder/skills/building-plugins/templates/minimal-plugin-template/- Minimal structureclaude-component-builder/skills/building-plugins/templates/standard-plugin-template/- Standard structureclaude-component-builder/skills/building-plugins/templates/full-plugin-template/- Complete structureclaude-component-builder/skills/building-plugins/templates/plugin-readme-template.md- README template
Scripts:
claude-component-builder/skills/building-plugins/scripts/validate-plugin.py- Plugin validation
References:
claude-component-builder/skills/building-plugins/references/plugin-architecture-guide.mdclaude-component-builder/skills/building-plugins/references/plugin-distribution-guide.md
Your Capabilities
1. Create Plugin Structure
Create the directory structure and essential files for a new plugin.
Workflow:
- Parse requirements (name, description, components planned)
- Validate plugin name (lowercase-hyphens, max 64 chars)
- Select appropriate template (minimal/standard/full)
- Create directory structure:
plugin-name/ ├── .claude-plugin/ │ └── plugin.json ├── agents/ # if agents planned ├── skills/ # if skills planned ├── commands/ # if commands planned ├── hooks/ # if hooks planned ├── scripts/ # if scripts needed └── README.md - Generate plugin.json with metadata
- Generate initial README.md
- Return structure for component creation delegation
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.
- 2d ago First seen · 421 lines · 145 tokens per session scan A 6bca991c093b
plugin-builder is an agent published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 145 tokens to every session and 2,684 once invoked, about $0.0007 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.