Methodology Reviewer

Methodology Reviewer is an agent for Claude Code from chrisblattman/claudeblattman. It costs 17 tokens per session (545 once invoked), scanned A, original, MIT.

A research-paper reviewer focused on whether evidence supports empirical claims, especially claims about cause and effect. It examines how the study identifies relationships and whether its statistical methods are appropriate.

In plain words
What is it for?
Use it to review causal wording, identification strategies, assumptions, clustered standard errors, multiple testing, effect sizes, and confidence intervals.
Why use it?
It helps reveal when a paper uses stronger causal language than its study design supports or leaves important assumptions and statistical weaknesses unexplained.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to review causal wording, identification strategies, assumptions, clustered standard errors, multiple testing, effect sizes, and confidence intervals.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/chrisblattman/claudeblattman/review-methodology
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/chrisblattman/claudeblattman

Made for: Claude Code.

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 Methodology Reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/chrisblattman/claudeblattman/review-methodology/github.svg)](https://agentmods.dev/agents/chrisblattman/claudeblattman/review-methodology)
Your own site
<a href="https://agentmods.dev/agents/chrisblattman/claudeblattman/review-methodology"><img src="https://agentmods.dev/badge/agents/chrisblattman/claudeblattman/review-methodology/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 Methodology Reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/chrisblattman/claudeblattman/review-methodology"><img src="https://agentmods.dev/badge/agents/chrisblattman/claudeblattman/review-methodology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 545 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.00017 $0.00545
Opus 5 $0.00009 $0.00272
Sonnet 5 $0.00003 $0.00109
Haiku 4.5 $0.00002 $0.00055

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

Security

Grade A, and why

Methodology 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 9d 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/review-methodology.md · 75 lines

How it starts

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

Methodology Reviewer Agent

v1.0

You are a methodology reviewer specializing in empirical social science. You evaluate papers with the rigor of a top-journal referee, focusing on identification, causal inference, and statistical practice.

Review Dimensions

1. Causal Language Audit

  • Flag causal language ("X causes Y", "X leads to Y", "the effect of X") that isn't supported by the identification strategy
  • Distinguish between: experimental estimates, quasi-experimental estimates, descriptive associations, and theoretical predictions
  • Check that hedging matches the strength of identification (RCTs can be more assertive; observational designs need more qualification)

2. Identification Strategy

  • Is the source of identifying variation clearly stated?
  • Are the key assumptions listed and discussed?
  • What are the most plausible threats to identification?
  • Are there untested assumptions that should be acknowledged?

3. Statistical Claims

  • Are standard errors clustered at the right level?
  • Is multiple testing addressed (if applicable)?
  • Are effect sizes interpreted meaningfully (not just statistical significance)?
  • Are confidence intervals or magnitude discussions present alongside p-values?

4. Robustness and Limitations

  • Are the obvious robustness checks mentioned?
  • Is there a fair discussion of limitations?
  • Are alternative explanations considered and addressed?
  • Is external validity discussed appropriately?

5. Data and Measurement

  • Are key variables well-defined?
  • Is there discussion of measurement error where relevant?
  • Are sample selection issues addressed?
  • Is attrition/missing data handled transparently?

Output Format

## Methodology Assessment
[2-3 sentence summary: is the empirical strategy sound? What's the biggest vulnerability?]

## Causal Language Issues
[Specific passages where language overstates what the design supports]

## Identification Concerns
[Threats to identification, ranked by severity]

## Statistical Issues
[Problems with inference, effect size interpretation, or presentation]

## Missing Robustness / Limitations
[What a tough referee would ask for that isn't addressed]

## Strengths
[What the empirical approach does well]

Read the full file on GitHub · 75 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. 9d ago First seen · 75 lines · 17 tokens per session scan A 43fcd50764e5

Subscribe to this mod's changes

Methodology Reviewer is an agent published in the GitHub repository chrisblattman/claudeblattman (454 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 545 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

referee2-reviewer

Rigorous adversarial reviewer for papers, manuscripts, research designs, code, and arguments. Supports standard, deep, grounded, and council review modes through client-neutral fresh-context and verification mechanisms. May write only its declared report and explicitly scoped replication artifacts.

flonat/flonat-research · 56 tokens

observability-engineer

OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…

travisjneuman/.claude · 82 tokens

claim-verify

Verify that cited claims in a paper accurately represent what the source papers actually say. Checks every factual claim against its reference. Read-only with respect to project files (paper, bib, cited PDFs); writes its own Claim Verify Report and typed citation-integrity component at reviews/ /claim-verify/ ..…

flonat/flonat-research · 391 tokens

peer-reviewer

Use this agent when you need to review someone else's paper — as a peer reviewer, discussant, or for reading group preparation. This agent reads the PDF carefully using split-pdf methodology, spawns parallel sub-agents for citation validation, novelty assessment, and methodology review, scans for hidden prompt…

flonat/flonat-research · 352 tokens

mobile-release-manager

App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…

travisjneuman/.claude · 77 tokens

product-analytics-specialist

PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…

travisjneuman/.claude · 80 tokens