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/test-localgit 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.00011 | $0.02066 |
| Opus 5 | $0.00005 | $0.01033 |
| Sonnet 5 | $0.00002 | $0.00413 |
| Haiku 4.5 | $0.00001 | $0.00207 |
Grade A, and why
test-local 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
2 near-identical copies found in the catalogue:
- test-local — 100% identical, 0 lines differ
- test-local — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Plugin Locally
Set up a development marketplace for local testing and install the current plugin.
Prerequisites
- Must be run from a plugin root directory (containing
.claude-plugin/plugin.json) - Plugin should pass validation (run
/plugin-development:validatefirst)
Instructions
What This Command Does
- Creates a sibling
dev-marketplace/directory (if it doesn't exist) - Generates
dev-marketplace/.claude-plugin/marketplace.jsonpointing to your plugin - Provides instructions for:
- Adding the marketplace to Claude Code
- Installing the plugin
- Testing workflow (edit → reinstall → test loop)
Step 1: Read Plugin Metadata
Read .claude-plugin/plugin.json to get:
- Plugin name
- Plugin description
- Plugin version
Step 2: Determine Plugin Path
Get the current plugin directory path. Common patterns:
- Current working directory
- From the location of plugin.json
The marketplace source path should be relative from marketplace to plugin:
- If plugin is at
/path/to/my-plugin/ - Dev marketplace at
/path/to/dev-marketplace/ - Source path:
../my-plugin
Step 3: Create Dev Marketplace Structure
- Create directory:
../dev-marketplace/.claude-plugin/ - Create
marketplace.jsonat../dev-marketplace/.claude-plugin/marketplace.json
Step 4: Generate marketplace.json
Create with this structure:
{
"name": "dev-marketplace",
"owner": {
"name": "Developer"
},
"metadata": {
"description": "Local development marketplace for testing plugins",
"version": "0.1.0"
},
"plugins": [
{
"name": "<plugin-name-from-plugin.json>",
"description": "<description-from-plugin.json>",
"version": "<version-from-plugin.json>",
"source": "../<plugin-directory-name>"
}
]
}
Important: The source path is relative from marketplace to plugin directory.
Step 5: Provide Testing Instructions
Display clear instructions for the user:
✅ Dev marketplace created at ../dev-marketplace/
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🚀 Testing Workflow
1️⃣ ADD MARKETPLACE (First time only)
/plugin marketplace add ../dev-marketplace
Verify:
/plugin marketplace list
2️⃣ INSTALL PLUGIN
/plugin install <plugin-name>@dev-marketplace
Verify:
/help
(Your commands should appear)
3️⃣ TEST COMMANDS
/<plugin-name>:<command-name> [args]
Examples:
/<plugin-name>:command1
/<plugin-name>:command2 arg
4️⃣ ITERATION LOOP (After making changes)
a. Edit your plugin files
b. Validate: /plugin-development:validate
c. Uninstall: /plugin uninstall <plugin-name>@dev-marketplace
d. Reinstall: /plugin install <plugin-name>@dev-marketplace
e. Test again: /<plugin-name>:command-name
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
💡 Tips
- Must uninstall/reinstall to pick up changes
- Use /plugin-development:validate before each test
- Check /agents to see if your agents appear
- Use claude --debug to see plugin loading details
- Run hooks/scripts directly to test them: ./scripts/validate.sh
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📦 Marketplace Location
Path: ../dev-marketplace/
Config: ../dev-marketplace/.claude-plugin/marketplace.json
Plugin reference:
- Name: <plugin-name>
- Source: ../<plugin-directory>
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 · 380 lines · 11 tokens per session scan A 962cfff40088
test-local is a command published in the GitHub repository ivan-magda/claude-code-plugin-template (68 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 2,066 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.
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
extract
Analyze conversation history and extract reusable skills, commands, or agents.
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.