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/djrhails/dotfiles/import-papersnpx skills add DJRHails/dotfiles --skill import-papersgit clone --depth 1 https://github.com/DJRHails/dotfilesWhat 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.00076 | $0.00765 |
| Opus 5 | $0.00038 | $0.00382 |
| Sonnet 5 | $0.00015 | $0.00153 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
import-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 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Import Papers Skill
Process all PDFs in research/dump/, create bibtex entries, and move them to research/papers/.
Instructions
For each PDF in research/dump/:
-
Extract metadata using
pdftotext(first 30 lines only to avoid context overload):pdftotext "filename.pdf" - 2>&1 | head -30 -
Identify:
- Title (full, not truncated)
- Authors (first few primary authors)
- Year (infer from content or use the current year for recent papers)
- Venue (if clearly stated: conference/journal)
-
Generate citation key using format:
firstauthorYEARkeyword- Use lowercase only
- First author's last name
- Year
- One descriptive keyword from title
- Examples:
ren2015faster,choi2024neuromamba,park2024processing
-
Create bibtex entry matching existing format in
research/papers.bib:@article{citationkey, author = {Author One and Author Two and Author Three}, ejournal = {arXiv}, title = {Full Paper Title}, url = {https://arxiv.org/abs/XXXX.XXXXX}, year = {YYYY} }Use
@inproceedingsif it's a conference paper (like NIPS, ICML, etc.) with:@inproceedings{citationkey, author = {Authors}, booktitle = {Conference Name}, title = {Title}, year = {YYYY} } -
Append to papers.bib:
cat >> research/papers.bib << 'EOF' @article{citationkey, ... } EOF -
Move and rename PDF to
research/papers/:mv "research/dump/original.pdf" "research/papers/citationkey.pdf" -
Handle duplicates: If two PDFs are identical (same title), keep only one.
-
Verify after processing all files:
- List moved files:
ls -1 research/papers/ | tail -10 - Check dump is empty:
ls -1 research/dump/*.pdf 2>/dev/null || echo "empty"
- List moved files:
-
Run bibify.py to update the changelog and sync with Google Drive:
./bin/bibify.pyIf the output contains
Missing notes for, run bibify a second time — newly uploaded papers need a second pass to generate their note stubs.
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 · 95 lines · 76 tokens per session scan A af783a3d8a6f
import-papers is a skill published in the GitHub repository DJRHails/dotfiles (2 stars, last pushed 7d ago), licensed MIT. It adds 76 tokens to every session and 765 once invoked, about $0.0004 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
autopilot-batch
Fan out a batch of autopilot-queued issues to parallel background worktree subagents — each runs /autopilot at the build model from its 'model:' label — with a gating review at Opus 5 or above and never below the build (Opus reviews Sonnet and Opus builds, Fable reviews Fable builds).
todoist-cli
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
qa-handoff
Generate a hands-on QA testing guide as a self-contained HTML page — for Rails apps or static (Hugo) sites. --publish uploads the HTML to the project's configured QA host.
walkthrough
Generate a hands-on browser walkthrough of a PR's user-facing changes to exercise before review; --publish posts the final version to the PR for QA.
dustoff
Assess a project that's been dormant for months and produce a prioritized re-entry plan — lifecycle stage, what's stale or broken, and how far the project's tooling has drifted from current conventions — delegating every fix to the skill that owns it, and optionally capturing the plan as a tracking issue that survives…