Borrowing it
Nothing to install: this file belongs to Contrast-Security-OSS/mcp-contrast. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Contrast-Security-OSS/mcp-contrast/main/.claude/commands/harness-review.mdgit clone --depth 1 https://github.com/Contrast-Security-OSS/mcp-contrastWrote 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/contrast-security-oss/mcp-contrast/harness-review)<a href="https://agentmods.dev/commands/contrast-security-oss/mcp-contrast/harness-review"><img src="https://agentmods.dev/badge/commands/contrast-security-oss/mcp-contrast/harness-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/contrast-security-oss/mcp-contrast/harness-review"><img src="https://agentmods.dev/badge/commands/contrast-security-oss/mcp-contrast/harness-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.00018 | $0.00455 |
| Opus 5 | $0.00009 | $0.00228 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
harness-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 10d 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
/harness-review
Run Ryan Lopopolo's harness-engineering repository-review playbook against this repository. It is a broad, read-only diagnostic. It asks whether a capable coding agent can recover the real job, make a coherent change, prove the outcome, and operate safely here without using a person as a relay.
An optional focus area may be passed as $ARGUMENTS.
Steps
-
Locate the corpus by running the snippet in
docs/agents/harness.md. That resolvesCORPUS_DIRto a read-only checkout pinned to a known commit. -
Read
$CORPUS_DIR/AGENTS.md. Follow its Application routing and Working loop. It routes a broad assessment to the repository-review playbook. -
Read
$CORPUS_DIR/playbooks/README.md, then$CORPUS_DIR/playbooks/repository-review.md. Treat the playbook as a scaffold you can adapt, and record any omission with the local evidence that required it. -
Run the playbook with this repo as the target. Hold one model and coding-agent configuration constant. Start from this repo's own instructions,
CLAUDE.mdanddocs/agents/, before pulling any corpus thesis. Pull a corpus thesis only when local evidence leaves an owning decision unresolved. Keep the corpus read-only, and adapt its ideas without copying its file layouts, version pins, or fixtures. -
Deliver findings ordered by consequence, following the playbook's Findings section. For each, name the invariant at risk, the concrete evidence and owning boundary, why existing proof missed it, and the smallest owning correction.
This command inspects only. It does not authorize changes to the repo. To act on
one finding through a bounded change-and-verify loop, run /improve-harness.
If $ARGUMENTS names a focus area, weight the review there while still answering
the playbook's outcome questions.
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.
- 10d ago First seen · 43 lines · 18 tokens per session scan A 7d1b4e0e3716
harness-review is a command published in the GitHub repository Contrast-Security-OSS/mcp-contrast (23 stars, last pushed 6d ago), licensed Apache-2.0. It adds 18 tokens to every session and 455 once invoked, about $0.0001 per session on Opus 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-30.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.