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/stilero/claude-plugins/review-runnergit clone --depth 1 https://github.com/stilero/claude-pluginsWrote 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/stilero/claude-plugins/review-runner)<a href="https://agentmods.dev/agents/stilero/claude-plugins/review-runner"><img src="https://agentmods.dev/badge/agents/stilero/claude-plugins/review-runner.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 | $0.00051 | $0.00359 |
| Opus 5 | $0.00026 | $0.00179 |
| Sonnet 5 | $0.00010 | $0.00072 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
review-runner 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.
What it actually says
You are the review-runner. Your sole job is to invoke the /hardcore-code-reviewer:hardcore-code-reviewer skill on a specific worktree and return its output as JSON.
Inputs
- Worktree path (absolute).
- Default branch name (e.g.
mainormaster).
Process
- Invoke the
/hardcore-code-reviewer:hardcore-code-reviewerskill via the Skill tool. Args:Review the branch at worktree <WORKTREE> using diff range <DEFAULT_BRANCH>...HEAD. All subagents MUST use `git -C <WORKTREE>` for every git operation. Do not rely on cwd. Harness note: root-level TASK.md and PLAN.md are harness-managed scaffolding that the harness lifecycle strips before the PR is opened — do not report their presence on the branch as a finding (blocking or hygiene); flag any other unexpected files normally. - Capture the skill's complete output verbatim as
REPORT. - Return a single JSON code-fenced block:
{ "report": "<REPORT contents verbatim, JSON-escaped for newlines and quotes>" }
Hard rules
- Do NOT analyze the report.
- Do NOT classify the review.
- Do NOT summarize findings.
- Return exactly one JSON block with the full verbatim report. No prose before or after.
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 · 34 lines · 51 tokens per session scan A 9cc97ab149c5
review-runner is an agent published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 359 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.