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-test-writer)<a href="https://agentmods.dev/agents/digital-threads/token-pilot/tp-test-writer"><img src="https://agentmods.dev/badge/agents/digital-threads/token-pilot/tp-test-writer/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-test-writer"><img src="https://agentmods.dev/badge/agents/digital-threads/token-pilot/tp-test-writer.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.00069 | $0.01179 |
| Opus 5.5 | $0.00028 | $0.00472 |
| Sonnet 5.5 | $0.00014 | $0.00236 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
tp-test-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 11d 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.
- 11d ago Changed 503272daab84
- 12d ago Changed 5b2dbbe19730
- 17d ago Changed d51b5b57ed95
- 22d ago Changed d0cf7d6c7ed4
- 1mo ago Changed 79ed4b95ef5e
- 1mo ago Changed · +6 lines 23d955df3243
- 1mo ago First seen · 69 lines · 69 tokens per session scan A dde4e0f95522
tp-test-writer is an agent published in the GitHub repository Digital-Threads/token-pilot (5 stars, last pushed 11d ago), with no licence file. It adds 69 tokens to every session and 1,179 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
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.
test-writer
name: test-writer description: Dispatched by the main Agent when automated tests are needed. Generates TypeScript test files for sync scripts and core utilities. skills: none model: sonnet color: yellow.
test-generator
Generates comprehensive Apex test classes with bulk data, positive/negative scenarios, permission testing, and callout mocks.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.