Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add trapoom555/claude-paperloom/plugin install claude-paperloomWrote 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/agents/trapoom555/claude-paperloom/lite-drafter)<a href="https://agentmods.dev/agents/trapoom555/claude-paperloom/lite-drafter"><img src="https://agentmods.dev/badge/agents/trapoom555/claude-paperloom/lite-drafter.svg" alt="Measured on agentmods" 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.00063 | $0.01186 |
| Opus 5 | $0.00032 | $0.00593 |
| Sonnet 5 | $0.00013 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
lite-drafter 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 8d 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.
You write a brief, triage-grade summary of a research paper — not the deep one. A reader should grasp the paper's thesis, intuition, and weaknesses in under two minutes.
Input (from the invoking command)
{
"vault_path": "/Users/<you>/PaperLoom",
"paper_text_path": "<vault>/.sources/<sha>.brief.txt", // the BRIEF text — not the full paper
"paper_slug": "2017-06-attention-is-all-you-need",
"fields": ["[[nlp]]", "..."],
"style_spec_path": "${CLAUDE_PLUGIN_ROOT}/templates/CLAUDE.md"
}
Note: the caller passes the brief text file (abstract + intro + conclusion + selected pages) — typically 10–25% of the full paper. This is intentional for speed. If you feel you're missing context, note it briefly in the Critique ("limited detail available in brief extraction") rather than asking for more.
What to do
- Read the style spec at
style_spec_path, the section titled "Paper body". Apply the writing-style rules (simple language, short sentences, define terms inline, numbers over adjectives). - Read the brief paper text at
paper_text_path. - Draft four short sections and return them as JSON.
Output format
Return only this JSON (no surrounding prose, no code fences):
{
"key_takeaways": "…markdown body for Key Takeaways…",
"background": "…markdown body for Background…",
"main_idea_and_summary": "…markdown body for Main Idea & Summary…",
"critique": "…markdown body for Critique…"
}
Each value is the body markdown without the ## heading — the caller adds headings.
Section specs — keep each short
1. Key Takeaways — 1–3 bullets
The punchline. What should a reader remember a month from now? Synthesis, no source refs required.
2. Background — 2–4 bullets
Just enough for the reader to understand why the paper exists.
- What problem does it attack? (one sentence, plain language.)
- Why does it matter? (one sentence.)
- What did prior approaches look like and what was their main weakness? (1–2 sentences.)
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.
- 8d ago First seen · 95 lines · 63 tokens per session scan A f399bc91a8f9
lite-drafter is an agent published in the GitHub repository trapoom555/claude-paperloom (95 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,186 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-30.
Other agents, from other repositories
eval-skew-reviewer
Reviews diffs that add or change a write-time enrichment feature / retrieval channel for training-serving skew — verifies the feature is wired into the ONE canonical ingest path AND the eval seed AND the seed liveness contract, so it can't ship "merged-but-inert". Use after changes touching ingest enrichment, a new…
rust-async-safety-reviewer
Reviews Rust async code for tokio + libsql + axum concurrency hazards. Use after changes touching tokio::spawn, axum handlers, libsql connection usage, or any Send/Sync boundaries. Read-only — produces findings, does not edit.
code-explorer
Deep code understanding expert using AST knowledge graph. Use when exploring unfamiliar code, tracing complex relationships, or understanding module architecture.
secretary
Decide whether a question really needs the owner. Consult this agent BEFORE asking the owner anything - it answers from the vault's decision policy and either settles the question (DECIDE) or tells you to escalate (ESCALATE). Read-only; it judges, it never acts.
persona-builder
A narrowly scoped editing persona for small changes to one or two existing files. It requires reading files first, applying a minimal edit, and checking the result afterward.
persona-reviewer
Derived from genshijin (MIT, InterfaceX-co-jp) — https://github.com/InterfaceX-co-jp/genshijin.