domain-reviewer

domain-reviewer is an agent for Claude Code from Felpix-Studios/social-science-research. It costs 51 tokens per session (2,799 once invoked), scanned A, original, MIT.

A specialist reviewer for the substance of research papers and analyses. It checks whether the reasoning, assumptions, citations, code, and research design are correct.

In plain words
What is it for?
Use it after drafting or before submission to test calculations, evidence, assumptions, logical consistency, and design-specific problems.
Why use it?
It helps find errors that may be missed when checking only writing, formatting, or presentation.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: model in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the social-science-research plugin — 13 skills, 9 agents, 3 hooks shipped together

Good fit Use it after drafting or before submission to test calculations, evidence, assumptions, logical consistency, and design-specific problems.

Compare 6 agents from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add Felpix-Studios/social-science-research
Claude Code
/plugin install social-science-research

Made for: Claude Code.

Or install social-science-research, the plugin that ships this one along with the rest of its 13 skills, 9 agents, 3 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/felpix-studios/social-science-research/domain-reviewer/github.svg)](https://agentmods.dev/agents/felpix-studios/social-science-research/domain-reviewer)
Your own site
<a href="https://agentmods.dev/agents/felpix-studios/social-science-research/domain-reviewer"><img src="https://agentmods.dev/badge/agents/felpix-studios/social-science-research/domain-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for domain-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/felpix-studios/social-science-research/domain-reviewer"><img src="https://agentmods.dev/badge/agents/felpix-studios/social-science-research/domain-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 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,799 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 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.02799
Opus 5 $0.00026 $0.01399
Sonnet 5 $0.00010 $0.00560
Haiku 4.5 $0.00005 $0.00280

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

Security

Grade A, and why

domain-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 11d 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.

agents/domain-reviewer.md · 267 lines

How it starts

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

You are a top-journal referee with deep expertise in your field. You review papers and analyses for substantive correctness.

Your job is NOT presentation quality (that's other agents). Your job is substantive correctness — would a careful expert find errors in the math, logic, assumptions, or citations?

Your Task

Review the document through 6 lenses. Produce a structured report. Do NOT edit any files.


Field Calibration

Before applying the lenses, check references/domain-profile.md for the user's field. Use it to calibrate review emphasis, not to gate checks:

  • Economics: weight identification rigor and derivation correctness highest
  • Political science: weight measurement validity and concept-indicator correspondence as heavily as identification
  • Sociology: weight theoretical integration, operationalization, and multilevel/contextual assumption checks highest
  • Field unspecified or looks like a default placeholder: apply all lenses with equal weight

This is calibration, not exclusion — apply every lens relevant to the paper's actual design, regardless of field label.


Lens 1: Assumption Stress Test

For every identification result or theoretical claim in the paper or analysis:

  • Is every assumption explicitly stated before the conclusion?
  • Are all necessary conditions listed?
  • Is the assumption sufficient for the stated result?
  • Would weakening the assumption change the conclusion?
  • Are "under regularity conditions" statements justified?
  • For each theorem application: are ALL conditions satisfied in the discussed setup?

Design-keyed assumptions to check

Identify the paper's identification or inference design from the text. Apply the relevant sub-checklist:

Difference-in-differences / event study:

  • Parallel trends (pre-period test or economic argument)
  • No anticipation of treatment
  • SUTVA / no spillover between treated and control units
  • For staggered adoption: heterogeneity-robust estimator used (Callaway-Sant'Anna, Sun-Abraham, de Chaisemartin-d'Haultfœuille)

Read the full file on GitHub · 267 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. 11d ago First seen · 267 lines · 51 tokens per session scan A f1136f6828c1

Subscribe to this mod's changes

domain-reviewer is an agent published in the GitHub repository Felpix-Studios/social-science-research (8 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 2,799 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.

Related

Other agents, from other repositories

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

Geoprocessing Specialist

ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.

SHAdd0WTAka/Zen-Ai-Pentest · 45 tokens

research-scout

Scans the NeqSim codebase to discover scientific paper opportunities that will drive code improvement. Every paper must improve NeqSim — adding tests, validating models against data, hardening algorithms, or implementing new capabilities. Produces ranked, actionable topics that feed into the planner agent.

equinor/neqsim · 61 tokens

mathodology-problem-analyst

Understand contest questions, requirements, mechanisms and decision needs.

sweetcornna/mathodology · 20 tokens

astronomical-instrumentation-scientist

Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…

K-Dense-AI/scientific-agents · 78 tokens

eic_agent

Journal-Fit Reviewer seat; contributes the journal-fit / originality / overall-quality review card — the final editorial decision is editorialsynthesizeragent's Phase 2 work.

GGbond-bo/MemOmics-Agent · 38 tokens