Claude Code Harness is a development workflow for coding agents that organizes work into planning, implementation, review, synchronization, and release stages. It helps developers keep specifications, tests, independent reviews, and release evidence connected while using tools such as Claude Code, Codex CLI, Cursor, or Grok.
Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Chachamaru127/claude-code-harness/plugin install claude-code-harnessWrote 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/skills/chachamaru127/claude-code-harness/cursor-review)<a href="https://agentmods.dev/skills/chachamaru127/claude-code-harness/cursor-review"><img src="https://agentmods.dev/badge/skills/chachamaru127/claude-code-harness/cursor-review.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.00056 | $0.01072 |
| Opus 5 | $0.00028 | $0.00536 |
| Sonnet 5 | $0.00011 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
cursor-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 today.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cursor:review - Advisory Cursor Review
Cursor Composer (composer-2.5-fast) を read-only second opinion として使う review skill。primary verdict は host brain (Opus / Claude role) が出す。
Quick Reference
cursor:review --base origin/main
cursor:review "Phase 88.5 command namespace diff"
Rules
-
Cursor review is advisory. The final verdict must come from the host reviewer.
-
Do not pass
--writetocursor-companion.sh. -
Use resolver/model routing, not direct env checks:
bash scripts/resolve-impl-backend.sh --backend cursor --role reviewer bash scripts/model-routing.sh --host cursor --role worker --field model -
Prefer the existing
harness-reviewcontract when a full review is requested. This command exists for users who explicitly ask for the Cursor lane.
Flow
-
Resolve the Harness helper root:
HARNESS_PLUGIN_ROOT="${HARNESS_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}" if [ -z "$HARNESS_PLUGIN_ROOT" ] && [ -n "${CLAUDE_SKILL_DIR:-}" ]; then probe="$(cd "${CLAUDE_SKILL_DIR}" && pwd)" while [ "$probe" != "/" ] && [ ! -d "$probe/scripts" ]; do probe="$(cd "$probe/.." && pwd)" done [ -d "$probe/scripts" ] && HARNESS_PLUGIN_ROOT="$probe" fi if [ -z "$HARNESS_PLUGIN_ROOT" ]; then echo "ERROR: HARNESS_PLUGIN_ROOT is not set and could not be derived from CLAUDE_PLUGIN_ROOT or CLAUDE_SKILL_DIR" >&2 exit 2 fi -
Determine review scope:
BASE_REF="${TASK_BASE_REF:-origin/main}" REVIEW_SCOPE="${ARGUMENTS:-}" if [ -n "${REVIEW_SCOPE}" ]; then set -- ${REVIEW_SCOPE} while [ "$#" -gt 0 ]; do case "$1" in --base) BASE_REF="${2:?--base requires a ref}" shift 2 ;; --base=*) BASE_REF="${1#--base=}" shift ;; *) shift ;; esac done fi DIFF_STAT="$(git diff --stat "${BASE_REF}..HEAD")" DIFF_TEXT="$(git diff "${BASE_REF}..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.
- today Changed · +5 lines 7a95f7d8a739
- 6d ago First seen · 115 lines · 56 tokens per session scan A 5bda12e55997
cursor-review is a skill published in the GitHub repository Chachamaru127/claude-code-harness (3,091 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,072 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…