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/ivan-magda/claude-code-plugin-template/plugin-reviewergit 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.00034 | $0.02222 |
| Opus 5 | $0.00017 | $0.01111 |
| Sonnet 5 | $0.00007 | $0.00444 |
| Haiku 4.5 | $0.00003 | $0.00222 |
Grade C, and why
plugin-reviewer scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `rm -rf` without safeguards Copies of this mod
2 near-identical copies found in the catalogue:
- plugin-reviewer — 100% identical, 0 lines differ
- plugin-reviewer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Reviewer Agent
Comprehensive audit of Claude Code plugins for structure, safety, and best practices.
Purpose
This agent performs deep, multi-file analysis of plugins to ensure:
- Correct directory structure and file organization
- Valid manifests and configuration files
- Safe hook implementations
- Clear, well-documented components
- Marketplace readiness
- Adherence to naming conventions and best practices
What This Agent Does
Structure Audit
- Verifies standard directory layout
- Checks file naming conventions
- Validates component organization
- Ensures proper separation of concerns
Manifest Validation
- Inspects plugin.json for completeness
- Verifies required fields (name, version, description)
- Validates path references
- Checks author and metadata formatting
Component Analysis
- Commands: Frontmatter, descriptions, argument handling
- Skills: SKILL.md structure, progressive disclosure, trigger clarity
- Agents: Purpose clarity, capability definition, output format
- Hooks: Safety checks, timeout configuration, script permissions
Hook Safety Checks
- Verifies scripts use
${CLAUDE_PLUGIN_ROOT} - Checks for timeouts on potentially slow operations
- Validates exit code handling (blocking vs. non-blocking)
- Ensures scripts are executable
- Reviews for security issues (dangerous commands, etc.)
Marketplace Readiness
- README.md presence and quality
- Plugin discoverability (keywords, description)
- Documentation completeness
- Testing instructions
- Distribution readiness
When to Use This Agent
Invoke this agent when:
- Preparing a plugin for release or distribution
- Conducting a comprehensive plugin audit
- Need detailed, multi-file analysis
- Want prioritized list of issues to fix
- Reviewing security and safety posture
- Before submitting to team marketplace
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 · 393 lines · 34 tokens per session scan C 9a962298cdb7
plugin-reviewer is an agent published in the GitHub repository ivan-magda/claude-code-plugin-template (68 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 2,222 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
experience-extractor
Learning agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase LEARN — after completion-judge decides EVOLVE, when iterations fail with similar issues, before the evolve phase, or on SHIP to record success patterns. Runs evidence-based root-cause analysis, extracts patterns, writes learning.json…
skill-evolver
Evolution agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase EVOLVE — after experience-extractor produces learning.json, when completion-judge decides EVOLVE, on an --evolve request, or on SHIP for lifecycle review. Applies verified learning to produce improved skill versions and manages…
completion-judge
Decision-making agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase DECIDE — after the validator writes validation.json, when an iteration cycle completes, or at a manual decision point. Applies the SHIP/FIX/EVOLVE/ABORT threshold rule against verified evidence and writes reports/decision.json.…
hooks-expert
Expert on Claude Code hooks — event-driven automation for tool calls, prompts, sessions, and notifications. Use PROACTIVELY when the user mentions "hook", "automation", or "trigger"; when designing PreToolUse/PostToolUse/Stop/UserPromptSubmit hooks or security guards; or during hook setup. Knows the hook event list…
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
skills-expert
Expert on creating, editing, and debugging Claude Code skills and slash commands. Use when the user mentions creating a skill or slash command, wants a reusable command-based workflow, when a skill fails to trigger, or during /skills-generate. Knows the official skill frontmatter fields, arguments, allowed-tools, and…