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-ship-coordinator)<a href="https://agentmods.dev/agents/digital-threads/token-pilot/tp-ship-coordinator"><img src="https://agentmods.dev/badge/agents/digital-threads/token-pilot/tp-ship-coordinator/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-ship-coordinator"><img src="https://agentmods.dev/badge/agents/digital-threads/token-pilot/tp-ship-coordinator.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.00067 | $0.01167 |
| Opus 5.5 | $0.00027 | $0.00467 |
| Sonnet 5.5 | $0.00013 | $0.00233 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
tp-ship-coordinator 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 3d 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.
- 3d ago Changed 8ea1cc0b1327
- 18d ago Changed f11753ea5e33
- 19d ago Changed a391b9f9ed48
- 24d ago Changed b2123ddd3c6b
- 29d ago Changed d0afec74035b
- 1mo ago Changed 946c1200d5d3
- 1mo ago Changed · +5 lines b8db049a39ef
- 1mo ago First seen · 69 lines · 67 tokens per session scan A eb58b8906541
tp-ship-coordinator is an agent published in the GitHub repository Digital-Threads/token-pilot (5 stars, last pushed 4d ago), with no licence file. It adds 67 tokens to every session and 1,167 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-dep-audit
Flag publishConfig drift, lock-in version skew, dep version mismatches. Trigger before any release wave.
ijfw-doc-writer
Writes/updates CHANGELOG.md + README.md from commit log + handoff. Trigger before ship-gate.
ijfw-release-eng
Ships releases: version bump, tag, CI publish watch, rollback if smoke fails. Trigger when phase passes ship-gate.
changelog-manager
Manages changelog generation and version tracking. Use after commits, before releases, or when preparing release notes. Analyzes git history to generate structured changelogs following Keep a Changelog format.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
doc-changelog
Changelog maintenance following Keep a Changelog. Use to document changes between versions.