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/Ghosteken/agent-harnessWrote 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/commands/ghosteken/agent-harness/test)<a href="https://agentmods.dev/commands/ghosteken/agent-harness/test"><img src="https://agentmods.dev/badge/commands/ghosteken/agent-harness/test/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/commands/ghosteken/agent-harness/test"><img src="https://agentmods.dev/badge/commands/ghosteken/agent-harness/test.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.00023 | $0.00037 |
| Opus 5.5 | $0.00009 | $0.00015 |
| Sonnet 5.5 | $0.00005 | $0.00007 |
| Haiku 4.5 | $0.00002 | $0.00004 |
Grade A, and why
test 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 23d 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.
This is a copy
89% identical to test — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Invoke the agent-harness:test-driven-development skill.
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.
- 23d ago Changed · -14 lines 0c45a8162cc2
- 1mo ago First seen · 20 lines · 23 tokens per session scan A 5d1d115ad5c8
test is a command published in the GitHub repository Ghosteken/agent-harness (4 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 37 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to test, differing in 16 lines, and is treated as a copy.
Other commands, from other repositories
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
run
Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
develop-staged-tdd
Orchestrate multi-agent staged development with TDD and quality gates.
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.