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 commands/ivan-magda/claude-code-plugin-template/initgit clone --depth 1 https://github.com/ivan-magda/claude-code-plugin-templateWhat 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.00753 |
| Opus 5 | $0.00006 | $0.00377 |
| Sonnet 5 | $0.00003 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00075 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- init — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 150 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/withplugin.jsoncommands/directoryagents/directoryskills/directoryhooks/directory withhooks.jsonscripts/directory
- Generates a starter
plugin.jsonwith 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:
$1/
├── .claude-plugin/
├── commands/
├── agents/
├── skills/
├── hooks/
└── scripts/
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 hooks.json
Create hooks/hooks.json with a basic structure:
{
"description": "Plugin hooks",
"hooks": {}
}
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]
### Create Validation Script
Create `scripts/validate-plugin.sh` with executable permissions:
```bash
#!/usr/bin/env bash
set -euo pipefail
# Basic plugin structure validation
[ -f ".claude-plugin/plugin.json" ] || { echo "Missing plugin.json" >&2; exit 2; }
exit 0
Make it executable: chmod +x scripts/validate-plugin.sh
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 · 150 lines · 13 tokens per session scan A 2ad5ef2dcb47
init is a command published in the GitHub repository ivan-magda/claude-code-plugin-template (67 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 753 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-30.
Other commands, from other repositories
save-chat
Save the current conversation to a document file.
extract
Analyze conversation history and extract reusable skills, commands, or agents.
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
raw-export
Export raw conversation data directly from JSONL session files.
search
Search saved conversations by keyword or date.
clean
Clean up old saved conversation files.