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 skills add KhaledSaeed18/dotclaude --skill paper-readergit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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.
[](https://agentmods.dev/skills/khaledsaeed18/dotclaude/paper-reader)<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/paper-reader"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/paper-reader/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.
<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/paper-reader"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/paper-reader.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00092 | $0.00848 |
| Opus 5.5 | $0.00037 | $0.00339 |
| Sonnet 5.5 | $0.00018 | $0.00170 |
| Haiku 4.5 | $0.00009 | $0.00085 |
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 25d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read the paper, not the abstract. The note you produce will be trusted later, when the student is writing under deadline and will not reopen the PDF, so every claim in the note must be traceable to a page or section.
Get the text
- A local PDF: extract text (
pdftotext -layout file.pdf -), and read the figures and tables where the text is unclear. - An arXiv id: fetch the LaTeX source when available (
https://arxiv.org/e-print/<id>, a gzipped tar) because it keeps equations and tables intact; otherwise the PDF (https://arxiv.org/pdf/<id>). - A DOI: resolve it to metadata with CrossRef, then ask the student for the PDF if it is not open access. Do not summarise a paper from its abstract and pretend it was read.
Read in this order
- Abstract, introduction, conclusion: what the authors claim.
- Method and setup: what they did, precisely enough to judge the claim.
- Results, including tables: what the evidence shows, including what it does not show.
- Related work and limitations: where they place themselves and what they concede.
- References: which works they lean on (candidates for
citation-graph).
The note
Write one markdown file per paper under research/notes/, named <firstauthor><year>-<short-title>.md, with the BibTeX key in the front matter so citation-verifier and lit-review-synthesis can join them:
---
key: smith2023feedback
title: ...
authors: ...
year: 2023
venue: ...
doi: 10.xxxx/yyyy
type: empirical | design | survey | theory | position
read: 2026-09-21
relevance: high | medium | low
---
## One-sentence claim
What the paper says it shows, in your words.
## Research question it answers
Their question, and which of the student's sub-questions it bears on.
## Method
Design, data (source, size), procedure, metrics, baselines. Enough to judge validity.
## Evidence
The key results with numbers, and the table or figure each comes from (Table 3, Fig. 2).
What was not tested.
## Limitations
Theirs (from the paper) and yours (what you noticed).
## Relation to this thesis
Supports / contradicts / extends / provides method for: which claim of the student's, and how.
## Quotable
> "exact sentence" (p. 4, Sec. 3.2)
At most five. Exact text, with location, for use in the review.
## Follow-up
References worth chasing, with the reason.
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.
- 25d ago First seen · 74 lines · 92 tokens per session scan A ff7dc7ffee2e
paper-reader is a skill published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 848 once invoked, about $0.0004 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-09-22.
Other skills, from other repositories
data-warehouse-experimentation
Running experiments out of the data warehouse instead of via dedicated experiment platforms. SQL-based assignment, exposure logging discipline, metric definitions in dbt models, statistical analysis in SQL or Python, variance reduction with CUPED, sequential testing, and the operational tradeoffs vs platforms like…
data-scientist
Processes and analyzes data with resident-kernel engines (DuckDB, Polars) and one-shot tools. Use for CSV/parquet/JSON analysis, group-by/join/aggregation, time series, distributions, cleaning, or plotting a dataset.
fortran
Best practices for modern Fortran (2003/2008+) scientific and numerical computing, covering modules, explicit interfaces, kind parameters, memory safety, and testing. Use when writing or reviewing Fortran source (.f90/.f95/.f03/.f08), defining modules and derived types, choosing numeric kind parameters, working with…
julia
Julia development guidelines covering multiple dispatch, type system, performance optimization, and scientific computing best practices.
hypothesis-testing-engine
Take any claim and design + execute a complete research protocol to test it. Apply scientific method automatically: design study, gather data, run analysis, provide verdict with confidence level.
nlp-natural-language-processing
Expert guidance for natural language processing development using transformers, spaCy, NLTK, and modern NLP techniques.