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-linkify)<a href="https://agentmods.dev/commands/roomi-fields/paper-trail/paper-trail-linkify"><img src="https://agentmods.dev/badge/commands/roomi-fields/paper-trail/paper-trail-linkify.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.00070 | $0.00620 |
| Opus 5 | $0.00035 | $0.00310 |
| Sonnet 5 | $0.00014 | $0.00124 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
paper-trail-linkify 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:linkify <SOTA-path> — Wikilinks finaux + section Statut
Étape 4 du pipeline cible refondu. Insère les wikilinks finaux dans le
SOTA et ajoute/régénère la section ## Statut des sources en bas.
Usage
/paper-trail:linkify <SOTA-path> # dry-run (compte uniquement)
/paper-trail:linkify <SOTA-path> --apply # applique + backup git
Ce que fait Claude
-
Vérifie git initialisé dans le vault.
-
Extrait les sections + sub-agent citation-parser (parallèle), comme pour identify, produisant
/tmp/citations_<sota_stem>.json. -
Lance le linkify :
python3 -m pipeline linkify <SOTA-path> \ --citations-json /tmp/citations_<sota_stem>.json [--apply]Comportement par mention :
- Si la ref est validée (state=
page1_validatedousota_cited_confirmed) AVEC unpdf_path→ wikilink direct vers le PDF, par exemple :[[Sources/Knuth_1965_Translation.pdf|knuth_1965]] — Knuth 1965 (LR) - Sinon → wikilink vers une ancre
#source-<lastname>-<year>dans une section## Statut des sourcesrégénérée en bas du SOTA. Exemple :[[#source-younger-1967|younger_1967]] — Younger 1967
- Si la ref est validée (state=
-
Régénère la section
## Statut des sourcesidempotemment, encadrée par :<!-- paper-trail:statut:begin --> ## Statut des sources ... <!-- paper-trail:statut:end -->5 sous-sections : validées / en cours / bloquées / rétractées / non créées. Chaque entrée a une ancre
<a id="source-..."></a>ciblable. -
Présente le récap : N wikilinks PDF + N wikilinks ancre + N entrées dans la section Statut.
Style
- Concis.
- En cas d'erreur (backup git échoué, SOTA introuvable), explique et propose un retry.
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 · 58 lines · 70 tokens per session scan A 5a883014d5cb
paper-trail-linkify is a command published in the GitHub repository roomi-fields/paper-trail (5 stars, last pushed 4d ago), licensed MIT. It adds 70 tokens to every session and 620 once invoked, about $0.0003 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).