By dragantod
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.
Explicit helper for non-technical VibeCoder coaching: what to ask next, how to describe work, and how to stay safe. Do NOT load for: direct implementation, technical review, or Cursor/PM workflow.
Browser automation through the repo agent-browser CLI. Explicit helper for navigation, forms, screenshots, scraping, and web-app checks. Prefer Browser Use or Playwright when available. Do NOT load for: sharing URLs, embedding links, or editing screenshot files.
Explicit helper for authentication and payment implementation with Clerk, Supabase Auth, or Stripe. Do NOT load for: general UI work, database design, or non-auth features.
Team execution mode — backward-compatible alias for harness-work with team orchestration.
Validates brainstormed ideas with Cursor PM, updates Plans.md, then handoff back. Cursor ↔ Claude Code 2-Agent workflow support. Use when user mentions Cursor PM handoff, 2-agent plan validation, CC-Cursor round trip, or brainstorm review. Do NOT load for: implementation work, single-agent tasks, or direct coding.
Matches all tools
Hooks run on every tool call, not just specific ones
Executes bash commands
Hook triggers when Bash tool is used
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Executables (bin/) — files in this plugin's bin/directory are added to the Bash tool's PATH while the plugin is enabled.
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Plan. Work. Review. Ship.
Turn Claude Code into a disciplined development partner.
English | 日本語
Hokage line carries forward. Full Claude Code 2.1.99-2.1.110 + Opus 4.7 integration. Plugin manifest now matches the official
plugins-referenceschema.
Anthropic shipped Opus 4.7 with literal-instruction-following semantics, plus Claude Code 2.1.105 added the PreCompact hook and the monitors/monitors.json manifest. v4.2 makes Harness fit those changes precisely:
| Area | Before (v4.1) | After (v4.2) |
|---|---|---|
| Long-running workers | Could be silently compacted mid-task | PreCompact hook blocks compaction while a worker is active or Plans.md is dirty |
| Plugin validation | claude plugin validate rejected monitors/agents blocks | Public-spec compliant: monitors/monitors.json + agents/ auto-discovery |
| Sync regression | harness sync could silently strip declared blocks (4 prior incidents) | Two-layer guard: shell idempotency test + Go struct test for phantom fields |
| Long sessions | Default 5-minute prompt cache only | bash scripts/enable-1h-cache.sh opt-in to 1-hour TTL (CC v2.1.108) |
| Reviewer/Advisor effort | medium / high | xhigh (CC v2.1.111, Opus 4.7) — sharper review, with high fallback for other models |
| Agent prompts | Worked on Opus 4.6 implicit semantics | Re-tuned for Opus 4.7 literal instruction following — explicit thresholds, schemas, command names |
| Guardrails (R01-R13) | Conformed to CC 2.1.98 contract | Re-conformed to CC 2.1.110 (PermissionRequest updatedInput, PreToolUse additionalContext, Bash bypass closures) — 17 new regression tests |
What you'll notice:
claude plugin validate runs clean on Harness for the first time since monitors was addedharness sync stops mysteriously deleting your monitors/agents blockUpdate with the usual flow:
/plugin update claude-code-harness
For detailed Before/After in Japanese, see CHANGELOG.md [4.2.0] entry.
Go-native engine. 25x faster hooks. Zero Node.js dependency.
Every tool call Claude makes passes through Harness hooks. In v3, each pass cost 40-60ms of bash + Node.js overhead — a subtle drag you feel across hundreds of calls per session. v4 replaces the entire stack with a single Go binary:
| v3 (bash + Node.js) | v4 "Hokage" (Go) | |
|---|---|---|
| PreToolUse | 40-60ms | 10ms |
| SessionStart | 500-800ms | 10-30ms |
| PostToolUse | 20-30ms | 10ms |
| Node.js | Required (18+) | Not needed |
What you'll notice:
npm install or Node.js version issues on setupJust update the plugin — no configuration changes needed:
/plugin update claude-code-harness
Claude Code is powerful. Harness turns that raw capability into a delivery loop that is easier to trust and harder to derail.
The 5 verb skills keep setup, plan, work, review, and release on one path. The Go-native guardrail engine protects execution with sub-10ms response, and validation can be rerun when you need proof.
npx claudepluginhub dragantod/claude-code-harnessConsult multiple AI coding agents (Gemini, OpenAI, Grok, Perplexity, plus codex, antigravity, and grok CLIs when installed) to get diverse perspectives on coding problems
Matt Pocock's agent skills for real engineering — grilling, spec/ticket flows, TDD, code review, domain modelling and more. Plug-and-play, not vibe coding.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Lazy senior dev mode. Forces the simplest, shortest solution that actually works: YAGNI, stdlib first, no unrequested abstractions.