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.
npx agentmods add agents/digital-threads/token-pilot/tp-doc-writergit clone --depth 1 https://github.com/Digital-Threads/token-pilotWhat 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 | $0.00077 | $0.01199 |
| Opus 5 | $0.00039 | $0.00600 |
| Sonnet 5 | $0.00015 | $0.00240 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
tp-doc-writer 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 75 lines · 77 tokens per session scan A 64133df662a9
tp-doc-writer is an agent published in the GitHub repository Digital-Threads/token-pilot (5 stars, last pushed 6d ago), with no licence file. It adds 77 tokens to every session and 1,199 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 agents, from other repositories
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
ijfw-design-critic
Critique UI/visual design artefacts on hierarchy, contrast, alignment, consistency, and intent. Trigger per design review pass.
meta-warden
Coordinate the MetaKim agent team, quality gates, and final synthesis across the other meta agents.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
code-explorer
Deep code understanding expert using AST knowledge graph. Use when exploring unfamiliar code, tracing complex relationships, or understanding module architecture.
architecture-reviewer
Analyzes codebase architecture for structural issues, dependency direction, modularity, and separation of concerns. Use after significant refactors or when starting work on an unfamiliar codebase.