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/improve-harness.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/improve-harness)<a href="https://agentmods.dev/commands/contrast-security-oss/mcp-contrast/improve-harness"><img src="https://agentmods.dev/badge/commands/contrast-security-oss/mcp-contrast/improve-harness/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/improve-harness"><img src="https://agentmods.dev/badge/commands/contrast-security-oss/mcp-contrast/improve-harness.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.00468 |
| Opus 5 | $0.00009 | $0.00234 |
| Sonnet 5 | $0.00004 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
improve-harness 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 9d 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
/improve-harness
Run Ryan Lopopolo's harness-engineering improve-harness playbook against this repository. It closes one bounded operational loop, from baseline through the earliest failed handoff to the smallest owning intervention, native verification, and a fresh rerun.
The job to improve is passed as $ARGUMENTS. If none is given, ask for one
bounded, representative job before starting.
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, and use its Context routing inside the gap-classification step. -
Read
$CORPUS_DIR/playbooks/README.md, then$CORPUS_DIR/playbooks/improve-harness.md. Treat the procedure as a scaffold you can adapt or reject, and record what changed and why. -
Run the loop with this repo as the target. Record the job contract first, and establish scope and authority before changing anything. Change this repo only when the task and its authority contract grant that operation, otherwise stop after recording the evidence, proposed owner, intervention, proof plan, and expected effect.
-
Implement the smallest reversible change at the earliest owner, then verify both layers. Run this repo's native checks (
make check, plusmake verifywhen credentials allow), and exercise the user or operational journey that establishes the accepted outcome. -
Record the compact result where this repo keeps architecture or history, a bead comment, an ADR under
docs/adr/, orCONTEXT.md. Name the owner, the evidence, and the retirement condition.
Keep the corpus read-only, and adapt its ideas without copying its file layouts, version pins, or fixtures. Follow this repo's branching and PR workflow in CLAUDE.md for any change.
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.
- 9d ago First seen · 46 lines · 18 tokens per session scan A 38d9ab04834f
improve-harness is a command published in the GitHub repository Contrast-Security-OSS/mcp-contrast (23 stars, last pushed 4d ago), licensed Apache-2.0. It adds 18 tokens to every session and 468 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.