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 stellarshenson/claude-code-plugins --skill papersgit clone --depth 1 https://github.com/stellarshenson/claude-code-pluginsWrote 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/stellarshenson/claude-code-plugins/papers)<a href="https://agentmods.dev/skills/stellarshenson/claude-code-plugins/papers"><img src="https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/papers/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/stellarshenson/claude-code-plugins/papers"><img src="https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/papers.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.00163 | $0.02045 |
| Opus 5.5 | $0.00065 | $0.00818 |
| Sonnet 5.5 | $0.00033 | $0.00409 |
| Haiku 4.5 | $0.00016 | $0.00204 |
Grade A, and why
papers 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 today.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Papers - reference and digest workflow
Every source cited in a project document (design docs, experiment registrations, hypothesis groundings, research notes) gets TWO artifacts in the project's references/papers/ directory. A cited source that is not downloaded and digested is a defect - no citation without both.
[<type>] <short name>, <year>.pdf- the downloaded PDF[<type> digest] <short name>.md- the structured digest
<type> states what the source actually is, and the digest carries the same type as its PDF:
| Source | PDF prefix | Digest prefix |
|---|---|---|
| paper, preprint, technical report | [paper] |
[paper digest] |
| book, ebook, book chapter | [book] |
[book digest] |
| article, blog post, vendor post, newsletter | [article] |
[article digest] |
| course, lecture notes, syllabus | [course] |
[course digest] |
| slide deck | [presentation] |
[presentation digest] |
Never write a [paper digest] for a book or an article: the prefix is how a reader tells from the filename what the digest covers. Classify before naming - a work with an ISBN, publisher imprint or book length is a book; prose published on a site under a byline is an article; an abstract with numbered sections is a paper.
<short name> is a compact human-readable title (not the arXiv id), identical between the two files - e.g. [book] the rust programming language, 2019.pdf and [book digest] the rust programming language.md.
A digest already written under the wrong prefix is renamed to match its source; the short name and the file body do not change. When several digests are mislabelled, rename them in one pass and report the count.
Provenance link - hard requirement
The digest's **Source** section carries the online provenance link: the actual downloadable or access URL for the original. Never a local filename, never a path.
- A digest outlives its PDF - it is read, quoted, and grounded against on other machines, in other repos, after the local file has moved or gone. A local path resolves for exactly one reader; a URL resolves for every reader
- Durability order: DOI URL (
https://doi.org/<doi>) > arXiv abs page > publisher OA / PMC / OpenReview / ACL Anthology landing page > direct PDF URL. Prefer the landing page over a CDN link that rots - Verify the URL resolves before writing it - a fabricated or dead DOI is worse than no link
- Paywalled - link the DOI anyway and add one line:
- Access: paywalled; digest written from abstract and published summaries - Books - link the publisher page, DOI, or a stable catalogue record (worldcat, openlibrary); an ISBN alone is not a link
- The PDF is still downloaded under the naming rule above; it simply never appears inside the digest
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.
- today Changed · +14 lines · +34 tokens per session e5c50d6d3381
- 1mo ago First seen · 126 lines · 129 tokens per session scan A 257a361e50e7
papers is a skill published in the GitHub repository stellarshenson/claude-code-plugins (4 stars, last pushed today), licensed MIT. It adds 163 tokens to every session and 2,045 once invoked, about $0.0007 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.
Other skills, from other repositories
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
meta-web-to-pdf-briefing
Render a topic into a distributable PDF briefing in three steps: web search → bullet summary → styled PDF. Trigger when the user asks for a PDF briefing on a single topic.
chat-complex-documents
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready…
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.
paper-reader
A reading assistant for computer-vision and deep-learning research papers. It can work with PDF files, arXiv papers, and papers stored in Zotero, a reference-management app.