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-identify)<a href="https://agentmods.dev/commands/roomi-fields/paper-trail/paper-trail-identify"><img src="https://agentmods.dev/badge/commands/roomi-fields/paper-trail/paper-trail-identify.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.1 | $0.00076 | $0.00491 |
| Opus 5 | $0.00038 | $0.00246 |
| Sonnet 5 | $0.00015 | $0.00098 |
| Haiku 4.5 | $0.00008 | $0.00049 |
Grade A, and why
paper-trail-identify 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 8d 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:identify <SOTA-path> — Rapport d'identification (read-only)
Étape 1 du pipeline cible refondu (avant purge / acquire / linkify). Produit un rapport sans toucher au SOTA ni au registre.
Usage
/paper-trail:identify <SOTA-path>
Ce que fait Claude
-
Extrait les sections bibliographiques :
python3 -m pipeline ingest <SOTA-path> --extract-onlyRetourne un JSON
[{header, is_excluded, raw_text, ...}]. -
Pour chaque section non exclue, invoque le sub-agent
paper-trail:citation-parser(en parallèle), qui écrit chaque JSON dans/tmp/section_<i>_citations.json. -
Consolide les JSON en un seul fichier
/tmp/citations_<sota_stem>.json. -
Lance le rapport :
python3 -m pipeline identify <SOTA-path> \ --citations-json /tmp/citations_<sota_stem>.jsonAffiche pour chaque mention :
- action recommandée (reuse / reuse_retracted / create / skipped_low)
- slug matché ou would-be-created
- état actuel + présence PDF
- PDF orphelin trouvé éventuel
-
Présente le récap + propose les passes suivantes :
/paper-trail:purge <SOTA>si wikilinks vers retracted détectés/paper-trail:acquire <SOTA>pour les fiches sans PDF/paper-trail:linkify <SOTA>pour insérer les wikilinks finaux
Style
- Concis. Pas de jargon technique.
- En cas d'erreur sur une section, propose un retry ciblé.
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.
- 8d ago First seen · 51 lines · 76 tokens per session scan A eeb668268bfb
paper-trail-identify is a command published in the GitHub repository roomi-fields/paper-trail (5 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 491 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.
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).