1-osp-summary

1-osp-summary is a skill for Claude Code, Codex from amirkiarafiei/open-scholar-peer. It costs 19 tokens per session (1,081 once invoked), scanned C, original, MIT.

A research-paper analysis step that extracts a paper's main claims, methods, and supporting evidence into a structured summary. It requires readable paper text.

In plain words
What is it for?
Use it to summarize what a paper says, how it works, and what evidence supports its conclusions.
Why use it?
It turns a paper into consistent notes that later review steps can use, rather than making each step reread and interpret the whole paper.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents).

Good fit Use it to summarize what a paper says, how it works, and what evidence supports its conclusions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amirkiarafiei/open-scholar-peer/1-osp-summary
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.

Any agent
npx skills add amirkiarafiei/open-scholar-peer --skill 1-osp-summary
Clone the repo
git clone --depth 1 https://github.com/amirkiarafiei/open-scholar-peer

Made for: Claude Code, Codex.

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 1-osp-summary

README.md
[![agentmods](https://agentmods.dev/badge/skills/amirkiarafiei/open-scholar-peer/1-osp-summary/github.svg)](https://agentmods.dev/skills/amirkiarafiei/open-scholar-peer/1-osp-summary)
Your own site
<a href="https://agentmods.dev/skills/amirkiarafiei/open-scholar-peer/1-osp-summary"><img src="https://agentmods.dev/badge/skills/amirkiarafiei/open-scholar-peer/1-osp-summary/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 1-osp-summary

Your own site · 80×15
<a href="https://agentmods.dev/skills/amirkiarafiei/open-scholar-peer/1-osp-summary"><img src="https://agentmods.dev/badge/skills/amirkiarafiei/open-scholar-peer/1-osp-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,081 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00019 $0.01081
Opus 5.5 $0.00008 $0.00432
Sonnet 5.5 $0.00004 $0.00216
Haiku 4.5 $0.00002 $0.00108

Measured 22d ago against content hash 7d48db4e7922, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

1-osp-summary scanned grade C with 1 finding 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 22d 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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

that the venue is unknown. Mention `/0-osp-onboarding` once. Do not insist, and do not refuse.
extensions/.agents/skills/1-osp-summary/SKILL.md · 83 lines

How it starts

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

/1-osp-summary — Internal Compression

Extracts the paper's claims, method, and evidence into a structured summary Ŝ that downstream personas rely on.

Activation

Invoke the osp-summary-agent skill. The agent assumes the Summary Agent persona and follows that skill's protocol exactly.

Inputs — none of these is a gate

  • phases.onboarding.status == "completed" in session.json. If onboarding was skipped you have no venue and no review guidelines; extract the summary anyway, and record under NOTE and in Provenance that the venue is unknown. Mention /0-osp-onboarding once. Do not insist, and do not refuse.

The one thing that cannot be worked around

Every other input in this protocol is optional. This one is not: with no readable text of the paper there is nothing to review, so this guard stops — and it is the only place in Open ScholarPeer that does.

PDF/DOCX/TEX in .brain/input/ is not enough on its own; a binary path handed to the agent is the single biggest cause of silent downstream failure.

Before activating the skill, verify in this order:

  1. .brain/input/paper.md exists and is readable — ideal case, proceed.
  2. .brain/input/paper.md is missing but a PDF/DOCX exists — try to convert it now using the markitdown MCP tool (convert_to_markdown). Save the result to .brain/input/paper.md. Update session.json.paper.parsed_path.
  3. markitdown MCP is unavailable AND only a PDF/DOCX is present — stop here, and say why in one line: there is no readable text to summarise. Print:

    Paper at .brain/input/<file> is in a binary format and markitdown MCP is not available. Either: (a) install markitdown — uvx markitdown-mcp --help confirms it is fetchable; plain uvx markitdown-mcp starts the server and waits, which looks like a hang — or (b) convert the paper manually and place the markdown at .brain/input/paper.md, or (c) if your host tool reads this format natively (Claude Code reads PDFs, for one), read it yourself, write the extracted text to .brain/input/paper.md, and re-run.

  4. Nothing in .brain/input/ — stop here too; there is no paper. Point at /0-osp-onboarding, which will help locate it.

Read the full file on GitHub · 83 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. 22d ago First seen · 83 lines · 19 tokens per session scan C 7d48db4e7922

Subscribe to this mod's changes

1-osp-summary is a skill published in the GitHub repository amirkiarafiei/open-scholar-peer (48 stars, last pushed 12d ago), licensed MIT. It adds 19 tokens to every session and 1,081 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-24.

Related

Other skills, from other repositories

ara-rigor-reviewer

Performs ARA Seal Level 2 semantic epistemic review on Agent-Native Research Artifacts, scoring six dimensions (evidence relevance, falsifiability, scope calibration, argument coherence, exploration integrity, methodological rigor) and producing a constructive, severity-ranked report with a Strong Accept-to-Reject…

Orchestra-Research/AI-Research-SKILLs · 91 tokens

eval-design-forensics

Audit whether a paper's EVALUATION DESIGN actually measures what it claims and whether its reporting is complete — the validity layer family D (experiment-forensics) cannot reach. Three patterns: train/test leakage means the reported score may not measure generalization (HP-EVAL-LEAKAGE — adopts the Kapoor & Narayanan…

wanshuiyin/Anti-Autoresearch · 458 tokens

anti-autoresearch

End-to-end substantive-integrity forensic sweep of a research paper (especially autoresearch / AI-Scientist-style output). Orchestrates the whole pipeline: ingest (arxiv-id | pdf | dir → working dir + pdftotext for L0) → /evidence-ledger (artifact manifest + observability level L0/L1/L2 + span-anchored claims.json) →…

wanshuiyin/Anti-Autoresearch · 275 tokens

baseline-comparison-audit

Audit whether a paper's baseline comparisons are COMPLETE, FAIR, and SIGNIFICANT: a required recent SOTA baseline is missing while 'best/SOTA' is claimed (HP-MISSING-BASELINE); a baseline is undertuned / given less compute-tuning-data, run at a mismatched config, or the equal-budget ablation-as-baseline is absent…

wanshuiyin/Anti-Autoresearch · 310 tokens

experiment-forensics

Audit experiment integrity against the evidence ledger. At L2 (repo + result files present) a fresh cross-model reviewer reads the eval code line-by-line for fake/derived ground truth, score self-normalization, phantom results (a paper number with no backing file/key), dead/uncalled metric code, verified-scope…

wanshuiyin/Anti-Autoresearch · 237 tokens

proof-derivation-forensics

Family-G proof & derivation integrity forensics: does a THIRD PARTY's written proof/derivation actually establish its theorem, or does it skip an obligation, assume its own conclusion, take an invalid step, drift a symbol's meaning, or smuggle an unstated assumption? Decides from the WRITTEN proof/derivation …

wanshuiyin/Anti-Autoresearch · 222 tokens