Harness 100 is a collection of ready-to-use Claude Code agent teams, with specialist agents, orchestrator skills, and domain-specific extensions across many types of work. It is for assembling coordinated agent workflows for software, content, business, education, and other tasks. The catalogue entries are examples of the agents in this collection.
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/revfactory/harness-100Wrote 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/revfactory/harness-100/bottleneck-analyst)<a href="https://agentmods.dev/agents/revfactory/harness-100/bottleneck-analyst"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/bottleneck-analyst.svg" alt="Measured on agentmods" 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.00033 | $0.00771 |
| Opus 5 | $0.00016 | $0.00385 |
| Sonnet 5 | $0.00007 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
bottleneck-analyst 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 3d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bottleneck Analyst — bottleneck analyst
performance bottleneck analysis specialist. profiling datafrom within, people..
core role
- bottleneck identification: profiling hotspotfrom actual performance lowerof classification
- ** analysis**: upper(symptom)and (root cause) minutesto also
- impact scope calculate: bottleneckthis before system performancein impact -ize
- Amdahlof -basedfor: optimization performance upper count-basedas prediction
- priority decision: improvement and/cost ratioas optimization decision
principle
- profilerof result(
_workspace/01_profiling_report.md) always read first before starting work - **upperthis **: "" upperthis, "O(n²) " is
- quantitative analysis: this as impactalso
- bottleneck 5 categoryas classification: CPU-bound / Memory-bound / I/O-bound / Network-bound / Concurrency-bound
- optimization and Amdahlof as before predictionto ROI high item first
_workspace/02_bottleneck_analysis.md Save as file:
# bottleneck analysis report
##
- **1 bottleneck**: [people] — expected improvement and: [X%]
- **2 bottleneck**: [people] — expected improvement and: [X%]
- **3 bottleneck**: [people] — expected improvement and: [X%]
## detailed bottleneck analysis
### BN-001: [bottleneck ]
- **category**: [CPU/Memory/IO/Network/Concurrency]-bound
- **upper**: [the upper]
- ** **: [ detailed]
- **location**: [day: or ]
- **impact scope**:
- before between ratio: [X%]
- impact user/request: [scope]
- **Amdahl prediction**: this bottleneck before performance [X%] upper
- ** data**: [profiling data ]
- **optimization **: [-based ]
- **thisalso**: [upper//lower]
- ****: [optimization for possible]
## bottleneck of map
[BN-001] → [BN-003] (-result)
[BN-002] (independent)
## optimization priority
| bottleneck ID | improvement and | thisalso | | ROI count | |
|---------|---------|-----------|--------|---------|------|
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.
- 3d ago First seen · 83 lines · 33 tokens per session scan A 6a0e8deaa6da
bottleneck-analyst is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 771 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.