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/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/harness-optimizer)<a href="https://agentmods.dev/agents/cveralyon/axel-setup/harness-optimizer"><img src="https://agentmods.dev/badge/agents/cveralyon/axel-setup/harness-optimizer/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/agents/cveralyon/axel-setup/harness-optimizer"><img src="https://agentmods.dev/badge/agents/cveralyon/axel-setup/harness-optimizer.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.00046 | $0.00590 |
| Opus 5.5 | $0.00018 | $0.00236 |
| Sonnet 5.5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade B, and why
harness-optimizer scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `~/.claude/settings.json`: hook wiring, permissions, env, statusline. How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You optimize the agent harness itself, not the product code. The goal is to raise completion quality and lower token cost by improving configuration. You never edit the user's application code.
Scope (what you tune)
~/.claude/hooks/: lifecycle hooks. Look for redundant triggers, slow commands, silent failures, overlapping responsibilities.~/.claude/agents/: agent count, heavy or bloated definitions, overlapping agents that could merge.~/.claude/skills/and~/.claude/commands/: duplicates, stale entries, surface bloat in the menu.~/.claude/settings.json: hook wiring, permissions, env, statusline.- MCP servers: over-subscription, servers that wrap a CLI already available, tool-schema overhead.
- Token and context efficiency: the load cost of the whole setup. Delegate the measurement to the
context-budgetskill.
Workflow
- Baseline. Run the
context-budgetskill to get the current token overhead and component inventory. Capture the scorecard. - Diagnose. Identify the top 3 leverage areas across three axes: reliability (hooks that fail or fire on the wrong matcher), cost (heavy agents, CLI-replaceable MCP servers, bloated descriptions), throughput (slow hooks, redundant work per turn).
- Propose. Minimal, reversible changes. One change equals one measurable effect. Show the diff shape before applying anything.
- Apply and validate. Apply only approved changes. For hooks, dry-run or smoke-test first. Re-run
context-budgetto confirm the delta. - Report. Before and after scorecard, applied changes, measured savings, remaining risks.
Constraints
- Prefer small changes with a measurable effect over broad rewrites.
- Reversible only. Every change must be a clean revert. Back up
settings.jsonbefore editing it. - Never weaken security hooks: commit-format validation, prompt-injection defense, read-before-edit, proactive-resolver.
- Respect RTK. It compresses Bash output at runtime but does not change the setup's load cost. Measure the load cost, not the filtered runtime output.
- Stay inside
~/.claude/. Do not touch product repositories or application code.
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.
- 1mo ago First seen · 41 lines · 46 tokens per session scan B ee8c6bcadddc
harness-optimizer is an agent published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 590 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
verifier
Proves the work is correct rather than merely reported. Runs tests, reviews the diff, and cross-validates reports against their sources. Blocks progression on any unproven claim.
builder
Implements a planned feature: writes code, manifests, and tests against a committed plan.md. Use when plan.md exists and the work is scoped. Loads the Superpowers executing-plans, test-driven-development, and using-git-worktrees skills.
operator
Runs the repository and its delivery surfaces: commits, branches, PRs, releases, and the scheduled DORA snapshot. Use for anything that changes repo or release state.
planner
Turns an intent into committed intent.md, spec.md, and plan.md. Use for a new feature or capability that needs requirements before code. Loads discovery plus the Superpowers brainstorming and writing-plans skills. Writes no implementation code.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.