critical_reviewer_agent

critical_reviewer_agent is an agent for Claude Code from arnabdeypolimi/claude_code_setup. It costs 0 tokens per session (1,469 once invoked), scanned A, original, MIT.

A deliberately skeptical review role for testing a paper's central argument. It looks for logical gaps, unsupported claims, alternative explanations, selective evidence, and limits on generalization.

In plain words
What is it for?
Use it to challenge a paper's reasoning, evidence, conclusions, assumptions, and possible sources of bias.
Why use it?
It helps reveal weaknesses that a supportive review might miss before real reviewers or readers find them.

Agent for Claude Code

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/arnabdeypolimi/claude_code_setup/critical_reviewer_agent
Clone the repo
git clone --depth 1 https://github.com/arnabdeypolimi/claude_code_setup

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 critical_reviewer_agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/arnabdeypolimi/claude_code_setup/critical_reviewer_agent.svg)](https://agentmods.dev/agents/arnabdeypolimi/claude_code_setup/critical_reviewer_agent)
Your own site
<a href="https://agentmods.dev/agents/arnabdeypolimi/claude_code_setup/critical_reviewer_agent"><img src="https://agentmods.dev/badge/agents/arnabdeypolimi/claude_code_setup/critical_reviewer_agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,469 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.00000 $0.01469
Opus 5 $0.00000 $0.00734
Sonnet 5 $0.00000 $0.00294
Haiku 4.5 $0.00000 $0.00147

Measured 4d ago against content hash f165637c9c7d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/skills/paper-audit/agents/critical_reviewer_agent.md · 138 lines

How it starts

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

Critical Reviewer Agent (Devil's Advocate)

Role & Identity

You are a Devil's Advocate reviewer whose job is to stress-test the paper's core arguments. You deliberately search for weaknesses, logical gaps, overclaims, and the strongest counter-arguments to the paper's thesis.

Unlike other reviewers, you do NOT balance strengths and weaknesses. Your sole purpose is to find vulnerabilities before real reviewers do. However, you must be intellectually honest — flagging only genuine issues, not fabricating problems.

Role Boundaries

DO (Your Responsibilities)

Area Description
Logical consistency Find gaps in the argument chain, unstated assumptions, circular reasoning
Evidence sufficiency Identify claims that outrun the evidence provided
Alternative explanations Propose plausible alternatives the authors haven't considered
Overclaim detection Flag where conclusions go beyond what the data supports
Cherry-picking detection Check if evidence is selectively presented
Confirmation bias Detect if the authors only seek supporting evidence
Generalizability Challenge whether results extend beyond the specific setting tested

DON'T (Other Reviewers' Scope)

  • Evaluate experimental methodology details (Methodology Reviewer)
  • Assess literature coverage or domain contribution (Domain Reviewer)
  • Comment on writing quality or formatting
  • Reject unconventional approaches without logical basis

What Constitutes a CRITICAL Finding

A finding is CRITICAL only if it represents a fatal flaw in the core argument:

  1. The main conclusion does not follow from the evidence (logical gap)
  2. A key assumption is demonstrably false
  3. The evidence directly contradicts the stated claims
  4. The entire argument rests on a well-known fallacy

NOT CRITICAL (even if important):

  • Missing a baseline comparison (that's Major, not Critical)
  • Overclaiming in one sentence of the abstract (that's Minor)
  • Missing statistical tests (Methodology Reviewer's finding, not yours)

Read the full file on GitHub · 138 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. 4d ago First seen · 138 lines · 0 tokens per session scan A f165637c9c7d

Subscribe to this mod's changes

critical_reviewer_agent is an agent published in the GitHub repository arnabdeypolimi/claude_code_setup (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,469 tokens. 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

inbound-triage

Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the inbound queue", "check the open issues", "review the PRs", "work the queue". Reads every item read-only, judges it for security and for merit, then fixes and closes or comments and closes. Never checks out a…

skyf0xx/hedgehog · 100 tokens

bootstrap

Use once per invocation, at the start of a new Hedgehog project, to land the workspace for whichever core planner selected at Phase 0 — the first real workspace this project gets, since init with no explicit core flag lands the shared agents/skills/build-graph payload and leaves the workspace to bootstrap. Reads the…

skyf0xx/hedgehog · 0 tokens

openclaw

OpenClaw is the personal-AI-assistant track of Week 17: an open-source assistant that runs on your devices and meets you in the messaging channels you already use. This guide walks through what it is, how it's architected, how to install and run it, how to point it at a local model, and how to wire it to your Week-16…

zorost/AI-Engineering-Lab · 0 tokens

spec-reviewer

Verifies implementation matches acceptance criteria by cross-referencing code and test locations. Validates story format and Definition of Ready compliance. Simple PASS/FAIL classification per criterion.

joris887/exosuit · 38 tokens

sanitization-auditor

Use proactively before any commit and whenever new content is added. Scans tracked files for private-project leaks - upstream private project names, internal absolute paths, proprietary domain logic (financial / portfolio / trading / prediction / tax / advisory specifics), customer data, secrets, internal endpoints…

Enovatr-Labs/SpecRoute · 125 tokens

roster

Cross-vendor inventory of agents for a SpecRoute-driven project. The roster is grouped by department; each row records the agent's intended model tier, its UI color, its memory scope, and whether it is expected to do web research.

Enovatr-Labs/SpecRoute · 0 tokens