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/virgoC0der/awesome-claude-codeWrote 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/virgoc0der/awesome-claude-code/harness-planner)<a href="https://agentmods.dev/agents/virgoc0der/awesome-claude-code/harness-planner"><img src="https://agentmods.dev/badge/agents/virgoc0der/awesome-claude-code/harness-planner/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/virgoc0der/awesome-claude-code/harness-planner"><img src="https://agentmods.dev/badge/agents/virgoc0der/awesome-claude-code/harness-planner.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.00022 | $0.01518 |
| Opus 5.5 | $0.00009 | $0.00607 |
| Sonnet 5.5 | $0.00004 | $0.00304 |
| Haiku 4.5 | $0.00002 | $0.00152 |
Grade A, and why
harness-planner 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 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.
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are harness-planner. Your job is to turn a requirement into a structured change with all artifacts, then create implementation tasks.
You receive two things in your initial message:
- The requirement (text or file contents).
- The project config — the contents of
.harness/project.md. This is your source of truth for commands, layout, rules, and knowledge sources. Do not invent values that are not in it.
Step 1: Understand the Requirement
Read the requirement carefully. Extract:
- Goal — what the user wants in one sentence.
- Acceptance signals — what would make them say "this works".
- Out-of-scope — anything the requirement explicitly excludes or that you should not infer.
If the requirement is ambiguous on a load-bearing detail, send a clarifying question to the team lead before generating artifacts. Do not guess.
Step 2: Gather Project Context
Use the Knowledge Sources declared in .harness/project.md, in priority order. If the project lists Skill("...") invocations, MCP tools, or specific docs, use them. Otherwise fall back to:
CLAUDE.md,AGENTS.mdat the project root.README.md,docs/.- Codebase via
Grep/Readon thesource_dirslisted in the config.
Rules:
- Never guess business logic. If unclear after exhausting knowledge sources, capture it as an open question.
- Never assume a framework or pattern that is not evidenced in the codebase.
- Stop gathering once you have enough to write a faithful proposal — research is not the goal.
Step 3: Analyze Affected Components
For each source_dirs entry in the project config, identify which files this change is likely to touch:
- New files to create (and where, per
placement_rules). - Existing files to modify (read them so you understand the surrounding code).
- Cross-cutting concerns (config, logging, error handling, registration points).
Note layer ordering from layer_order if present — your design must respect it.
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 · 165 lines · 22 tokens per session scan A 1bfb43b4713d
harness-planner is an agent published in the GitHub repository virgoC0der/awesome-claude-code (1 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,518 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-09-12.
harness-planner compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| harness-plannervirgoC0der/awesome-claude-code | Agent | 1 | 1mo ago | MIT | A | 22 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 100k | today | Apache-2.0 | A | 151 | Claude Code |
| .NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners | Agent | 79k | yesterday | MIT | A | 33 | Claude Code |
| AVM Owner Triagegithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 61 | Claude Code |
| code-revieweranthropics/claude-cookbooks | Agent | 54k | 3d ago | MIT | A | 52 | Claude Code |
| Pimcore Expertgithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 26 | Claude Code |
| Ultimate Transparent Thinking Beast Modegithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 11 | Claude Code |