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/zebbern/termstackWrote 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/zebbern/termstack/test_planner)<a href="https://agentmods.dev/agents/zebbern/termstack/test_planner"><img src="https://agentmods.dev/badge/agents/zebbern/termstack/test_planner/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/zebbern/termstack/test_planner"><img src="https://agentmods.dev/badge/agents/zebbern/termstack/test_planner.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.00046 | $0.01616 |
| Opus 5.5 | $0.00018 | $0.00646 |
| Sonnet 5.5 | $0.00009 | $0.00323 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
test_planner 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 1mo 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.
- 1mo ago First seen · 181 lines · 46 tokens per session scan A 0d0c4da5b44a
test_planner is an agent published in the GitHub repository zebbern/termstack (4 stars, last pushed 6mo ago), with no licence file. It adds 46 tokens to every session and 1,616 once invoked, about $0.0002 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
verification
Use this agent to verify that implementation work is correct before reporting completion. Invoke after non-trivial tasks (3+ file edits, backend/API changes, infrastructure changes). Pass the ORIGINAL user task description, list of files changed, and approach taken. The agent runs builds, tests, linters, and checks to…
coder
Code implementation specialist. Handles file editing, code migration, module refactoring, and other pure implementation tasks. Use this agent when the user needs to write code, modify files, or move modules — not for architecture design or solution evaluation.
bulk-test-writer
Writes tests for existing behaviour. Adds and edits test files only — never touches production code. Use for coverage backfill where the bulk of the work is mechanical.
qa-automation-engineer
QA automation engineer for unit, integration, API, UI, regression, fixtures, and automation maintainability.
pre-deploy-validator
9-point pre-deploy gate — compilation, linting, tests, build/bundle, migrations, API spec, debug artifacts, env config, secrets — ends in READY / NOT READY.
plan-validator
Use this agent when you have created a plan (e.g., implementation plan, architecture design, refactoring strategy, feature specification) and need to validate and iteratively improve it before execution. This agent should be invoked:\n\n- After drafting any significant technical plan that will guide implementation…