test-harness SKILL.md skillA

test-harness from phuryn/product-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add phuryn/product-engineering/test-harness@git:20261113.1e01017

Pins git:20261113.1e01017 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
phuryn/product-engineering
Path
ai-shipping/skills/test-harness/SKILL.md
Versions recorded
5
Latest version
git:20261113.1e01017, committed Nov 13, 2026
First version recorded
Nov 7, 2026
Size
15,540 bytes
Repository stars
643
License
MIT

Writing or running tests, proving a fix, a red or flaky run, a fix that didn't land, 'is it verified', 'run the gate': tests where green means something.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Test harness — so a green gate means something

**Make each harness prove something real before trusting its green result.** A suite can pass against the wrong server, database, fixture branch, or developer's `.env` and prove nothing. This skill arranges the harnesses, defines gate runs and reporting, and keeps green runs honest with rules learned from bugs.

**On another stack, keep the principle and swap the mechanism.** Each rule states its principle first and the mechanism second. The web-app mechanisms use Next.js (App Router), Supabase Postgres, Clerk, Vitest, and Playwright. The two-halves mechanisms were learned on a relay service with a web client and an editor extension with desktop installers that drives a CLI agent.

**The product's own instructions come first** — where they name its scripts, folders, or coverage file, follow them.

## The one question: what does each harness fake?

**A bug survives exactly where every harness fakes the same side.** Coverage of surfaces is not coverage of journeys. Before adding a suite, write down what it makes real. If everything else already fakes the same side, it mostly re-covers ground.

| Harness | Makes real | Fakes | Runs |
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_54xjf4uq55j5mpol/81035c9d0b2c96560f16d3f4561aeabb48b0f7d4eb46e41924722285e3c43ad3.json

Then /plugin install test-harness@markdownregistry-54xjf4uq55j5mpol in Claude Code. It installs git:20261113.1e01017, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add phuryn/product-engineering/test-harness@sha256:81035c9d0b2c9656

The line at the top of this page pins the label git:20261113.1e01017, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_54xjf4uq55j5mpol.svg)](https://markdownregistry.com/a/art_54xjf4uq55j5mpol)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in phuryn/product-engineering/test-harness since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of test-harness from somewhere else? Ask it: where did my test-harness come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 5 versions of this file, between Nov 7, 2026 and Nov 13, 2026, about one every 2 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261113.1e01017 latest2026-11-13 1e01017 15,540 BA view · diff
git:20261113.27e93282026-11-13 27e9328 15,496 BA view · diff
git:20261108.2e3add82026-11-08 2e3add8 15,013 BA view · diff
git:20261108.696d3dd2026-11-08 696d3dd 14,995 BA view · diff
git:20261107.53704ef2026-11-07 53704ef 16,545 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (15540 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

phuryn/product-engineering · 643 stars · license MIT · pushed 2026-11-18 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_54xjf4uq55j5mpol
GET https://markdownregistry.com/api/v1/resolve?ref=phuryn/product-engineering/test-harness
GET https://markdownregistry.com/api/v1/blob/81035c9d0b2c96560f16d3f4561aeabb48b0f7d4eb46e41924722285e3c43ad3

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from phuryn/product-engineering

AGENTS.md AGENTS.md file
phuryn/product-engineering · AGENTS.md
git:20261113.cab148b · audit A · 643 stars
CLAUDE.md CLAUDE.md file
phuryn/product-engineering · CLAUDE.md
git:20261028.30d344c · audit B · 643 stars
agent-instructions SKILL.md skill
phuryn/product-engineering · agent-harness/skills/agent-instructions/SKILL.md · Writing or restructuring AGENTS.md or CLAUDE.md, adding a rule ('remember this'), or after an agent ignored a rule it…
git:20261108.6aba512 · audit A · 643 stars
flight-deck SKILL.md skill
phuryn/product-engineering · agent-harness/skills/flight-deck/SKILL.md · 'What's the status', 'where were we', a progress report or status deck; long work that must survive compaction…
git:20261108.4d8bb2b · audit A · 643 stars
guardrail-hooks SKILL.md skill
phuryn/product-engineering · agent-harness/skills/guardrail-hooks/SKILL.md · An agent keeps breaking a rule ('it did it again', 'make this impossible', 'add a hook', 'my hook didn't fire'): make…
git:20261108.063a347 · audit A · 643 stars
handover SKILL.md skill
phuryn/product-engineering · agent-harness/skills/handover/SKILL.md · Write the handover a fresh session starts from: the objective, what is true now, the evidence actually obtained, what…
git:20261108.6aba512 · audit A · 643 stars
retro SKILL.md skill
phuryn/product-engineering · agent-harness/skills/retro/SKILL.md · Build a session's learnings into the setup: its friction, what went wrong and why, then an improved instruction, route…
git:20261108.063a347 · audit A · 643 stars
windows-agent-shell SKILL.md skill
phuryn/product-engineering · agent-harness/skills/windows-agent-shell/SKILL.md · A coding agent on Windows: Git Bash path rewriting, PowerShell quoting and encoding, CRLF. Use when output comes back…
git:20261108.4d8bb2b · audit B · 643 stars
claude-agents SKILL.md skill
phuryn/product-engineering · agent-teams/skills/claude-agents/SKILL.md · 'Ask Claude', 'have Claude build or review this': drive Claude Code headless (claude -p) from another agent as a peer…
git:20261113.cab148b · audit A · 643 stars
codex-agents SKILL.md skill
phuryn/product-engineering · agent-teams/skills/codex-agents/SKILL.md · 'Ask Codex', 'check with Codex', handing Codex a build or review, or stuck between two framings: the Codex CLI as peer…
git:20261114.b203f38 · audit A · 643 stars
delegation SKILL.md skill
phuryn/product-engineering · agent-teams/skills/delegation/SKILL.md · Before spawning a subagent or dispatching a build, review or research, and before trusting its report: the brief, the…
git:20261113.cab148b · audit A · 643 stars
grok-agents SKILL.md skill
phuryn/product-engineering · agent-teams/skills/grok-agents/SKILL.md · 'Ask Grok', 'have Grok build or review this': drive the Grok CLI headless from another agent as a peer, builder or…
git:20261113.1e01017 · audit A · 643 stars

Every file in phuryn/product-engineering

Other files named test-harness

test-harness SKILL.md skill
mathews-tom/armory · skills/test-harness/SKILL.md · Generates pytest test suites with happy path, edge cases, error conditions, fixture scaffolding, mocks, async patterns…
v1.1.1 · audit A · 344 stars

Browse by kind, by grade A, or by owner.