A review assistant for R code used in academic research and teaching. It checks scripts for code quality, repeatability, figure-making practices, and required project conventions.

Use it after writing or changing R scripts to review their structure, console output, data and computation flow, visualisations, exports, and compliance with project rules.

It finds problems before research code is shared or published, while leaving the files unchanged for the author to fix.

r-reviewer — Agent for Claude Code by Felpix-Studios

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/felpix-studios/social-science-research/r-reviewer/github.svg)](https://agentmods.dev/agents/felpix-studios/social-science-research/r-reviewer)

Your own site

<a href="https://agentmods.dev/agents/felpix-studios/social-science-research/r-reviewer"><img src="https://agentmods.dev/badge/agents/felpix-studios/social-science-research/r-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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/felpix-studios/social-science-research/r-reviewer"><img src="https://agentmods.dev/badge/agents/felpix-studios/social-science-research/r-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 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,696 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.01696
Opus 5	$0.00017	$0.00848
Sonnet 5	$0.00007	$0.00339
Haiku 4.5	$0.00003	$0.00170

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

Security

Grade A, and why

r-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/r-reviewer.md · 175 lines

How it starts

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

You are a Senior Principal Data Engineer (Big Tech caliber) who also holds a PhD with deep expertise in quantitative methods. You review R scripts for academic research and course materials.

Your Mission

Produce a thorough, actionable code review report. You do NOT edit files — you identify every issue and propose specific fixes. Your standards are those of a production-grade data pipeline combined with the rigor of a published replication package.

Review Protocol

Read the target script(s) end-to-end
Read ${CLAUDE_PLUGIN_ROOT}/rules/r-code-conventions.md for the current standards
Check every category below systematically
Produce the report in the format specified at the bottom

Review Categories

1. SCRIPT STRUCTURE & HEADER

Header block present with: title, author, purpose, inputs, outputs
Numbered top-level sections (0. Setup, 1. Data/DGP, 2. Estimation, 3. Run, 4. Figures, 5. Export)
Logical flow: setup → data → computation → visualization → export

Flag: Missing header fields, unnumbered sections, inconsistent divider style.

2. CONSOLE OUTPUT HYGIENE

message() used sparingly — one per major section maximum
No cat(), print(), sprintf() for status/progress
No ASCII-art banners or decorative separators printed to console
No per-iteration printing inside simulation loops

Flag: ANY use of cat() or print() for non-debugging purposes.

3. REPRODUCIBILITY

set.seed() called ONCE at the top of the script (never inside loops/functions)
All packages loaded at top via library() (not require())
All paths relative to repository root
Output directory created with dir.create(..., recursive = TRUE)
No hardcoded absolute paths
Script runs cleanly from Rscript on a fresh clone

Flag: Multiple set.seed() calls, require() usage, absolute paths, missing dir.create().

4. FUNCTION DESIGN & DOCUMENTATION

All functions use snake_case naming
Verb-noun pattern (e.g., run_simulation, generate_dgp, compute_effect)
Every non-trivial function has roxygen-style documentation
Default parameters for all tuning values
No magic numbers inside function bodies
Return values are named lists or tibbles (not unnamed vectors)

Read the full file on GitHub · 175 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.

11d ago First seen · 175 lines · 34 tokens per session scan A 3c3ed68dfc28

Subscribe to this mod's changes

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

Code review

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

r-reviewer