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/commands/roomi-fields/paper-trail/paper-trail-reactivate-ocr)<a href="https://agentmods.dev/commands/roomi-fields/paper-trail/paper-trail-reactivate-ocr"><img src="https://agentmods.dev/badge/commands/roomi-fields/paper-trail/paper-trail-reactivate-ocr/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/commands/roomi-fields/paper-trail/paper-trail-reactivate-ocr"><img src="https://agentmods.dev/badge/commands/roomi-fields/paper-trail/paper-trail-reactivate-ocr.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.00045 | $0.00557 |
| Opus 5 | $0.00023 | $0.00279 |
| Sonnet 5 | $0.00009 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
paper-trail-reactivate-ocr 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 9d 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.
What it actually says
/paper-trail:reactivate-ocr — Resume OCR-waiting refs
Polls RTFM (local indexing engine) for refs in state awaiting_rtfm_ocr
and dispatches them based on the OCR verdict.
Usage
/paper-trail:reactivate-ocr
/paper-trail:reactivate-ocr --quiet
No other arguments.
What it does
Delegates to the worker B :
python -m pipeline reactivate-ocr [--quiet]
For each ref in state awaiting_rtfm_ocr :
- Calls
rtfm check --path <pdf>via the RTFM CLI - Dispatches based on the verdict :
ok(OCR done, chunks indexed) → re-run page 1 validation, transition topage1_validatedif validation passesstill_pending(OCR not yet finished) → no changemissing_in_index(RTFM hasn't seen this file yet) → log and waitanomaly(OCR done but 0 chunks) → log anomaly, no transitionocr_failed(OCR attempted and failed) → transition toneeds_reacquisitionfor cascade retry
Output
# reactivate-ocr — N refs en awaiting_rtfm_ocr scannées
converted N (→ page1_validated)
still_pending N
missing_in_index N
anomaly N
ocr_failed N (→ needs_reacquisition)
needs_reacq_post_ocr N
error N
Cadence
There's no automatic polling. The skill is invoked manually when the user wants to check OCR progress. RTFM OCR jobs typically take minutes to hours depending on PDF size and queue depth.
Recommendation : run /paper-trail:reactivate-ocr at the start of each
session to clear refs whose OCR completed in the interim.
Cross-reference
- I15 invariant (doctor) reports refs that have been
awaiting_rtfm_ocr30 days with no recent RTFM check
- See
pipeline/USAGE.mdfor the worker B CLI - See
tools/rtfm-bridge(if installed) for direct RTFM integration
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.
- 9d ago First seen · 67 lines · 45 tokens per session scan A f026b0ef3b90
paper-trail-reactivate-ocr is a command published in the GitHub repository roomi-fields/paper-trail (5 stars, last pushed 6d ago), licensed MIT. It adds 45 tokens to every session and 557 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-31.
Other commands, from other repositories
gh-release
Create a new release for the marketplace or a specific plugin.
commit
Classify changes and create atomic commits with conventional messages. Flags out-of-context modifications and red-flag patterns before committing.
resolve
Resolve merge conflicts on the current branch or for a pull request. Detects conflict types, analyzes both sides, applies per-file resolution strategies, and verifies the result compiles and passes tests.
ledger-research
Launch parallel evidence collection across all active research pillars.
ledger-spec
Generate constrained PRD and architecture documents where every section cites decisions.
quick-research
Quick research with source verification (lighter than /deep-research).