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-search)<a href="https://agentmods.dev/commands/roomi-fields/paper-trail/paper-trail-search"><img src="https://agentmods.dev/badge/commands/roomi-fields/paper-trail/paper-trail-search/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-search"><img src="https://agentmods.dev/badge/commands/roomi-fields/paper-trail/paper-trail-search.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.00087 | $0.00509 |
| Opus 5 | $0.00044 | $0.00254 |
| Sonnet 5 | $0.00017 | $0.00102 |
| Haiku 4.5 | $0.00009 | $0.00051 |
Grade A, and why
paper-trail-search 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:search <query> — Search the validated registry
Étape 5 du pipeline cible : interrogation du registre validé.
Usage
/paper-trail:search beat tracking # par défaut, refs sota_cited_confirmed
/paper-trail:search "tempo estimation" --include-pending # inclut page1_validated
/paper-trail:search heydari --limit 10
Ce que fait Claude
-
Lance la recherche :
python3 -m pipeline search "<query>" [--include-pending] [--limit N] -
Filtre :
- Par défaut : refs en
sota_cited_confirmed(claims audités contre PDF) - Avec
--include-pending: ajoutepage1_validated(PDF OK techniquement, claims non audités)
- Par défaut : refs en
-
Sortie : liste compacte
[sota_cited_confirmed] Heydari, M. (2021) — BeatNet: CRNN and Particle... heydari_2021_beatnet [page1_validated] Chang, Y.-C. & Su, L. (2024) — BEAST: Online Joint Beat... chang_2024_beast -
Propose les usages :
- Si tu écris un SOTA / paper : copier le slug et l'utiliser comme
[[wikilink]] - Si tu veux la fiche complète d'une ref :
/paper-trail:decide <slug>
- Si tu écris un SOTA / paper : copier le slug et l'utiliser comme
Quand utiliser cette commande
- Avant d'écrire : pour ne citer que du validé
- Pour vérifier la couverture : « est-ce que j'ai des refs sur tel sujet ? »
- Pour booster sota-writer : après identification des candidates, cette commande montre lesquelles sont déjà dans ton registre validé
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 · 47 lines · 87 tokens per session scan A c7c989859fe3
paper-trail-search is a command published in the GitHub repository roomi-fields/paper-trail (5 stars, last pushed 6d ago), licensed MIT. It adds 87 tokens to every session and 509 once invoked, about $0.0004 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).