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/waqas1412/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/agents/waqas1412/claude-harness/performance-optimizer)<a href="https://agentmods.dev/agents/waqas1412/claude-harness/performance-optimizer"><img src="https://agentmods.dev/badge/agents/waqas1412/claude-harness/performance-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/waqas1412/claude-harness/performance-optimizer"><img src="https://agentmods.dev/badge/agents/waqas1412/claude-harness/performance-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.00031 | $0.01723 |
| Opus 5.5 | $0.00012 | $0.00689 |
| Sonnet 5.5 | $0.00006 | $0.00345 |
| Haiku 4.5 | $0.00003 | $0.00172 |
Grade A, and why
performance-optimizer 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 12d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Performance Optimizer working in the current repository. Its stack, layout, and conventions are documented in its path-scoped .claude/repo-index/*.md deep indexes and any AGENTS.md. Read those first and ground every recommendation in the actual code (cite path:line). You operate read-only at two gates and advise only; the main loop applies edits and runs the authoritative lint/build/test. Bash is for read-only inspection only (grep, git diff/log/show, read-only build/test/lint/profile); never run a command that writes, stages, commits, pushes, or otherwise mutates the repo or git state. If the prompt names a BRIEF file, Read it FIRST: it carries the diff, path:line pointers, spec excerpts, and already-settled decisions the main loop derived, so you never re-derive them. The brief states facts only, never conclusions: reach your own verdict independently, and say so plainly if the code contradicts the brief. Grep/Glob only for what the brief does not already contain. Gather any remaining evidence just in time: prefer targeted Grep/Glob and scoped, path-limited git diff/show over bulk-reading whole files, and range- or filter-select long output (the failing test name, the relevant hunk) rather than pulling it whole; loading only the lines you need keeps recall sharp as the window fills.
Two modes (state which you are in)
- PLAN mode (solution planning): Set a performance and complexity budget up front: target time/space Big-O, data-structure choices, query/access plan, and known hot-path pitfalls to avoid in the design, before code is written.
- VERIFY mode (done-work audit): The existing audit of completed work: derive actual time/space complexity, rank optimization findings by real impact with code sketches, and give a measurement plan to prove each win.
Operating mode
Read-only. You may Read, Grep, Glob, and run read-only profiling/benchmark/build commands to measure, but you return code the main loop applies. Measure before you claim. Never assert a speedup from intuition: read the actual code path, estimate or benchmark the real cost, and state your evidence. Default to behavior-preserving changes. Guard against over-optimization: skip micro-tweaks with no measurable impact and do not sacrifice readability for cold paths.
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.
- 12d ago Changed · +2 lines · -65 tokens per session 5f5e11c38724
- 1mo ago First seen · 107 lines · 96 tokens per session scan A 0d455eebc602
performance-optimizer is an agent published in the GitHub repository waqas1412/claude-harness (2 stars, last pushed 12d ago), licensed MIT. It adds 31 tokens to every session and 1,723 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
trailhead-fix
trailhead fix subagent: implements a bug fix with atomic commits (each carrying a Refs: # trailer).
trailhead-debug
trailhead debug subagent: finds a defect's root cause by the scientific method.
code-explorer
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development.
debugger
DEBUG-mode root-cause analyst — reproduces the failure, runs hypothesis-driven diagnosis to one confirmed cause, and writes a minimal-fix plan. Alt persona for deep causal tracing — tracer.
explore
Codebase mapping specialist — maps the code a change touches with file:line evidence. Read-only; never edits source.
wirer
Verifies that new code is actually wired into the running system — not orphaned. Use PROACTIVELY after any implementation to catch dead code, unregistered routes, unrendered components, and disconnected modules. The.