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 agents/contrast-security-oss/mcp-contrast/harnessgit 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/agents/contrast-security-oss/mcp-contrast/harness)<a href="https://agentmods.dev/agents/contrast-security-oss/mcp-contrast/harness"><img src="https://agentmods.dev/badge/agents/contrast-security-oss/mcp-contrast/harness.svg" alt="Measured on agentmods" 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.00000 | $0.00757 |
| Opus 5 | $0.00000 | $0.00378 |
| Sonnet 5 | $0.00000 | $0.00151 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness engineering route
The harness-engineering corpus is a read-only context bundle and set of playbooks by Ryan Lopopolo, meant to be pointed at a target repository. Two project commands run its playbooks against this repo just in time, so the corpus is never preloaded into CLAUDE.md.
/harness-reviewruns the repository-review playbook, a broad diagnostic of whether a coding agent can recover the real job, make a coherent change, prove the outcome, and operate safely here without a human relay./improve-harnessruns the improve-harness playbook, one bounded loop from baseline through the earliest failed handoff to the smallest owning intervention, native verification, and a fresh rerun.
Both commands read the corpus AGENTS.md, follow its routing to the named
playbook, and keep the corpus read-only. This repo is always the target.
Locate the corpus
The corpus is pinned to commit 226c8d35fb6ea3ed55467753dba6dea2b5fd5778 for
reproducible runs. Any developer with git and network access resolves the same
commit, no pre-existing local layout required. Run this to resolve CORPUS_DIR.
CORPUS_COMMIT=226c8d35fb6ea3ed55467753dba6dea2b5fd5778
CORPUS_URL=https://github.com/lopopolo/harness-engineering.git
CACHE_DIR=$HOME/.cache/harness-engineering/$CORPUS_COMMIT
# Fast path, reuse a local checkout only when it already sits on the pin.
# Never checkout inside a developer's own clone, the corpus stays read-only.
if [ -n "$HARNESS_ENGINEERING_DIR" ] && \
[ "$(git -C "$HARNESS_ENGINEERING_DIR" rev-parse HEAD 2>/dev/null)" = "$CORPUS_COMMIT" ]; then
CORPUS_DIR=$HARNESS_ENGINEERING_DIR
else
# Managed per-user cache, clone once and pin to the exact commit.
if [ ! -e "$CACHE_DIR/AGENTS.md" ]; then
git clone --quiet "$CORPUS_URL" "$CACHE_DIR"
fi
git -C "$CACHE_DIR" fetch --quiet origin "$CORPUS_COMMIT" 2>/dev/null || true
git -C "$CACHE_DIR" checkout --quiet "$CORPUS_COMMIT"
CORPUS_DIR=$CACHE_DIR
fi
echo "corpus $CORPUS_DIR at $(git -C "$CORPUS_DIR" rev-parse HEAD)"
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.
- 6d ago First seen · 63 lines · 0 tokens per session scan A 3816619beefa
harness is an agent published in the GitHub repository Contrast-Security-OSS/mcp-contrast (23 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 757 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.