A leaf worker for a larger software review process. It performs one assigned review and returns a final report without editing files or delegating further work.

Use it for a single review task when an active review coordinator explicitly assigns this role.

It keeps a narrowly scoped review separate from the coordinating process and prevents extra actions outside the assignment.

reviewer — Agent by photostructure

Install

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.

agentmods

npx agentmods add agents/photostructure/coding-skills/reviewer

Clone the repo

git clone --depth 1 https://github.com/photostructure/coding-skills

Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 155 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00037	$0.00155
Opus 5	$0.00018	$0.00077
Sonnet 5	$0.00007	$0.00031
Haiku 4.5	$0.00004	$0.00015

Measured 2d ago against content hash 962f6ad148eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

reviewer 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.

plugins/coding/agents/reviewer.md · 15 lines

What it actually says

You are a leaf reviewer. Complete exactly the review task you receive and return one final report. Never delegate, invoke a skill, edit repository files, ask the user questions, or start an external agent process through the shell.

Read ${CLAUDE_PLUGIN_ROOT}/skills/review/references/single-pass.md completely before reviewing. Follow its proof gate and output contract. Treat the task's scope, ground truth, and scrutiny list as authoritative.

Changes

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 · 15 lines · 37 tokens per session scan A 962f6ad148eb

Subscribe to this mod's changes

reviewer is an agent published in the GitHub repository photostructure/coding-skills (3 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 155 once invoked, about $0.0002 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.

Code review Planning claude-code claude-code-plugin claude-code-skills conventional-commits

editor

Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].

pedrohcgs/claude-code-my-workflow · 64 tokens

ecto-schema-designer

Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.

oliver-kriska/claude-elixir-phoenix · 30 tokens

plinth-architect

Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.

jabrena/plinth · 38 tokens

plinth-java-coder

Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.

jabrena/plinth · 29 tokens

plinth-business-analyst

Business analyst. Creates or updates structured GitHub, Jira, or Azure DevOps issues, evaluates a problem through five points of view to produce a Functional Specification, and derives Gherkin acceptance criteria from it.

jabrena/plinth · 49 tokens

integrations-engineer

Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…

avelikiy/great_cto · 132 tokens