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.
git 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/cascade-runner)<a href="https://agentmods.dev/agents/roomi-fields/paper-trail/cascade-runner"><img src="https://agentmods.dev/badge/agents/roomi-fields/paper-trail/cascade-runner/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/agents/roomi-fields/paper-trail/cascade-runner"><img src="https://agentmods.dev/badge/agents/roomi-fields/paper-trail/cascade-runner.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.00060 | $0.00641 |
| Opus 5.5 | $0.00024 | $0.00256 |
| Sonnet 5.5 | $0.00012 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
cascade-runner 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 1mo 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sub-agent : cascade-runner
Role
Orchestrate the worker B cascade across a batch of references. Useful when N > 5 candidates are being processed in one session and we want to :
- Track progress without polluting the main agent's context
- Aggregate results (success / blocked / retracted counts) cleanly
- Surface only the actionable outcomes (e.g., refs that need human decision)
For single-ref acquisitions, the pdf-cascade skill suffices.
Input contract
slugs: [list of ref slugs to process]
# OR
state_filter: candidate | uid_resolved | needs_reacquisition
limit: N (optional cap)
shadow_enabled: true | false (optional, defaults to env var)
What this agent does
- If
slugsprovided : iterate, invokepython -m pipeline run --ref <slug>for each (sequential to avoid lock contention viaWorkerLock) - If
state_filterprovided : invokepython -m pipeline run --state <X> --limit <N>once - Parse the worker B output (recap session line) for each invocation
- Aggregate :
success_slugs[]: refs reachingpage1_validatedpending_slugs[]: refs reachingawaiting_rtfm_ocr(OCR queued)blocked_slugs[]: refs reachingblocked_human:*(with reason)retracted_slugs[]: refs reachingretracted
- Return structured summary to caller
Output contract
{
"batch_size": N,
"success_slugs": ["arnold_1982", "smith_2020", ...],
"pending_slugs": ["lerdahl_2001", ...],
"blocked_slugs": [
{"slug": "chemillier_2003", "reason": "title_mismatch"},
...
],
"retracted_slugs": [],
"elapsed_seconds": 145.2,
"errors": []
}
Constraints
- Sequential invocation (worker B has a
WorkerLockpreventing concurrent cmd_run sessions) - No retries on transient failures (the worker B's circuit-breakers and cascade exhaustion handle that)
- Never modifies registry directly — only via worker B CLI
When NOT to invoke
- Single ref by slug : use pdf-cascade skill directly (no need for sub-agent overhead)
- Semantic decisions (curator role) : use sota-auditor skill
- Doctor / invariant checks : use registry-doctor skill
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.
- 1mo ago First seen · 78 lines · 60 tokens per session scan A f51b3eed3497
cascade-runner is an agent published in the GitHub repository roomi-fields/paper-trail (6 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 641 once invoked, about $0.0002 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 agents, from other repositories
peer-reviewer
Use this agent when you need to review someone else's paper — as a peer reviewer, discussant, or for reading group preparation. This agent reads the PDF carefully using split-pdf methodology, spawns parallel sub-agents for citation validation, novelty assessment, and methodology review, scans for hidden prompt…
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
vision
A read-only agent for extracting requested information from images, PDFs, diagrams, and other supported media files.
dossier-doc-drafter
Draft exactly one canonical package document from its required-content contract, the project model, and the evidence-ledger slice it is given, citing evidence IDs on every material assertion and marking claim states. Use when Phase 4 drafts internal documents or Phase 5 derives public documents, dispatched once per…
document-writer
Technical writing specialist. Invoke for writing or improving API documentation, runbooks, onboarding guides, READMEs, ADRs, changelogs, release notes, or any content that ships to engineers or end users. Also use for structuring documentation sites and diagrams-as-code.
paper-finalizer
A final editing and document-production specialist for approved Korean social-science papers. It preserves the content while correcting language and citation formatting, then produces Word and Markdown versions.