paper-reader

paper-reader is a skill for Claude Code, Codex from surfmind-space/awesome-surfmind. It costs 66 tokens per session (741 once invoked), scanned A, original, MIT.

A guide for explaining academic papers, preprints, abstracts, PDFs, and technical articles in everyday language. It separates the authors' claims, measured findings, limitations, and practical meaning, while defining specialist terms.

In plain words
What is it for?
Use it to break down a paper's question, method, data or participants, results, limitations, and implications.
Why use it?
It makes dense research easier to understand without treating unsupported claims as established facts or adding details missing from the source.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

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/surfmind-space/awesome-surfmind/paper-reader
Any agent
npx skills add surfmind-space/awesome-surfmind --skill paper-reader
Clone the repo
git clone --depth 1 https://github.com/surfmind-space/awesome-surfmind

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 paper-reader

README.md
[![agentmods](https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/paper-reader.svg)](https://agentmods.dev/skills/surfmind-space/awesome-surfmind/paper-reader)
Your own site
<a href="https://agentmods.dev/skills/surfmind-space/awesome-surfmind/paper-reader"><img src="https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/paper-reader.svg" alt="Measured on agentmods" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 741 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.1 $0.00066 $0.00741
Opus 5 $0.00033 $0.00370
Sonnet 5 $0.00013 $0.00148
Haiku 4.5 $0.00007 $0.00074

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

Security

Grade A, and why

paper-reader 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 5d 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/paper-reader/SKILL.md · 41 lines

How it starts

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

Paper Reader

Make a dense paper or technical article approachable by laying out its research question, method, findings, limitations, and practical implications, defining specialized terms along the way. Never invent results, numbers, citations, identifiers, dates, benchmark names, method details, architecture details, code-release status, or findings the source doesn't contain, and never present an author's claim as a settled fact.

  1. Identify the research question, domain, and document type (full paper, preprint, abstract, or article).
  2. Extract the method, dataset or sample, assumptions, key findings, limitations, and practical implications from what is actually present.
  3. Separate the authors' claims from measured results and from your own interpretation. Use attribution such as "the authors report," "the abstract claims," or "the study found" for every result or method claim that comes from the source.
  4. Define important technical terms in plain language for non-specialists, especially statistical terms (for example hazard ratio, confidence interval, Cox model, confounder, quartile) and benchmark metrics (for example FLOPs, mAP, mIoU, top-1 accuracy).
  5. If only an abstract or a partial paper is visible, summarize what's there and state plainly what's missing. Do not infer full-paper details from the abstract: if training setup, dataset splits, ablations, statistical significance, architecture specifics, or code and weights are not visible, say they are not visible. Don't treat a single study or preprint as settled consensus, and don't overstate causality.

Report with concise headings. For explanatory summaries, use these headings unless the user requests a different format: Plain-language summary, Research question, Method and evidence, Key findings, Limitations, Why it matters, and Questions to verify. Preserve exact names, numbers, links, arXiv or DOI identifiers, submission dates, currencies, percentages, confidence intervals, sample sizes, benchmark names, and benchmark scores; include all reported headline metrics, not just the largest or most familiar ones.

Read the full file on GitHub · 41 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. 5d ago First seen · 41 lines · 66 tokens per session scan A a6f7fbc4f51c

Subscribe to this mod's changes

paper-reader is a skill published in the GitHub repository surfmind-space/awesome-surfmind (5 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 741 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-31.

Related

Other skills, from other repositories

cs-master

Expert computer scientist for algorithms, complexity analysis, and distributed systems.

lubluniky/awesome-agent-blueprints · 15 tokens

guidance

回答用户关于 QwenPaw 安装与配置的问题:优先定位并阅读本地文档,再提炼答案;若本地信息不足,兜底访问官网文档。.

agentscope-ai/QwenPaw · 44 tokens

edu-math-tutorial

数学题分步讲解视频的领域知识。适用场景:(1) 用户给出一道数学题并要求做讲解/ 解题视频;(2) 用户说"讲解这道题"、"生成解题视频"、"make a math tutorial"; (3) 需要中文数学教学视频,涉及方程、公式或几何图形。本 skill 只提供领域 知识(题目拆解、讲解节奏、旁白文案规范、版式与 KaTeX 排版风格);画面、 配音与成片一律用 Creator 原生 Element 与工具从源头构建。.

agentscope-ai/QwenPaw · 146 tokens

video-tutorial-maker

Create scripted tutorial videos with narration, TTS, aligned subtitles, MP4 rendering, and platform variants. Use when Codex needs to create or revise tutorial, explainer, product walkthrough, course, demo, or short-form videos; generate 16:9 landscape output by default unless the user explicitly asks for 9:16, 1:1…

guanyang/super-publisher · 81 tokens

hidden-talents

Interview you in depth to surface overlooked or suppressed talents and write your Personal Talent Manual.

coolTheWorld/evolution-skills · 21 tokens

socratic

Diagnose a confusion Socratically, one question at a time, until the question actually worth answering surfaces — then answer that one.

coolTheWorld/evolution-skills · 30 tokens