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/intense-visions/harness-engineering/harness-code-reviewergit clone --depth 1 https://github.com/Intense-Visions/harness-engineeringWrote 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/intense-visions/harness-engineering/harness-code-reviewer)<a href="https://agentmods.dev/agents/intense-visions/harness-engineering/harness-code-reviewer"><img src="https://agentmods.dev/badge/agents/intense-visions/harness-engineering/harness-code-reviewer.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 | $0.00045 | $0.10444 |
| Opus 5 | $0.00023 | $0.05222 |
| Sonnet 5 | $0.00009 | $0.02089 |
| Haiku 4.5 | $0.00005 | $0.01044 |
Grade A, and why
harness-code-reviewer 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 4d 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.
This is a copy
89% identical to harness-adversarial-reviewer — 15 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.
How it starts
The opening of the file, as written. The whole thing — 877 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Perform AI-powered code review incorporating harness validation, architectural analysis, and project-specific calibration. Produces structured Strengths/Issues/Assessment output.
Skills
- harness-code-review
Steps
- Run
harness validate(always) - Run
harness check-deps(always) - Run
harness check-docs(on_pr) - Run
harness check-perf(on_pr) - Execute harness-code-review skill (on_pr)
- Execute harness-code-review skill (manual)
Methodology
Harness Code Review
Multi-phase code review pipeline — mechanical checks, graph-scoped context, parallel review agents, cross-agent deduplication, and structured output with technical rigor over social performance.
When to Use
- When performing a code review (manual invocation or triggered by
on_pr/on_review) - When requesting a review of completed work (see Role A at the end of this document)
- When responding to review feedback (see Role C at the end of this document)
- NOT for in-progress work (complete the feature first)
- NOT for rubber-stamping (if you cannot find issues, look harder or state confidence level)
- NOT for style-only feedback (leave that to linters and mechanical checks)
Argument Resolution
When invoked by autopilot (or with explicit arguments), resolve paths before starting:
- Session slug: If
session-slugargument provided, set{sessionDir} = .harness/sessions/<session-slug>/. Pass togather_context({ session: "<session-slug>" }). All handoff writes go to{sessionDir}/handoff.json. - Commit range: If
commit-rangeargument provided (e.g.,abc123..HEAD), use as diff scope in Phase 2 MECHANICAL and Phase 7 OUTPUT. Otherwise, auto-detect from git environment.
When no arguments are provided (standalone invocation), session slug is unknown — omit from gather_context, fall back to global .harness/ paths. Diff scope auto-detected.
Process
Iron Law
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.
- 4d ago First seen · 877 lines · 45 tokens per session scan A 8a92d04394d2
harness-code-reviewer is an agent published in the GitHub repository Intense-Visions/harness-engineering (20 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 10,444 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to harness-adversarial-reviewer, differing in 15 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.