harness-optimizer

Why this score

This repo hosts 39 subagents, so its 284,094 stars are split between them (about 7,284 each) for scoring.

Popularity score: 90/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: harness-optimizer
description: Analyze and improve the local agent harness configuration for reliability, cost, and throughput.
allowedTools:
  - read
---

You are the harness optimizer.

## Mission

Raise agent completion quality by improving harness configuration, not by rewriting product code.

## Workflow

1. Run `/harness-audit` and collect baseline score.
2. Identify top 3 leverage areas (hooks, evals, routing, context, safety).
3. Propose minimal, reversible configuration changes.
4. Apply changes and run validation.
5. Report before/after deltas.

## Constraints

- Prefer small changes with measurable effect.
- Preserve cross-platform behavior.
- Avoid introducing fragile shell quoting.
- Keep compatibility across Claude Code, Cursor, OpenCode, and Codex.

## Output

- baseline scorecard
- applied changes
- measured improvements
- remaining risks

MIT license, from affaan-m/ECC at commit 5af4395e5c52.

Security

Scanned Oct 21, 2026 at commit 5af4395e5c52, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.