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 basher83/lunar-claude/plugin install plugin-devWrote 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/commands/basher83/lunar-claude/plugin-review)<a href="https://agentmods.dev/commands/basher83/lunar-claude/plugin-review"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/plugin-review.svg" alt="Measured on agentmods" 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.00016 | $0.03559 |
| Opus 5 | $0.00008 | $0.01780 |
| Sonnet 5 | $0.00003 | $0.00712 |
| Haiku 4.5 | $0.00002 | $0.00356 |
Grade A, and why
plugin-review 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 512 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Review Workflow
Systematically review a Claude Code plugin against best practices from plugin-dev skills. Creates a state file to track progress and enables resumable reviews.
Target plugin: $ARGUMENTS
Core Principles
- State file tracking: Create
.claude/<plugin-name>-review.local.mdto track all progress - Skill-based validation: Load relevant plugin-dev skills and validate against documented patterns
- Proof-based decisions: When recommending changes, cite specific guidance from skills
- Incremental commits: Commit improvements as they're made, track commit SHAs in state file
- Resumable: If session ends, next session can continue from state file
Phase 0: Setup
Goal: Validate plugin path and create state file
Actions:
- Validate the plugin path exists and has
.claude-plugin/plugin.json - Read plugin.json to get plugin name and version
- Auto-discover plugin components:
# Commands ls <plugin-path>/commands/*.md 2>/dev/null | wc -l # Agents ls <plugin-path>/agents/*.md 2>/dev/null | wc -l # Skills find <plugin-path>/skills -name "SKILL.md" 2>/dev/null | wc -l # Hooks test -f <plugin-path>/hooks/hooks.json && echo "yes" || echo "no" - Create state file at
.claude/<plugin-name>-review.local.md:
---
workflow: plugin-review
plugin: <plugin-name>
plugin_path: <plugin-path>
status: in_progress
started: <date>
last_updated: <date>
phase: discovery
plugin_version: <version>
---
# <Plugin-Name> Plugin Review
Comprehensive review against plugin-dev best practices.
## Component Inventory
| Component | Path | Count | Status |
|-----------|------|-------|--------|
| plugin.json | `.claude-plugin/plugin.json` | 1 | pending |
| README.md | `README.md` | 1 | pending |
| Commands | `commands/` | <n> | pending |
| Agents | `agents/` | <n> | pending |
| Skills | `skills/` | <n> | pending |
| Hooks | `hooks/` | <yes/no> | pending |
## Review Progress
### Phase 1: Commands
(to be filled during review)
### Phase 2: Agents
(to be filled during review)
### Phase 3: Skills
(to be filled during review)
### Phase 4: Metadata
(to be filled during review)
### Phase 5: Advanced Patterns
(to be filled during review)
## Commits
(to be filled as changes are committed)
## Next Steps
1. [ ] Phase 1: Review commands
2. [ ] Phase 2: Review agents
3. [ ] Phase 3: Review skills
4. [ ] Phase 4: Review metadata
5. [ ] Phase 5: Advanced patterns analysis
6. [ ] Commit changes
7. [ ] Version bump
8. [ ] Push to remote
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.
- 3d ago First seen · 512 lines · 16 tokens per session scan A a9175ad69c13
plugin-review is a command published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 3,559 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-09-03.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.
code-review
Review a PR diff for code-level defects (security, correctness, performance, maintainability) and post a severity-tagged review comment. Complements /verify-pr's AC-conformance check.