DeepPaperNote is an agent skill that reads one research paper and turns its content into a structured Obsidian research note. It is for researchers and learners who want to preserve a paper’s question, methods, evidence, results, and figures in an academic knowledge base. The catalogue entries are its agent skills, instructions, and plugin packaging for use with coding agents.
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 917Dhj/DeepPaperNote --skill paper-glossarygit clone --depth 1 https://github.com/917Dhj/DeepPaperNoteWrote 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/917dhj/deeppapernote/paper-glossary)<a href="https://agentmods.dev/skills/917dhj/deeppapernote/paper-glossary"><img src="https://agentmods.dev/badge/skills/917dhj/deeppapernote/paper-glossary/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/917dhj/deeppapernote/paper-glossary"><img src="https://agentmods.dev/badge/skills/917dhj/deeppapernote/paper-glossary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 12 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00046 | $0.01276 |
| Opus 5 | $0.00023 | $0.00638 |
| Sonnet 5 | $0.00009 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
paper-glossary 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 10d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paper Glossary
Build shared glossary notes from *_source_manifest.json. --source-manifest is always required; --raw-sections only overrides its raw_sections_path with an explicit *_raw_sections.jsonl. This skill never runs or modifies a paper-reading workflow; the manifest and raw-sections file are its only paper-content boundary. See references/file-contract.md for JSON and CLI contracts.
Preview And Wait (Default)
- Show saved configuration on first use per person/device. If absent, ask for a term directory inside an Obsidian vault and configure it; reuse valid configuration later. Setup may create
~/.paper-glossary/config.json. - Require an explicit article Markdown path when article links are requested. Validate it and the configured term directory are in the same Obsidian vault; never infer an article path.
- Run deterministic proposal from the effective body.
- Perform exactly one grounded host semantic review, bounded by
shortlist_limit. It may only drop or reorder candidates and must preserve each retained proposal candidate's exacttermstring. - Record the reviewed shortlist with
plan_glossary.py --review-proposal PROPOSAL --reviewed-terms NAMES; this validates the saved proposal against the current paper source and preserves each full candidate, orderedsurface_forms, and provenance. If review produces an empty reviewed shortlist, reportno_candidatesand stop without presenting a selector. - Present every retained term from that reviewed artifact as a numbered Markdown list. This is the terminal, Codex, and Claude Code interaction. Show the resolved term directory, the article Markdown path (or that none was requested), and that selection authorizes glossary writes/enrichment plus first-safe-occurrence article links when an article was supplied.
- State: No glossary notes or article Markdown have been written before selection. End the response and wait. Do not triage, inventory, generate, link, or lint during preview.
What ships with it
23 files 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.
- agents/openai.yaml 475 B
- README.md 4.5 KB
- references/file-contract.md 13 KB
- references/optimization-design.md 9.6 KB
- references/optimization-implementation-plan.md 44 KB
- scripts/configure_glossary.py 2.7 KB runs code
- scripts/glossary_common.py 12 KB runs code
- scripts/glossary_config.py 4.8 KB runs code
- scripts/glossary_contracts.py 518 B runs code
- scripts/glossary_library.py 13 KB runs code
- scripts/inspect_glossary_library.py 2.6 KB runs code
- scripts/link_glossary_terms.py 33 KB runs code
- scripts/lint_glossary.py 4.5 KB runs code
- scripts/plan_glossary.py 27 KB runs code
- scripts/write_glossary_terms.py 30 KB runs code
- tests/conftest.py 5.3 KB runs code
- tests/test_glossary_config.py 12 KB runs code
- tests/test_glossary_library.py 19 KB runs code
- tests/test_link_glossary_terms.py 44 KB runs code
- tests/test_plan_glossary.py 29 KB runs code
- tests/test_skill_boundary.py 15 KB runs code
- tests/test_workflow_integration.py 12 KB runs code
- tests/test_write_and_lint_glossary.py 67 KB runs code
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.
- 10d ago First seen · 44 lines · 46 tokens per session scan A ae87ec9e2353
paper-glossary is a skill published in the GitHub repository 917Dhj/DeepPaperNote (1,051 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 1,276 once invoked, about $0.0002 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-30.
Other skills, from other repositories
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
youtube-fetcher
Retrieve YouTube transcripts and subtitles, summarize or analyze what was said, or save an Obsidian-ready Markdown knowledge-base note with captions, creator metadata, chapters, language, and source provenance. Use for a YouTube URL or video ID when the request needs spoken content or an archival note. A bare YouTube…
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
link-health
Use at the start of Link work when readiness is unclear, after installs or upgrades, and before repairs; verify health, inspect interrupted writes, back up, and repair generated indexes without MCP.
link-ingest
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.