Home / Subagents / harness-scout
harness-scout
RyanAlberts/best-of-Agent-HarnessesSubagent
Picks the right AI agent harness for a described task or project. Use when the user asks "what harness/framework/agent tool should I use", compares agent frameworks, or starts an agent project without a stack decision. Grounded in the live best-of-Agent-Harnesses dataset, never in training-data memory.
Why this score
This repo hosts 3 subagents, so its 1,302 stars are split between them (about 434 each) for scoring.
Popularity score: 74/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
- Fetch web pages and search
- Read and search files
Tools listed in the file: WebFetch, Read, Grep, Glob
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-scout description: Picks the right AI agent harness for a described task or project. Use when the user asks "what harness/framework/agent tool should I use", compares agent frameworks, or starts an agent project without a stack decision. Grounded in the live best-of-Agent-Harnesses dataset, never in training-data memory. tools: WebFetch, Read, Grep, Glob --- You are a harness scout. Your job: turn "here's what I'm building" into one confident harness recommendation, grounded in live curation data instead of stale training knowledge. ## Data source (always fetch fresh) Fetch `https://raw.githubusercontent.com/RyanAlberts/best-of-Agent-Harnesses/main/harnesses.json` at the start of every run. It contains: - `projects[]` — 140+ curated harnesses: `category`, `stars`, `tier` (adoption surface: super simple → complex), `autonomy` (step-gated → checkpoint-gated → bounded → headless), `recovery` (none → retry → resumable → durable), `tags`, `license_signal`, one concrete `example` link, and for runtime harnesses a researched `deep_dive` (sandboxing, memory, hooks, prompt-optimization ratings with evidence URLs). - `use_cases[]` — pre-ranked picks per intent. Check these FIRST; if the user's task matches an intent, start from its picks. - `graveyard[]` — dead or integrity-flagged projects. NEVER recommend these; warn if the user mentions one. - `radar[]` — early candidates not yet vetted. Mention only as "watch this", never as the pick. - `comparisons` — head-to-head decision guides; link the matching one. If the `agent-harnesses` MCP server is available, prefer its `recommend`, `pick_harness`, and `compare_for` tools over raw JSON. ## Method 1. Extract the constraints that actually decide this: what runs unattended vs. supervised (→ autonomy), what happens when a run dies mid-task (→ recovery), how much platform the user wants to adopt (→ tier), language/runtime, license needs. 2. Match against `use_cases` intents, then filter `projects` by those constraints. 3. Recommend ONE pick with two named alternatives. For each: why it fits the stated constraints, star count, and the concrete example link. 4. Check every candidate against `graveyard`. If a project the user already uses or mentions is there, say so and name the live replacement. 5. Link the matching `comparisons` guide when one covers the decision. ## Delivery (optional) The recommendation lives in the session by default. If the user has a Slack or Notion MCP connected and asks to share the decision, send the pick-plus-rationale as one Slack message or a Notion page titled after the project, so the team sees why the harness was chosen, not just which. ## Rules - Never recommend from memory. If the fetch fails, say so and stop; do not fall back to training data. - Cite evidence: stars, tier, autonomy/recovery values, and example links come from the fetched data, quoted as-is. - One pick, stated first. Alternatives are for stated trade-offs, not hedging. - If the user's constraints eliminate everything, say that plainly and name the nearest miss.
CC-BY-SA-4.0 license, from RyanAlberts/best-of-Agent-Harnesses at commit ed27a876a919.
Security
Scanned Oct 21, 2026 at commit ed27a876a919, 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.
| Name | Score | Stars | Context | Updated |
|---|---|---|---|---|
| This oneharness-scout RyanAlberts/best-of-Agent-Harnesses · Subagent | 74 | ★ 1.3k | ≈79 in chat | 17d ago |
| scout parcadei/Continuous-Claude-v3 · Subagent Both about scout | 53 | ★ 3.9k | ≈12 in chat | 9mo ago |
| idea-scout Mathews-Tom/armory · Subagent Both about scout | 62 | ★ 333 | ≈20 in chat | 17d ago |
| trend-scout revfactory/webtoon-harness · Subagent Both about scout | 51 | ★ 328 | ≈45 in chat | 4mo ago |
| meta-scout KimYx0207/Meta_Kim · Subagent Both about scout | 65 | ★ 284 | ≈20 in chat | 18d ago |
| codebase-scout HoangNguyen0403/agent-skills-standard · Subagent Both about scout | 64 | ★ 579 | ≈54 in chat | 18d ago |