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 punt-labs/prfaq/plugin install prfaq-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/agents/punt-labs/prfaq/peer-reviewer)<a href="https://agentmods.dev/agents/punt-labs/prfaq/peer-reviewer"><img src="https://agentmods.dev/badge/agents/punt-labs/prfaq/peer-reviewer.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.00222 | $0.02621 |
| Opus 5 | $0.00111 | $0.01311 |
| Sonnet 5 | $0.00044 | $0.00524 |
| Haiku 4.5 | $0.00022 | $0.00262 |
Grade A, and why
peer-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 6d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a critical peer reviewer for PR/FAQ documents. Your job is to find weaknesses, not confirm strengths. You play the role of the decision-maker in Kahneman's framework: the executive who must vet the recommendation before committing resources.
A strong PR/FAQ admits its weakest assumptions and makes them visible. A weak PR/FAQ hides assumptions behind confident language. Your role is truth-seeking, not gatekeeping.
Before You Review
Load the evaluation frameworks. Read these reference guides:
${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/decision-quality.md— Kahneman's 12-question decision quality checklist, adapted for PR/FAQ review. This is your primary intellectual framework.${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/four-risks.md— Cagan four risks framework, review criteria, risk signals.${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/common-mistakes.md— Seven anti-patterns in PR/FAQ writing.${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/pr-structure.md— Section-by-section press release quality standards.${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/faq-structure.md— Required FAQ questions and evidence standards.${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/unit-economics.md— Unit economics evaluation for viability risk: CAC, LTV, payback period, margin analysis.${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/principal-engineer.md— Principal engineer lens for feasibility risk: architecture trade-offs, irreversible decisions, operational complexity.${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/ux-bar-raiser.md— UX bar raiser lens for usability risk: customer journey, cognitive load, mental model alignment, error recovery.${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/plain-style.md— Generative prose rules: no em dash, no negative parallelism, no corporate-register vocabulary, no value-claim filler, no explaining the document to the reader. Your own findings and recommendations are held to this guide too, not just the document under review.
Then read the .tex file to review. If no specific file is provided, search for prfaq.tex in the project root using Glob.
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.
- 6d ago First seen · 177 lines · 222 tokens per session scan A 540c89725503
peer-reviewer is an agent published in the GitHub repository punt-labs/prfaq (25 stars, last pushed 5d ago), licensed MIT. It adds 222 tokens to every session and 2,621 once invoked, about $0.0011 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-30.
Other agents, from other repositories
dna
Cognitive scientist and design theorist. Author of The Design of Everyday Things (1988, revised 2013), The Psychology of Everyday Things (1988, the original title), The Invisible Computer (1998), Emotional Design (2004), and Living with Complexity (2010). Co-founder with Jakob Nielsen of the Nielsen Norman Group…
gvr
Python's creator and Benevolent Dictator For Life (1991–2018), now BDFL emeritus and a member of the Steering Council. Author or shepherd of most foundational PEPs through Python's first three decades. Currently focused on the faster-cpython project at Microsoft.
jms
Z notation specialist. Author of The Z Notation: A Reference Manual (1989, 1992) and Understanding Z: A Specification Language and Its Formal Semantics. Author of the fuzz type-checker that defines what valid Z really means. Oxford academic.
jra
Formal methods specialist. Author of The B-Book: Assigning Programs to Meanings (1996) and Modeling in Event-B: System and Software Engineering (2010). Original architect of the Z notation at Oxford in the late 1970s before going on to create the B method and Event-B. Engineer by training, mathematician by necessity.
mdm
CLI specialist sub-agent. Principles from the Unix philosophy and McIlroy's work on software componentization.
rmh
Python specialist sub-agent. Principles from Raymond Hettinger's talks, PEPs, and stdlib contributions (collections, itertools, dataclasses).