opponent

opponent is a command for Claude Code from josefslerka/study-kit. It costs 23 tokens per session (601 once invoked), scanned A, original, MIT.

A journal-style referee report that judges whether a study is worth publishing. It examines the study’s contribution, originality, method, scope, argument, and relationship to existing research.

In plain words
What is it for?
Use it after an integrity review to assess triviality, overstatement, method, journal fit, overall coherence, scholarly dialogue, and novelty against the supplied research sources.
Why use it?
It separates truth-checking from publication judgment: a review checks whether claims are supported, while this report asks whether the work adds enough to the field.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it after an integrity review to assess triviality, overstatement, method, journal fit, overall coherence, scholarly dialogue, and novelty against the supplied research sources.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/josefslerka/study-kit/opponent
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/josefslerka/study-kit

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 opponent

README.md
[![agentmods](https://agentmods.dev/badge/commands/josefslerka/study-kit/opponent/github.svg)](https://agentmods.dev/commands/josefslerka/study-kit/opponent)
Your own site
<a href="https://agentmods.dev/commands/josefslerka/study-kit/opponent"><img src="https://agentmods.dev/badge/commands/josefslerka/study-kit/opponent/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 opponent

Your own site · 80×15
<a href="https://agentmods.dev/commands/josefslerka/study-kit/opponent"><img src="https://agentmods.dev/badge/commands/josefslerka/study-kit/opponent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 601 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.00023 $0.00601
Opus 5.5 $0.00009 $0.00240
Sonnet 5.5 $0.00005 $0.00120
Haiku 4.5 $0.00002 $0.00060

Measured 2mo ago against content hash 1f9f23ab7f8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

opponent 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 2mo 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.

en/.claude/commands/opponent.md · 41 lines

What it actually says

Write the report a journal REFEREE would write on the study. This is NOT /review: /review verifies the study is TRUE (integrity against raw_primary/); /opponent judges whether it's WORTH PUBLISHING (contribution and positioning against raw_secondary/). Run ONLY AFTER /review — truth before worth.

Split two planes hard:

A) WHAT YOU JUDGE YOURSELF (from the study text + raw_primary/ + raw_secondary/):

  • Triviality: isn't the thesis a banal truth no one denies?
  • Overstatement: does the conclusion claim more than the body shows? (compare the title/abstract claim with what's documented)
  • Method: defensible or reductive? does the declared lens hold (no diagnosing the author)?
  • Scope and register: right for the target journal (from idea.md)? register not out of genre?
  • Coherence of the whole: does the argument hold as a whole? (at the level of construction, not single quotes — that's /review)
  • Dialogue with scholarship: does the study engage what IS in raw_secondary/, or ignore / conveniently bend a source there?

B) WHAT YOU JUDGE ONLY AGAINST raw_secondary/ (and otherwise NOT):

  • Novelty: does the study fill a real gap, or retell what the loaded scholarship already says?
  • Positioning: does it fit this scholarly debate? KEY RULE (anti-fabrication of novelty): assert novelty and positioning STRICTLY against what is in raw_secondary/. Where the field is not loaded, DON'T GUESS — write explicitly: "against the loaded sources there's a gap X; whether wider scholarship has already filled it, I CAN'T JUDGE — the monograph dialogue is missing". Never claim "this is new" without support; never invent what an unloaded source would contain. When a judgment lacks a source, escalate to the human ("a source belongs here, get it"), not a guess.

When raw_secondary/ is empty: do NOT do plane B at all, just note in the report that contribution and novelty can't be judged without loaded scholarship — and do plane A normally.

OUTPUT process/opponent-report.md: summary of the study (1 paragraph, factual) · claimed contribution (as you read it from the text) · strengths · main objections (description + what the author would have to add + severity: major/medium/minor) · minor points · suitability for the target journal · verdict (accept / revise / reject) · 1 most important sentence. Log it. Propose what /revise handles and what the human must (typically: get and place a source into raw_secondary/).

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. 2mo ago First seen · 41 lines · 23 tokens per session scan A 1f9f23ab7f8c

Subscribe to this mod's changes

opponent is a command published in the GitHub repository josefslerka/study-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 601 once invoked, about $0.0001 per session on Opus 5.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.

Related

opponent compared with commands from other repositories

opponent next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
opponentjosefslerka/study-kitCommand74mo agoMITA23Claude Code
verify-mathflonat/flonat-researchCommand1493d agoMITA81Claude Code
difffa-mc/vibe-cadingCommand824d agoAGPL-3.0A14Claude Code
arg-diagramMasqiller/ARG-RESEARCHER-V4.1Command65mo agoMITA14Claude Code
plotzhouziyue233/great-econometricsCommand86mo agononeA44Claude Code
graphite-morphology-classifyDaxxSec/cognitropy-labCommand14mo agononeA0Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code