A command that creates the starter files and folders for a new Claude Code plugin, which is an add-on for the coding assistant.

Use it to create a plugin directory, plugin.json, commands/, a README template, and additional component folders when needed.

It gives a new plugin the expected layout and checks that its name follows the required kebab-case format.

init — Command by kossakovsky

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 commands/kossakovsky/cc-plugins/init

Clone the repo

git clone --depth 1 https://github.com/kossakovsky/cc-plugins

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 670 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.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.00670
Opus 5	$0.00006	$0.00335
Sonnet 5	$0.00003	$0.00134
Haiku 4.5	$0.00001	$0.00067

Measured yesterday against content hash 4921c6a632de, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

plugins/plugin-development/commands/init.md · 122 lines

How it starts

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

Initialize Plugin

Create the standard directory structure and files for a new Claude Code plugin.

Arguments

$1 (required): Plugin name in kebab-case (e.g., my-awesome-plugin)

What This Command Does

Creates the plugin directory structure:
- .claude-plugin/ with plugin.json
- commands/ directory
- agents/ directory
- skills/ directory
- hooks/ directory with hooks.json
- scripts/ directory
Generates a starter plugin.json with the provided name
Creates a README.md template
Provides next steps

Instructions

Validation

First, validate the plugin name:

Must be provided (not empty)
Should be kebab-case (lowercase with hyphens)
Should not contain spaces or special characters

If validation fails, explain the requirements and ask for a valid name.

Create Directory Structure

Create these directories by default:

$1/
├── .claude-plugin/
└── commands/

Only create additional directories (skills/, agents/, hooks/, scripts/) when the user adds corresponding components via /plugin-development:add-skill, /plugin-development:add-agent, or /plugin-development:add-hook. Do not create empty directories.

Create plugin.json

Create .claude-plugin/plugin.json with this template:

{
  "name": "$1",
  "version": "0.1.0",
  "description": "Brief description of what this plugin does",
  "author": {
    "name": "Your Name",
    "email": "[email protected]"
  },
  "license": "MIT",
  "keywords": ["keyword1", "keyword2"]
}

Create README.md

Create README.md with this template:

# $1

[Brief description of what this plugin does]

## Installation

```bash
/plugin install $1@marketplace-name

Commands

[List commands here]

Usage

[Provide examples]


## Next Steps

After scaffolding, provide these instructions to the user:

✓ Plugin scaffolded at $1/

Next steps:

Edit $1/.claude-plugin/plugin.json with your metadata
Add components:
- /plugin-development:add-command
- /plugin-development:add-skill
- /plugin-development:add-agent
Validate: /plugin-development:validate
Test locally: /plugin-development:test-local

Read the full file on GitHub · 122 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.

yesterday First seen · 122 lines · 13 tokens per session scan A 4921c6a632de

Subscribe to this mod's changes

init is a command published in the GitHub repository kossakovsky/cc-plugins (3 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 670 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.

Building agents Frontend Writing and docs

verify

Adversarial spec-vs-implementation verification for a completed task. Dispatches the spec-mentor subagent with fresh context (no anchoring bias), parses its verdict (PASS / DRIFT / NEEDS-MARTY), and updates the verification queue. The v7.4.0 architectural replacement for a dedicated "mentor session.".

MartyBonacci/specswarm · 68 tokens

init