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-status)<a href="https://agentmods.dev/commands/roomi-fields/paper-trail/paper-trail-status"><img src="https://agentmods.dev/badge/commands/roomi-fields/paper-trail/paper-trail-status/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-status"><img src="https://agentmods.dev/badge/commands/roomi-fields/paper-trail/paper-trail-status.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.00021 | $0.00363 |
| Opus 5 | $0.00010 | $0.00181 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
paper-trail-status 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:status — Registry status
Read-only snapshot of the registry. Counts refs per FSM state and categorizes them (active / waiting / blocked_human / terminal).
Usage
/paper-trail:status
No arguments.
What it does
Delegates to the worker B :
python -m pipeline status
Output
# Registry status — 909 refs
État Count Catégorie
----------------------------------------------------------------------
candidate 210 active
uid_resolved 1 active
awaiting_rtfm_ocr 13 waiting
page1_validated 29 active
sota_cited_confirmed 536 terminal
retracted 120 terminal
Récap : active=240 waiting=13 blocked_human=0 terminal=656
Categories
- active : refs the worker should process (
candidate,uid_resolved,pdf_acquired,needs_reacquisition,page1_validated) - waiting :
awaiting_rtfm_ocr(worker idle, RTFM is OCRing) - blocked_human :
blocked_human:*(curator decision needed) - terminal :
sota_cited_confirmed,retracted(worker never touches these)
When to use
- Beginning of session : overview of registry state
- After a batch run : verify state distribution shifted as expected
- Before deciding what to invoke (cascade, doctor, audit-sota)
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 · 58 lines · 21 tokens per session scan A 901e8674c4e0
paper-trail-status is a command published in the GitHub repository roomi-fields/paper-trail (5 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 363 once invoked, about $0.0001 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.
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.
commit
Classify changes and create atomic commits with conventional messages. Flags out-of-context modifications and red-flag patterns before committing.
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).