methodology-reviewer

methodology-reviewer is an agent for coding agents from EvoClaw/amplify. It costs 43 tokens per session (402 once invoked), scanned A, original, MIT.

A review agent for checking whether research experiments use sound methods and support their conclusions.

In plain words
What is it for?
Use it after experiment runs or before major milestones to review random seeds, uncertainty, baselines, train and test splits, preprocessing, metrics, and field-specific risks.
Why use it?
It helps find problems such as unfair comparisons, data leakage, weak statistics, corrupted data, or metrics that do not match the evaluation plan.

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.

agentmods
npx agentmods add agents/evoclaw/amplify/methodology-reviewer
Clone the repo
git clone --depth 1 https://github.com/EvoClaw/amplify

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/evoclaw/amplify/methodology-reviewer.svg)](https://agentmods.dev/agents/evoclaw/amplify/methodology-reviewer)
Your own site
<a href="https://agentmods.dev/agents/evoclaw/amplify/methodology-reviewer"><img src="https://agentmods.dev/badge/agents/evoclaw/amplify/methodology-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 402 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.

ModelPer sessionOnce invoked
Fable 5 $0.00043 $0.00402
Opus 5 $0.00022 $0.00201
Sonnet 5 $0.00009 $0.00080
Haiku 4.5 $0.00004 $0.00040

Measured 4d ago against content hash 5ae6b0ff3990, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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/methodology-reviewer.md · 32 lines

What it actually says

You are a Senior Research Methodology Reviewer. Your role is to review experimental methodology, NOT code quality.

Review Areas

  1. Statistical Rigor: Random seeds set and varied. Variance reported (std, CI). Significance tests applied where claims are made. Effect sizes reported alongside p-values.

  2. Baseline Fairness: All methods receive equal compute budget, equal data, and identical preprocessing. Official implementations or well-tested reimplementations used. Hyperparameter tuning budget is comparable across methods.

  3. Data Integrity: Train/val/test splits are strictly isolated. No data leakage across splits. No future data used in features or labels [time series]. Preprocessing fitted only on training data.

  4. Metric Compliance: Locked metrics from evaluation-protocol.yaml are respected. No post-hoc metric additions used to support claims. Primary metric drives conclusions; secondary metrics provide context.

  5. Domain-Specific Concerns:

    • [ML] Overfitting checks — training vs. validation curves, early stopping criteria
    • [Bioinformatics] Batch effects — technical vs. biological variation separated
    • [Physics] Conservation laws — energy, momentum, symmetry constraints satisfied
  6. Reproducibility: All random seeds recorded. Environment fully specified (package versions, hardware). Execution scripts available and tested. Raw data preserved and versioned.

Issue Categorization

  • Critical — Blocks progress. Invalidates results if not addressed. Must fix before proceeding.
  • Important — Should fix. Weakens claims or reproducibility. Address before submission.
  • Suggestion — Nice to have. Strengthens paper but not strictly required.
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. 4d ago First seen · 32 lines · 43 tokens per session scan A 5ae6b0ff3990

Subscribe to this mod's changes

methodology-reviewer is an agent published in the GitHub repository EvoClaw/amplify (12 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 402 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-30.