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.
npx agentmods add skills/ethan2409/paperflow/paper-readernpx skills add Ethan2409/PaperFlow --skill paper-readergit clone --depth 1 https://github.com/Ethan2409/PaperFlowWhat 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 | $0.00069 | $0.03637 |
| Opus 5 | $0.00034 | $0.01818 |
| Sonnet 5 | $0.00014 | $0.00727 |
| Haiku 4.5 | $0.00007 | $0.00364 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paper Reader: 文献精读与认知重构
读论文不是做摘要，是猎取思想。本Skill把PDF论文拆解成「不懂这个领域的聪明人也能看懂并复述」的认知框架，最终输出带图片的结构化HTML精读笔记。
前置步骤：读取配置
开始前先读取项目根目录下的 config.yaml（如不存在则读取 config.example.yaml 并提示用户复制修改）。从配置中获取：
paths.python_exe— Python 解释器路径literature.pdf_dir— PDF 论文存放目录（按 W{周号}/ 子目录组织）literature.html_output_dir— 精读 HTML 输出目录（按 W{周号}/ 子目录组织）
路径约定
| 用途 | 路径 | 说明 |
|---|---|---|
| PDF输入 | {literature.pdf_dir}/W{周号}/ |
按ISO周号组织，如 W24。从 config.yaml 读取 pdf_dir |
| HTML输出 | {literature.html_output_dir}/W{周号}/ |
自动创建对应周目录。从 config.yaml 读取 |
| 图片资源 | {输出目录}/{论文名}_assets/ |
与HTML同目录下的assets子目录 |
| 提取工具 | <SKILL_DIR>/assets/extract_figures.py |
PDF文字+图片提取脚本 |
周号规则：默认使用当前ISO周号（python -c "import datetime; print(datetime.date.today().isocalendar()[1])"）。用户可指定周号，如"处理W19的所有论文"。
路径说明：所有路径通过项目根目录的
config.yaml集中配置。安装后请复制config.example.yaml为config.yaml并修改其中的路径为你本机的实际路径。详见项目 README.md 的"安装与配置"章节。
触发条件
用户消息包含以下任一关键词时触发：
- "精读论文" / "文献精读" / "paper reader" / "paper reading"
- "读这篇论文" / "解析文献" / "拆解这篇文献"
- "处理本周文献" / "处理W{数字}的论文"
工作流（严格按此顺序执行）
Phase 1: 确定范围并扫描
-
确定周号：
- 若用户未指定，用
python -c "import datetime; print(datetime.date.today().isocalendar()[1])"获取当前周 - 格式化为
W{周号}（如W24）
- 若用户未指定，用
-
扫描PDF：
- 用
ls或Get-ChildItem列出{literature.pdf_dir}/W{周号}/*.pdf - 若无PDF文件，告知用户并结束
- 向用户展示待处理清单，请求确认后再继续
- 用
-
创建输出目录：
mkdir -p "{literature.html_output_dir}/W{周号}"
Phase 2: 逐篇处理循环
对每个PDF文件，按以下子步骤执行：
2a. 提取文字 + 图片
运行提取脚本：
"{python_exe}" \
"<SKILL_DIR>/assets/extract_figures.py" \
--pdf "{literature.pdf_dir}/W{周号}/{论文文件名}.pdf" \
--output-dir "{literature.html_output_dir}/W{周号}/{论文名}_assets"
脚本输出：
{论文名}_meta.json— 元数据（full_text, figures列表）- 提取的图片文件（
fig_1.png,fig_2_rendered.png等）
读取 _meta.json 获取 full_text 和 figures 信息。
扫描版PDF检测（必须执行）：读取 _meta.json 后，检查 text_length。如果 text_length < 500（意味着几乎所有页面都无文字层，是扫描图片版PDF），立即停止处理该篇，告知用户：
"这篇「{论文名}」是扫描图片版PDF，fitz 无法提取文字（仅 {text_length} 字符）。请替换为文字版PDF后重试。"
- 跳过该篇，继续处理列表中下一篇
- 严禁尝试OCR、渲染页面截图等任何降级方案——这些不可靠且浪费时间
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 326 lines · 69 tokens per session scan A d477c8567eea
paper-reader is a skill published in the GitHub repository Ethan2409/PaperFlow (9 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 3,637 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.