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 uppifyagency/claude-harness --skill harness-evalgit clone --depth 1 https://github.com/uppifyagency/claude-harnessWrote 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/uppifyagency/claude-harness/harness-eval)<a href="https://agentmods.dev/skills/uppifyagency/claude-harness/harness-eval"><img src="https://agentmods.dev/badge/skills/uppifyagency/claude-harness/harness-eval/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/uppifyagency/claude-harness/harness-eval"><img src="https://agentmods.dev/badge/skills/uppifyagency/claude-harness/harness-eval.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.00074 | $0.00423 |
| Opus 5 | $0.00037 | $0.00211 |
| Sonnet 5 | $0.00015 | $0.00085 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
harness-eval 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 9d 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.
What it actually says
Harness Eval — Standalone Evaluation
Overview
Run the evaluator agent independently to assess an application against a specification. Useful for:
- Checking existing applications against requirements
- Re-evaluating after manual fixes
- Final quality gate before shipping
- Comparing quality across different builds
Execution
Step 1: Locate the Spec
Check for spec in this order:
- Argument path (if provided)
.harness/spec.mdin current project- Ask the user to provide or point to a spec
Step 2: Verify Application is Running
Check if a development server is already running. If not, look for common start commands:
package.jsonscripts (dev,start)Makefiletargets- Docker compose files
- Ask the user if unclear
Step 3: Dispatch Evaluator
Dispatch the harness-evaluator agent with:
- The spec file
- Instructions to test the running application
- Any previous eval reports (for comparison)
Step 4: Present Results
Show the user:
- Overall verdict (PASS / ITERATE / PIVOT)
- Quality dimension scores
- Critical issues found
- Comparison with previous eval (if available)
Determine the eval round number from existing .harness/eval-report-*.md files and write the new report as the next number.
Additional Resources
Reference Files
references/custom-criteria.md— Adapting evaluation criteria for non-visual projects
What ships with it
1 file 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.
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.
- 9d ago First seen · 56 lines · 74 tokens per session scan A d6f9c8d512a7
harness-eval is a skill published in the GitHub repository uppifyagency/claude-harness (5 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 423 once invoked, about $0.0004 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-31.
Other skills, from other repositories
symfony:e2e-panther-playwright
Write end-to-end tests with Symfony Panther 2.4 for browser automation or Playwright for complex scenarios.
symfony:functional-tests
Write functional tests for Symfony controllers and HTTP endpoints using WebTestCase, getContainer, loginUser, and DAMA rollback.
ccc-e2e
CC Commander · $ccc-e2e · Full-surface confidence before you ship.
ccc-qa
QA workflow. Runs unit + integration + E2E tests, coverage delta, edge case enumeration, flaky test quarantine. Delegates to qa-engineer agent.
verify
A four-layer check for deciding whether a software feature is truly finished: code checks, runtime tests, end-to-end tests, and user-reported confirmation.
playwright-expert
Use when writing or fixing E2E tests in a Playwright project - playwright.config.ts, .spec.ts files under tests/ or e2e/, @playwright/test imports - or right after implementing a frontend/backend change that needs an end-to-end proof. Writes and extends TypeScript E2E suites as the QA gate for feature and bug-fix…