agentmods.dev

create-plugin

create-plugin is a command for Claude Code from basher83/lunar-claude. It costs 16 tokens per session (3,321 once invoked), scanned A, a copy of create-plugin, MIT.

A guided workflow for building a complete Claude Code plugin from an initial idea through design, implementation, validation, and testing.

In plain words
What is it for?
It is for creating plugins with commands, skills, agents, hooks, or other components while clarifying requirements and checking the result.
Why use it?
It helps turn an unclear plugin request into defined components and reduces the chance of missing requirements or standard checks.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions .claude-plugin; names the TodoWrite tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the plugin-dev plugin — 7 skills, 5 commands, 3 agents shipped together

not rated 23repo today A scan 16 tokens copy · 83% MIT

Good fit It is for creating plugins with commands, skills, agents, hooks, or other components while clarifying requirements and checking the result.

Compare 6 commands from other repositories ↓
View source ↗ basher83/lunar-claude
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add basher83/lunar-claude
Claude Code
/plugin install plugin-dev

Made for: Claude Code.

Or install plugin-dev, the plugin that ships this one along with the rest of its 7 skills, 5 commands, 3 agents.

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 create-plugin

README.md
[![agentmods](https://agentmods.dev/badge/commands/basher83/lunar-claude/create-plugin/github.svg)](https://agentmods.dev/commands/basher83/lunar-claude/create-plugin)
Your own site
<a href="https://agentmods.dev/commands/basher83/lunar-claude/create-plugin"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/create-plugin/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for create-plugin

Your own site · 80×15
<a href="https://agentmods.dev/commands/basher83/lunar-claude/create-plugin"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/create-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,321 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% copy Near-identical to another mod 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.00016 $0.03321
Opus 5.5 $0.00006 $0.01328
Sonnet 5.5 $0.00003 $0.00664
Haiku 4.5 $0.00002 $0.00332

Measured 2mo ago against content hash 14ae34ff7f6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-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 2mo 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.

Origin

This is a copy

83% identical to create-plugin — 76 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/meta/plugin-dev/commands/create-plugin.md · 442 lines

How it starts

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

Plugin Creation Workflow

Guide the user through creating a complete, high-quality Claude Code plugin from initial concept to tested implementation. Follow a systematic approach: understand requirements, design components, clarify details, implement following best practices, validate, and test.

Core Principles

  • Ask clarifying questions: Identify all ambiguities about plugin purpose, triggering, scope, and components. Ask specific, concrete questions rather than making assumptions. Wait for user answers before proceeding with implementation.
  • Load relevant skills: Use the Skill tool to load plugin-dev skills when needed (plugin-structure, hook-development, agent-development, etc.)
  • Use specialized agents: Leverage agent-creator, plugin-validator, and skill-reviewer agents for AI-assisted development
  • Follow best practices: Apply patterns from plugin-dev's own implementation
  • Progressive disclosure: Create lean skills with references/examples
  • Use TodoWrite: Track all progress throughout all phases

Initial request: $ARGUMENTS

Phase 1: Discovery

Goal: Understand what plugin needs to be built and what problem it solves

Actions:

  1. Create todo list with all 7 phases
  2. If plugin purpose is clear from arguments:
    • Summarize understanding
    • Identify plugin type (integration, workflow, analysis, toolkit, etc.)
  3. If plugin purpose is unclear, ask user:
    • What problem does this plugin solve?
    • Who will use it and when?
    • What should it do?
    • Any similar plugins to reference?
  4. Summarize understanding and confirm with user before proceeding

Output: Clear statement of plugin purpose and target users

Phase 2: Component Planning

Goal: Determine what plugin components are needed

MUST load plugin-structure skill using Skill tool before this phase.

Actions:

  1. Load plugin-structure skill to understand component types
  2. Analyze plugin requirements and determine needed components:
    • Skills: Does it need specialized knowledge? (hooks API, MCP patterns, etc.)
    • Commands: User-initiated actions? (deploy, configure, analyze)
    • Agents: Autonomous tasks? (validation, generation, analysis)
    • Hooks: Event-driven automation? (validation, notifications)
    • MCP: External service integration? (databases, APIs)
    • Settings: User configuration? (.local.md files)
  3. For each component type needed, identify:
    • How many of each type
    • What each one does
    • Rough triggering/usage patterns
  4. Present component plan to user as table:

Read the full file on GitHub · 442 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. 2mo ago First seen · 442 lines · 16 tokens per session scan A 14ae34ff7f6d

Subscribe to this mod's changes

create-plugin is a command published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 3,321 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to create-plugin, differing in 76 lines, and is treated as a copy.

Building agentsPlanning
Related

create-plugin compared with commands from other repositories

create-plugin next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-pluginbasher83/lunar-claudeCommand23todayMITA16Claude Code
checklistgithub/spec-kitCommand149ktodayMITA13Claude Code
clarifygithub/spec-kitCommand149ktodayMITA27Claude Code
specifygithub/spec-kitCommand149ktodayMITA13Claude Code
analyzegithub/spec-kitCommand149ktodayMITA26Claude Code
convergegithub/spec-kitCommand149ktodayMITA35Claude Code
implementgithub/spec-kitCommand149ktodayMITA14Claude Code