agentmods.dev

referee-mock

referee-mock is a skill for Claude Code, Codex from matthewdigiuseppe/MStack. It costs 62 tokens per session (991 once invoked), scanned A, original, MIT.

A simulated journal referee report on a nearly finished academic paper. It reviews the paper from a chosen perspective, such as methodologist, theorist, subject expert, or editor, and gives comments plus a recommendation.

In plain words
What is it for?
Use it on a complete draft to receive major and minor comments, test whether the contribution is convincing, and assess likely reactions at the target journal.
Why use it?
It reveals problems that real reviewers may raise before submission. This gives the author a chance to strengthen the argument, evidence, presentation, and journal fit.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the mstack plugin — 38 skills, 1 hook shipped together

not rated 14 7d ago A scan 62 tokens original MIT
View the source file matthewdigiuseppe/MStack
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 skills/matthewdigiuseppe/mstack/referee-mock
Any agent
npx skills add matthewdigiuseppe/MStack --skill referee-mock
Clone the repo
git clone --depth 1 https://github.com/matthewdigiuseppe/MStack

Made for: Claude Code, Codex.

Or install mstack, the plugin that ships this one along with the rest of its 38 skills, 1 hook.

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 referee-mock

README.md
[![agentmods](https://agentmods.dev/badge/skills/matthewdigiuseppe/mstack/referee-mock.svg)](https://agentmods.dev/skills/matthewdigiuseppe/mstack/referee-mock)
Your own site
<a href="https://agentmods.dev/skills/matthewdigiuseppe/mstack/referee-mock"><img src="https://agentmods.dev/badge/skills/matthewdigiuseppe/mstack/referee-mock.svg" alt="Measured on agentmods" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 991 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.00062 $0.00991
Opus 5 $0.00031 $0.00495
Sonnet 5 $0.00012 $0.00198
Haiku 4.5 $0.00006 $0.00099

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

Security

Grade A, and why

referee-mock 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.

skills/referee-mock/SKILL.md · 78 lines

How it starts

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

/mstack:referee-mock

Stage: write (pre-submission) Voice: referee (anchored to journal-reviewer-style)

When to invoke

When all sections of the manuscript exist in paper/sections/ and the draft is "submission-ready." This skill is your last line of defense before reviewers see it.

Argument

$ARGUMENTS (optional) — referee persona. One of:

  • methodologist (default) — prosecutes identification and inference.
  • theorist — prosecutes theoretical novelty and engagement with the literature.
  • area-expert — prosecutes empirical/contextual claims.
  • editor — prosecutes fit, contribution-per-page, and clarity.

If unrecognized, default to methodologist.

Procedure

  1. Load the manuscript.

    • Read paper/main.tex (or main.qmd) and every file under paper/sections/.
    • Read output/tables/ and output/figures/ to verify claims in the prose.
    • Read .mstack/config.yaml to know the target journal — referees calibrate to journal expectations.

  2. Load prior referee snapshots in .mstack/referee-cache/. If the same persona produced a report on an earlier draft, the new report should explicitly note what improved and what didn't.

  3. Invoke the reviewer-style skill.

    • Read voice.reviewer_style from .mstack/config.yaml; if it names a skill the user has installed, use it for voice, tone, and structural conventions.
    • Otherwise follow ${CLAUDE_PLUGIN_ROOT}/references/referee-report-conventions.md — the built-in structure and tone for an IPE / political science referee report.

  4. Write the report with the persona's bias dialed in:

    Persona Where to press hardest
    methodologist Identification, SE clustering, robustness, multiple comparisons, sample restrictions, attrition
    theorist Theoretical contribution, mechanism vs. correlation, engagement with canonical 3–5 papers, scope conditions
    area-expert Empirical/case knowledge, measurement validity, omitted contextual factors, source reliability
    editor Contribution-per-page, fit with target journal, clarity, headline-vs-evidence proportionality, length

Read the full file on GitHub · 78 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 · 78 lines · 62 tokens per session scan A 73cf1f6e666c

Subscribe to this mod's changes

referee-mock is a skill published in the GitHub repository matthewdigiuseppe/MStack (14 stars, last pushed 7d ago), licensed MIT. It adds 62 tokens to every session and 991 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-30.

ResearchWriting and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens