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 skills/broomva/harness-engineering/harness-engineeringnpx skills add broomva/harness-engineering --skill harness-engineeringgit clone --depth 1 https://github.com/broomva/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/skills/broomva/harness-engineering/harness-engineering)<a href="https://agentmods.dev/skills/broomva/harness-engineering/harness-engineering"><img src="https://agentmods.dev/badge/skills/broomva/harness-engineering/harness-engineering.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.00054 | $0.00516 |
| Opus 5 | $0.00027 | $0.00258 |
| Sonnet 5 | $0.00011 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
harness-engineering-playbook 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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Engineering Playbook
A skills.sh-compatible skill that operationalizes the practices from OpenAI's Harness Engineering guide. Use it to set up or refactor agent-first workflows so that autonomous runs are repeatable, observable, and safe.
Install
npx skills add broomva/harness-engineering-skill --skill harness-engineering-playbook
What It Does
- Bootstraps harness artifacts:
AGENTS.md,PLANS.md,docs/ARCHITECTURE.md,docs/OBSERVABILITY.md,Makefile.harness, and CI workflows. - Wraps deterministic commands behind
make smoke,make check,make ciso agents can run them reliably. - Enforces strict module boundaries and data-shape contracts.
- Wires structured observability (correlation IDs, key transitions) from day 1.
- Adds entropy-control audits and nightly harness checks to prevent docs drift and flaky scripts.
Workflow
- Baseline the target repo — detect language, toolchain, and existing CI.
- Bootstrap harness artifacts from templates (interactive wizard or shell script).
- Apply the nine Harness Engineering practices across repo artifacts.
- Validate with
audit— treat anyMISSINGorFAILas blocking. - Iterate after real agent runs — patch gaps and re-audit.
Quick Start
# Interactive wizard (recommended)
python3 .agents/skills/harness-engineering-playbook/scripts/harness_wizard.py init <repo-path> --profile control
# Shell fallback
./scripts/bootstrap_harness.sh <repo-path>
# Audit
python3 .agents/skills/harness-engineering-playbook/scripts/harness_wizard.py audit <repo-path>
Profiles
| Profile | Scope |
|---|---|
baseline |
Core harness artifacts only |
control |
Baseline + control-system primitives |
full |
Control + entropy controls, nightly audit, CI |
Source
OpenAI Harness Engineering guide: https://openai.com/index/harness-engineering/
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.
- 5d ago First seen · 60 lines · 54 tokens per session scan A 8d6fe3e3e5e4
harness-engineering-playbook is a skill published in the GitHub repository broomva/harness-engineering (25 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 516 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
report
CEO dashboard with progressive disclosure — 3 tiers: headline (5 lines, default), summary (per-goal detail), deep (full weekly analysis). Takes an optional argument: headline (default), summary, deep, or legacy aliases daily/weekly.
brainstorm
Structured brainstorm — from quick Socratic refinement to full C-suite strategy sessions. The missing step before /directive: figure out WHAT to do before telling agents to DO it. Takes a question or topic as argument.
walkthrough
Cognitive walkthrough — simulate real user scenarios against the current system to find gaps between ideal and actual. Takes an optional scenario name or 'all' to run standing scenarios. Run after major directives or periodically as a reality check.
gruai-agents
Scaffold a variable-sized AI agent team into the current project. This replaces the old gruai init CLI command.
code-review-excellence
Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++. Helps catch bugs, improve code quality, and give constructive feedback. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring…
gruai-config
Update the gruai framework files (skills, pipeline docs, templates) to the latest version. This replaces the old gruai update CLI command.