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.
/plugin marketplace add ivan-magda/claude-code-plugin-template/plugin install plugin-developmentWrote 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.
[](https://agentmods.dev/agents/ivan-magda/claude-code-plugin-template/plugin-reviewer)<a href="https://agentmods.dev/agents/ivan-magda/claude-code-plugin-template/plugin-reviewer"><img src="https://agentmods.dev/badge/agents/ivan-magda/claude-code-plugin-template/plugin-reviewer/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.
<a href="https://agentmods.dev/agents/ivan-magda/claude-code-plugin-template/plugin-reviewer"><img src="https://agentmods.dev/badge/agents/ivan-magda/claude-code-plugin-template/plugin-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00034 | $0.02222 |
| Opus 5.5 | $0.00014 | $0.00889 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (70 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 2,222 once invoked, about $0.0001 per session on Opus 5.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
atomic-reviewer
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
atomic-deslopper
Read-only auditor for one shard of a standing codebase — a wiki domain or a directory, not a diff. Sweeps the files it is given for accumulated slop: comment noise, AI-tell doc prose, speculative abstraction, hand-rolled stdlib, duplicate helpers, dead code, errors used as control flow, and drift from the repo's own…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
reviewer
Code review agent. Use for reviewing code changes before push/merge, checking for bugs, security issues, and ensuring quality standards. Mandatory before any push.
security-auditor
Security assessment agent. Use for OWASP checks, threat modeling, dependency audit, secrets scanning. Spawn it whenever a task touches auth, secrets, user input or dependencies — no code spawns it for you, so the orchestrator has to decide. Reports vulnerabilities with severity + fix recommendations.
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.