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-simplifygit 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-simplify)<a href="https://agentmods.dev/skills/uppifyagency/claude-harness/harness-simplify"><img src="https://agentmods.dev/badge/skills/uppifyagency/claude-harness/harness-simplify/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-simplify"><img src="https://agentmods.dev/badge/skills/uppifyagency/claude-harness/harness-simplify.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.00086 | $0.00795 |
| Opus 5 | $0.00043 | $0.00398 |
| Sonnet 5 | $0.00017 | $0.00159 |
| Haiku 4.5 | $0.00009 | $0.00080 |
Grade A, and why
harness-simplify 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Simplify — Component Stress Testing
Overview
Every harness component encodes an assumption about what the model can't do on its own. This skill tests those assumptions by removing one component, re-running a task, and comparing quality.
"Find the simplest solution possible, and only increase complexity when needed."
Execution
Step 1: Identify Target Component
If the user specified a component, use it. Otherwise, ask which to test:
| Component | Assumption it encodes | Cost saved if removed |
|---|---|---|
evaluator |
Model can't judge its own work | ~$3-10 per eval round + time |
planner |
Model can't expand briefs well inline | ~$0.50 + 5 min |
rounds |
Model needs external feedback loops | Proportional to rounds saved |
Recommended test order: rounds → evaluator → planner (least to most impactful).
Step 2: Establish Baseline
Check for existing harness results in .harness/:
- If a completed run exists, use its eval scores as baseline
- If not, inform the user a baseline run is needed first
Record baseline scores:
Baseline (all components):
Design Quality: X/5
Originality: X/5
Craft: X/5
Functionality: X/5
Cost: $X
Time: Xm
Step 3: Run Without Component
Temporarily disable the component in .harness/config.json and dispatch a new harness run on the same brief.
- Remove evaluator: Generator builds, no QA pass. User or simplified heuristic checks quality.
- Remove planner: Generator works directly from user brief (no spec expansion).
- Reduce rounds: Set
maxRounds: 1(single build + single eval).
Step 4: Compare Results
If evaluator is enabled for comparison, dispatch it on both outputs. Present side-by-side:
With Component Without Component
Design Quality: 4/5 3/5
Originality: 3/5 3/5
Craft: 4/5 4/5
Functionality: 4/5 2/5
Cost: $125 $72
Time: 3h50m 2h07m
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 · 91 lines · 86 tokens per session scan A bca703a78f1a
harness-simplify is a skill published in the GitHub repository uppifyagency/claude-harness (5 stars, last pushed 5mo ago), licensed MIT. It adds 86 tokens to every session and 795 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
test-run
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.
implement
Implement a ticket or feature with proportional planning, test first behavior changes, independent review when available, and verification through the real affected surface.
symfony:doctrine-fixtures-foundry
Create test data with Zenstruck Foundry v2 factories (PersistentObjectFactory, real objects); define states, sequences, and relationships.
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.
symfony:tdd-with-pest
Apply RED-GREEN-REFACTOR with Pest v4 (PHP 8.3+) for Symfony via the PHPUnit bridge; Foundry factories, WebTestCase, verify failures first.