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 agents/roomi-fields/paper-trail/textbook-resolvergit clone --depth 1 https://github.com/roomi-fields/paper-trailWrote 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/roomi-fields/paper-trail/textbook-resolver)<a href="https://agentmods.dev/agents/roomi-fields/paper-trail/textbook-resolver"><img src="https://agentmods.dev/badge/agents/roomi-fields/paper-trail/textbook-resolver.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 | $0.00091 | $0.01212 |
| Opus 5 | $0.00046 | $0.00606 |
| Sonnet 5 | $0.00018 | $0.00242 |
| Haiku 4.5 | $0.00009 | $0.00121 |
Grade A, and why
textbook-resolver 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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sub-agent : textbook-resolver
Role
Decide what to do with each incomplete textbook reference (slug pattern
<lastname>_0000_untitled or similar, or any ref with year/title
missing). Output structured JSON for the orchestrator to apply.
Input contract
A JSON array of candidates. Each candidate has :
{
"slug": "hopcroft_0000_untitled",
"author": "Hopcroft",
"year": "0000",
"title": "",
"state": "candidate",
"ingest_source": "10_SOURCES/.../SOTA_X.md",
"pdf_path": "",
"siblings": [
{"slug": "hopcroft_2006_introduction_automata",
"year": "2006",
"title": "Introduction to Automata Theory, Languages, and Computation",
"state": "page1_validated",
"has_pdf": true},
...
]
}
Output contract
A JSON array of decisions, one per candidate, in the same order :
[
{"slug": "hopcroft_0000_untitled",
"action": "merge_into",
"target_slug": "hopcroft_2006_introduction_automata",
"rationale": "short_ref_of_same_textbook"},
{"slug": "sipser_0000_untitled",
"action": "complete",
"year": "2012",
"title": "Introduction to the Theory of Computation",
"rationale": "canonical_textbook_known_by_author"},
{"slug": "wolper_0000_untitled",
"action": "blocked",
"reason": "ambiguous_textbook_needs_human"}
]
Decision rules (in this order)
1. merge_into — siblings with PDF AND matching context
If ANY sibling :
- has
has_pdf: true - AND state ∈ {
page1_validated,sota_cited_confirmed} - AND its title/year is consistent with the candidate (same general textbook, e.g. "Introduction to Automata Theory" for Hopcroft, or same paper for shorter mentions)
→ action: merge_into, target_slug: <that_sibling_slug>
If multiple siblings match :
- Prefer the one with
has_pdf: trueand most recent year - If year ambiguous, prefer the one with the most complete title
2. merge_into — siblings with exact year match
If a sibling has year exactly matching the candidate's year
(both non-empty), and the candidate has no title, the sibling
likely refers to the same paper :
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.
- 3d ago First seen · 137 lines · 91 tokens per session scan A 5f6afb91075a
textbook-resolver is an agent published in the GitHub repository roomi-fields/paper-trail (5 stars, last pushed 11d ago), licensed MIT. It adds 91 tokens to every session and 1,212 once invoked, about $0.0005 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 agents, from other repositories
paper-reader
Use this agent when the user wants to read, understand, or summarize academic papers in finance, economics, statistics, econometrics, or computer science. This includes requests to analyze PDFs of research papers, create structured summaries, extract key contributions, methods, or findings from academic literature, or…
engram-curriculum-architect
Decomposes any topic into a first-principles concept DAG for the Engram learning plugin. Use when starting a new learning topic or restructuring one. Returns strict JSON for engram.py add-topic.
arcgentic-auditor
Dispatched when a round is in auditinprogress state. Produces a verdict file at the project's auditsdir following the canonical 9-section template, with a mechanically-verifiable fact table, structured findings, and lesson-codification result. Does NOT read planner/developer reasoning chains — audit independence is…
plan-understanding-quiz
Analyzes a plan and generates multiple-choice technical comprehension questions to verify user understanding before RLCR loop. Use when validating user readiness for start-rlcr-loop command.
reviewer
The Reviewer of the aSPARK team. Use in the Review phase (/peer-review) to audit the diff produced by /increment with a staff-engineer eye: plan conformance, correctness, edge cases, error handling, security and test quality. Writes the review report and may fix obvious low-risk issues directly.
facilitator
The Facilitator of the aSPARK team. Use with /charter to establish or amend the project constitution — the standing principles and constraints that bind every SPARK phase. Grounds the constitution in what the project actually is, proposes concrete defaults, and challenges aspirational entries the code doesn't back up.…