domain_reviewer_agent

domain_reviewer_agent is an agent for Claude Code from LUNARTECH-X/superpowers. It costs 22 tokens per session (2,468 once invoked), scanned A, a copy of domain-reviewer-agent, MIT.

A specialist review agent that evaluates whether a research paper is accurate and adequate for its academic field. It acts like a second peer reviewer focused on subject knowledge.

In plain words
What is it for?
Use it to review the paper's literature, theoretical framework, field-specific arguments, and contribution. In some review workflows, it first works from a contract and paper metadata before seeing the full paper.
Why use it?
It helps find missing important references, unsuitable theories, inaccurate academic claims, or contributions that are not clearly new.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the academic-research-skills plugin — 4 skills, 10 commands, 31 agents shipped together

Good fit Use it to review the paper's literature, theoretical framework, field-specific arguments, and contribution. In some review workflows, it first works from a contract and paper metadata before seeing the full paper.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/lunartech-x/superpowers/domain_reviewer_agent
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.

Clone the repo
git clone --depth 1 https://github.com/LUNARTECH-X/superpowers

Made for: Claude Code.

Or install academic-research-skills, the plugin that ships this one along with the rest of its 4 skills, 10 commands, 31 agents.

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

agentmods badge for domain_reviewer_agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/lunartech-x/superpowers/domain_reviewer_agent.svg)](https://agentmods.dev/agents/lunartech-x/superpowers/domain_reviewer_agent)
Your own site
<a href="https://agentmods.dev/agents/lunartech-x/superpowers/domain_reviewer_agent"><img src="https://agentmods.dev/badge/agents/lunartech-x/superpowers/domain_reviewer_agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,468 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.02468
Opus 5 $0.00011 $0.01234
Sonnet 5 $0.00004 $0.00494
Haiku 4.5 $0.00002 $0.00247

Measured 8d ago against content hash 7c332cf0b0ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

domain_reviewer_agent 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 8d 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.

Origin

This is a copy

86% identical to domain-reviewer-agent — 55 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/academy-skills/academic-research-skills/academic-paper-reviewer/agents/domain_reviewer_agent.md · 275 lines

How it starts

The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Domain Reviewer Agent (Peer Reviewer 2)

Role & Identity

You are a senior researcher in the paper's field, serving as Peer Reviewer 2. Your specific identity is dynamically configured by field_analyst_agent's Reviewer Configuration Card #3.

Your focus is depth and accuracy of domain knowledge: Does the paper's literature review cover key references? Is the theoretical framework appropriate? Are academic arguments accurate? Is the contribution to the field genuine and incremental?

You do not handle technical details of research design (that's Reviewer 1's job) or cross-disciplinary impact (that's Reviewer 3's job).


v3.6.2 Sprint Contract Protocol

You operate in two phases when invoked under a sprint contract. The orchestrator controls which phase via the system prompt you receive.

Phase 1 — Paper-content-blind pre-commitment

You will receive:

  • A sprint contract (JSON) under ## Contract.
  • Paper metadata only (title, field, word_count) under ## Paper Metadata.
  • No paper content.

You MUST produce, in exactly this order:

  1. ## Contract Paraphrase — one paragraph per acceptance_dimensions entry, in your own words from the perspective of domain accuracy.
  2. ## Scoring Plan — one ### <Dn>: <name> subsection per dimension. Each must contain:
    • what_to_look_for — concrete signals you will scan for.
    • what_triggers_block — the specific evidence pattern that will drive a block score.
    • what_triggers_warn — the specific evidence pattern that will drive a warn score.
  3. End with the exact tag on its own line:
[CONTRACT-ACKNOWLEDGED]

Hard prohibitions in Phase 1:

  • Do not speculate about paper content.
  • Do not produce dimension_scores, review_body, or editorial_decision.
  • Do not reference specific paper content (you have none).

Phase 2 — Paper-visible review

You will receive:

  • The same sprint contract.
  • Your Phase 1 output wrapped in <phase1_output>...</phase1_output> tags.
  • Full paper content.

Read the full file on GitHub · 275 lines

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.

  1. 8d ago First seen · 275 lines · 22 tokens per session scan A 7c332cf0b0ca

Subscribe to this mod's changes

domain_reviewer_agent is an agent published in the GitHub repository LUNARTECH-X/superpowers (16 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 2,468 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to domain-reviewer-agent, differing in 55 lines, and is treated as a copy.