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.
git 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-harness-pm)<a href="https://agentmods.dev/agents/intense-visions/harness-engineering/harness-harness-pm"><img src="https://agentmods.dev/badge/agents/intense-visions/harness-engineering/harness-harness-pm.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.00020 | $0.02708 |
| Opus 5 | $0.00010 | $0.01354 |
| Sonnet 5 | $0.00004 | $0.00542 |
| Haiku 4.5 | $0.00002 | $0.00271 |
Grade A, and why
harness-harness-pm 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 8d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Owns acceptance-criteria and eval-coverage quality. Reviews every spec for measurable, testable, complete success criteria; flags user-visible behaviors with no covering test; blocks specs that ship with no measurable criteria. The upstream twin of the outcome-eval ship gate.
Skills
- acceptance-eval
Steps
- Run
harness validate(always) - Execute acceptance-eval skill (on_pr)
- Execute acceptance-eval skill (manual)
Methodology
Acceptance Eval
Pre-execution LLM-judgment: does this spec carry measurable, testable, complete acceptance criteria before work begins? Resolves the spec's acceptance section, critiques observability / testability / completeness (advisory
criteriaFindings), flags user-visible behaviors with no covering test (advisorycoverageFindings), and emits a confidence-ratedAcceptanceVerdict(MEASURABLE | NOT_MEASURABLE | INCONCLUSIVE) with a rationale. Merge authority is derived in TypeScript, never trusted from the LLM: a high-confidenceNOT_MEASURABLEblocks merge; every other verdict is advisory. The upstream twin of theoutcome-evalship gate — it keeps the downstream gate fed with judgable specs.
When to Use
- On every spec entering the repo under
docs/changes/**— triggeredon_pr(andmanual) — before execution begins. - When you need a durable, structured answer to "can this spec's success be objectively judged later?"
- NOT for judging whether an implementation satisfied its spec post-execution (use
outcome-eval, the downstream twin). - NOT for authoring acceptance criteria —
acceptance-evalreviews; humans own the thinking layer. It never writes the criteria it judges. - NOT for rule-based floors (lint/architecture/entropy) or other craft ceilings — those run elsewhere.
- NOT when no judgable spec section exists — the verdict degrades to INCONCLUSIVE/advisory and never blocks.
Process
Phase 1: RESOLVE — Find the judgment section
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.
- 8d ago First seen · 136 lines · 20 tokens per session scan A 215c882e0ccf
harness-harness-pm is an agent published in the GitHub repository Intense-Visions/harness-engineering (20 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 2,708 once invoked, about $0.0001 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.