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 skills add stone16/harness-engineering-skills --skill harnessgit clone --depth 1 https://github.com/stone16/harness-engineering-skillsWrote 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/stone16/harness-engineering-skills/harness)<a href="https://agentmods.dev/skills/stone16/harness-engineering-skills/harness"><img src="https://agentmods.dev/badge/skills/stone16/harness-engineering-skills/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/skills/stone16/harness-engineering-skills/harness"><img src="https://agentmods.dev/badge/skills/stone16/harness-engineering-skills/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.00019 | $0.02132 |
| Opus 5.5 | $0.00008 | $0.00853 |
| Sonnet 5.5 | $0.00004 | $0.00426 |
| Haiku 4.5 | $0.00002 | $0.00213 |
Grade C, and why
harness scanned grade C with 2 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Verify (review roles): `{ find ~/.claude/plugins -path '*/plugins/harness-engineering-skills/agents/harness-*.md' -type f 2>/dev/null; ls plugins/harness-engineering-skills/agents/harness-*.md 2>/dev/null; ls ~/.claude/a Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
If not found, try `find ~/.claude/skills -path "*/harness/scripts/harness-engine.sh"` or `find ~/.codex/skills -path "*/harness/scripts/harness-engine.sh"` as fallback. In a checked-out repo, `plugins/harness-engineering Copies of this mod
1 near-identical copy found in the catalogue:
- harness — 89% identical, 41 lines differ
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness — Multi-Agent Orchestration
Orchestrate complex tasks through Planning -> Generation -> Evaluation -> Retro. Fresh sub-agents per checkpoint prevent drift. Retro accumulates learning across tasks.
Protocol Loading
This skill splits into two protocol files to minimize context usage. Read the one matching your intent before proceeding.
| Intent | Trigger phrases | Action |
|---|---|---|
| Planning | "harness plan", "harness this task", "use harness", "harness spec" | Read references/planning-protocol.md |
| Execution | "harness continue", "harness execute ", "harness " | Read references/execution-protocol.md |
After loading the protocol, follow it completely. Do not proceed without reading the appropriate reference file.
Recommended Workflow
Session 1 (Claude Code) → Brainstorm + Spec → Spec review with cross-model evaluator
↓ spec approved
Session 2 (Codex) → Execute checkpoints → Evaluate → E2E → Full-verify → PR → Retro
↕ Claude CLI as review-loop peer (cross-model quality gate)
- Session 1: Claude Code for interactive discovery — brainstorming + multi-turn Q&A to establish requirements. After the user approves the brainstormed design, spec drafting and the Spec Evaluator review loop run autonomously (agent-to-agent until consensus). See references/planning-protocol.md "Post-Brainstorming Autonomy".
- Session 2: Codex for autonomous execution — implementation, evaluation, PR creation, retro. Claude CLI serves as cross-model reviewer via
review-loop. - Both hosts support both phases. The above is the recommended flow, not a hard constraint.
Prerequisites
superpowersplugin installed (Claude Code): Generator preloads TDD, verification, debugging skills- Reviewer role definitions:
harness-convention-scout.md,harness-spec-evaluator.md,harness-generator.md,harness-evaluator.md,harness-retro.md— ship with this plugin atplugins/harness-engineering-skills/agents/; user overrides may live at~/.claude/agents/harness-*.md python3on PATH (engine JSON operations)gitrepository initialized- For Codex-hosted execution:
claudeCLI on PATH for sub-agent dispatch and review-loop
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- hooks/phase-guard.mjs 2.5 KB runs code
- references/checkpoint-definition.md 13 KB
- references/codex-mode.md 10.0 KB
- references/execution-protocol.md 22 KB
- references/planning-protocol.md 7.5 KB
- references/protocol-quick-ref.md 48 KB
- scripts/_cohort_spec.py 11 KB runs code
- scripts/claude-agent-invoke.sh 12 KB runs code
- scripts/harness-engine.sh 90 KB runs code
- scripts/normalize_claude_artifact.py 7.6 KB runs code
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.
- 1mo ago Changed · -9 lines · -111 tokens per session fa569f7c62b4
- 1mo ago First seen · 160 lines · 130 tokens per session scan C 4c5ba6587e98
harness is a skill published in the GitHub repository stone16/harness-engineering-skills (31 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 2,132 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
logic-review
Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…
logic-fix-all
Autonomous repository-wide audit-and-fix pipeline: health → review → locate/explain → fix → diff-verify → iterate until clean. Starts with a mandatory consent prompt (token-intensive); after consent runs hands-free. Trigger when the user wants ALL logic issues found and fixed — "fix everything", "fix all logic…
logic-health
Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…
run-iteration-eval
Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first. Use when the user wants to "run the…
new-skill
Scaffold a new logic- skill in the Logic-Lens repo and wire it into every place a skill must be registered, so no step is missed. Use when adding a seventh (or later) skill to Logic-Lens.
sync-skill-cache
Sync the Logic-Lens working-copy skills/ into the installed plugin cache so content-evals test the EDITED skill, not the last published one. ALWAYS run this after editing any skills//SKILL.md or guide/shared file and BEFORE running content-evals — otherwise the eval silently grades stale content and every token is…