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.
npx agentmods add commands/ghosteken/agent-harness/reviewgit clone --depth 1 https://github.com/Ghosteken/agent-harnessWhat 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 | $0.00016 | $0.00178 |
| Opus 5 | $0.00008 | $0.00089 |
| Sonnet 5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
review 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 yesterday.
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
91% identical to review — 2 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:code-review-and-quality skill.
Review the current changes (staged or recent commits) across all five axes:
- Correctness — Does it match the spec? Edge cases handled? Tests adequate?
- Readability — Clear names? Straightforward logic? Well-organized?
- Architecture — Follows existing patterns? Clean boundaries? Right abstraction level?
- Security — Input validated? Secrets safe? Auth checked? (Use security-and-hardening skill)
- Performance — No N+1 queries? No unbounded ops? (Use performance-optimization skill)
Categorize findings as Critical, Important, or Suggestion. Output a structured review with specific file:line references and fix recommendations.
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.
- yesterday First seen · 17 lines · 16 tokens per session scan A 70de75923770
review is a command published in the GitHub repository Ghosteken/agent-harness (2 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 178 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to review, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
journey-audit
Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.
cost-tracker
Track session costs, understand token spend, and get optimization tips.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.