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.
npx skills add SeongwoongCho/adaptive-harness --skill using-adaptive-harnessgit clone --depth 1 https://github.com/SeongwoongCho/adaptive-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/skills/seongwoongcho/adaptive-harness/using-adaptive-harness)<a href="https://agentmods.dev/skills/seongwoongcho/adaptive-harness/using-adaptive-harness"><img src="https://agentmods.dev/badge/skills/seongwoongcho/adaptive-harness/using-adaptive-harness/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/skills/seongwoongcho/adaptive-harness/using-adaptive-harness"><img src="https://agentmods.dev/badge/skills/seongwoongcho/adaptive-harness/using-adaptive-harness.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.00039 | $0.12734 |
| Opus 5 | $0.00019 | $0.06367 |
| Sonnet 5 | $0.00008 | $0.02547 |
| Haiku 4.5 | $0.00004 | $0.01273 |
Grade A, and why
using-adaptive-harness 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 11d 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 — 1,029 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adaptive-Harness Orchestration Protocol
QUICK REFERENCE — Follow this on EVERY task
This is the complete action sequence. After each step, IMMEDIATELY proceed to the next. Never pause, never respond to user mid-pipeline.
# 0. Determine mode
agent_mode = "dontAsk" if "--skip-interview" else "default"
plugin_root = Read(".adaptive-harness/.plugin-root") or "{{PLUGIN_ROOT}}"
# 1. ROUTE
router_result = Agent(subagent_type="adaptive-harness:router", mode=agent_mode, prompt="Classify: {task}\nRead .adaptive-harness/harness-pool.json")
response = parse_json(router_result)
# Router output includes ## NEXT_ACTION — follow those steps NOW, in this same response turn
# 1b. DISPLAY ROUTING SUMMARY (concise, before execution)
Output to user:
"Routing decision:
- Harness: {response.selected_harness or 'ensemble'}
- Task type: {response.taxonomy.task_type} | Uncertainty: {response.taxonomy.uncertainty} | Blast radius: {response.taxonomy.blast_radius}
- Reason: {response.reasoning}"
# 2. EXECUTE (pick ONE path)
if response.skip_routing:
→ Do the task directly. Write lightweight eval JSON. DONE.
elif response.ensemble_chains:
→ CHAIN ENSEMBLE:
a. Ensure git repo: Bash("git rev-parse --is-inside-work-tree 2>/dev/null || (git init && git add -A && git commit --allow-empty -m init)")
b. Run shared planning harness ONCE (no worktree)
c. Bash("git add -A && git diff --cached --quiet || git commit -m 'planning artifacts'")
d. Fan out sub-chains IN PARALLEL (sub_chains = [chain[1:] for chain in ensemble_chains]), each sub-chain runs sequentially in its own worktree with isolation="worktree"
e. Read synthesizer skill: Read("{plugin_root}/harnesses/synthesizer/skill.md")
f. Spawn synthesizer with BOTH worktree paths + skill.md → merges files into main workspace
elif response.ensemble_harnesses:
→ SIMPLE ENSEMBLE:
a. Spawn all harnesses IN PARALLEL, each with isolation="worktree"
b. Spawn synthesizer with worktree paths + skill.md
elif response.harness_chain and len > 1:
→ CHAIN: Write .chain-in-progress marker, execute sequentially, remove marker when done
else:
→ SINGLE: Read agent.md + skill.md, spawn one harness subagent
# 3. EVALUATE (immediately after execution completes)
Agent(subagent_type="adaptive-harness:evaluator", mode=agent_mode, prompt="Score result...")
# 4. RECORD (write eval JSON, update weights, copy to evaluation-logs/)
# 5. REPORT to user
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.
- 11d ago First seen · 1,029 lines · 39 tokens per session scan A bb5338918815
using-adaptive-harness is a skill published in the GitHub repository SeongwoongCho/adaptive-harness (8 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 12,734 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-08-31.
Other skills, from other repositories
relocate-claude-vm
Move the Claude Desktop "Computer Use" sandbox VM bundle (typically 11-13 GB at %APPDATA%\Claude\vmbundles on Windows) off the system drive to a roomier disk via a directory junction. Transparent to Claude Desktop, reversible. Use when the system drive is low on space and a disk scan shows vmbundles as a top consumer.…
autoresearch
Autonomous experiment loop: modifies code, runs experiments, evaluates metrics, keeps improvements. Inspired by karpathy/autoresearch + pi-autoresearch + autoexp. Triggers: /autoresearch, 'auto research', 'optimize continuously', 'experiment loop', 'autonomous optimization'.
security
Claude-driven security audit with an independent second opinion. Integrates the ralph-security agent (6 quality pillars, OWASP A01-A10). Uses LSP for code navigation during analysis. Use when: (1) /security is invoked, (2) task relates to security functionality.
task-batch
Autonomous batch task execution with PRD parsing, task decomposition, and continuous execution until all tasks complete. Uses /orchestrator internally. Stops only for major failures (no internet, token limit, system crash). Use when: (1) processing task lists autonomously, (2) PRD-driven development, (3) batch feature…
diagram-design
Create technical and product diagrams — architecture, flowchart, sequence, state machine, ER / data model, timeline, swimlane, quadrant, nested, tree, layer stack, venn, pyramid — as standalone HTML files with inline SVG. Ships with a neutral editorial skin and a first-run gate that prompts users to customize the…
create-task-batch
Interactive wizard to create PRD or task lists for /task-batch. Uses /clarify and /ask-questions-if-underspecified for precise task definition. Use when: (1) preparing batch execution, (2) creating PRDs, (3) defining task lists with dependencies. Triggers: /create-task-batch, 'create tasks', 'new batch', 'prepare PRD'.