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/Digital-Threads/token-pilotWrote 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/agents/digital-threads/token-pilot/tp-context-engineer)<a href="https://agentmods.dev/agents/digital-threads/token-pilot/tp-context-engineer"><img src="https://agentmods.dev/badge/agents/digital-threads/token-pilot/tp-context-engineer/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/agents/digital-threads/token-pilot/tp-context-engineer"><img src="https://agentmods.dev/badge/agents/digital-threads/token-pilot/tp-context-engineer.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.00079 | $0.01216 |
| Opus 5.5 | $0.00032 | $0.00486 |
| Sonnet 5.5 | $0.00016 | $0.00243 |
| Haiku 4.5 | $0.00008 | $0.00122 |
Grade A, and why
tp-context-engineer 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.
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.
- 8d ago Changed 8d76e53c5296
- 23d ago Changed 5498fd7e7a91
- 24d ago Changed 8cf5637d3117
- 29d ago Changed 6ec636817c50
- 1mo ago Changed 0f6fb0b03325
- 1mo ago Changed db0913997d2e
- 1mo ago Changed · +6 lines 4c7d4a4bcce0
- 1mo ago First seen · 73 lines · 79 tokens per session scan A ad04bba8a6cd
tp-context-engineer is an agent published in the GitHub repository Digital-Threads/token-pilot (5 stars, last pushed 8d ago), with no licence file. It adds 79 tokens to every session and 1,216 once invoked, about $0.0003 per session on Opus 5.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.
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.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
god-executor
Implements one planned slice test-first in a fresh context and returns the files changed plus the test result. Does not commit.
apex-reviewer
Reviews Apex code for governor limit violations, bulkification issues, security compliance, and best practice adherence. Read-only analysis.