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/z5840415/crossharnessWrote 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/z5840415/crossharness/review)<a href="https://agentmods.dev/commands/z5840415/crossharness/review"><img src="https://agentmods.dev/badge/commands/z5840415/crossharness/review/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/z5840415/crossharness/review"><img src="https://agentmods.dev/badge/commands/z5840415/crossharness/review.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.00007 | $0.00029 |
| Opus 5.5 | $0.00003 | $0.00012 |
| Sonnet 5.5 | $0.00001 | $0.00006 |
| Haiku 4.5 | $0.00001 | $0.00003 |
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 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.
What it actually says
Review the following diff. Flag bugs first, style second: $ARGUMENTS
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 · 5 lines · 7 tokens per session scan A 37e164fea0d1
review is a command published in the GitHub repository z5840415/crossharness (1 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 29 once invoked, about $0.0000 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 commands, from other repositories
review
You are an expert code reviewer. Your job is to review code changes and provide actionable feedback.
delegate-review
Run OCR in delegation mode — OCR handles file selection and rules, the host agent performs the actual review.
review.v1
Review code changes: /review [commit|branch|PR].
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
review
Review code across five axes with categorized findings.
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.