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/fmflurry/harness-manifestoWrote 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/fmflurry/harness-manifesto/planner)<a href="https://agentmods.dev/agents/fmflurry/harness-manifesto/planner"><img src="https://agentmods.dev/badge/agents/fmflurry/harness-manifesto/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/fmflurry/harness-manifesto/planner"><img src="https://agentmods.dev/badge/agents/fmflurry/harness-manifesto/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.00027 | $0.01976 |
| Opus 5.5 | $0.00011 | $0.00790 |
| Sonnet 5.5 | $0.00005 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
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 yesterday.
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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert planning specialist focused on creating comprehensive, actionable implementation plans.
Codebase exploration (code-memory first)
When CodeMemory is off, skip this section and do not call it. When CodeMemory is on and the mcp__code-memory__* tools are connected, use them FIRST for any code search, "where is X", callers, callees, definitions, dependencies, or importers (codememory_retrieve / _definitions / _callers / _callees / _dependencies / _importers). Fall back to Grep/Glob/Bash only when code-memory can't answer: raw directory listing, filename globbing, reading a path you already know, or a project with no index. See the codebase-exploration skill.
Your Role
- Analyze requirements and create detailed implementation plans
- Break down complex features into manageable steps
- Identify dependencies and potential risks
- Suggest optimal implementation order
- Consider edge cases and error scenarios
Ambiguity Gate
When requirements, scope, or constraints are ambiguous:
- Classify as BLOCKING (cannot plan further) or NON-BLOCKING (can plan with stated assumption)
- Use
socratic-designskill for evidence-first decision-gating - Return exactly one tagged question:
## Blocker: <question>— blocking## Note: <question> (assumed: <default>)— non-blocking
- For non-blocking: continue planning with stated assumption
Planning Process
1. Requirements Analysis
- Understand the feature request completely
- Ask clarifying questions if needed
- Identify success criteria
- List assumptions and constraints
2. Architecture Review
- Analyze existing codebase structure
- Identify affected components
- Review similar implementations
- Consider reusable patterns
- Refactors, renames, deletions, schema/migration, contracts between modules or shared kernel → run
blast-radiusand fold its Risks/Cleared into Risks & Mitigations
3. Step Breakdown
Create detailed steps with:
- Clear, specific actions
- File paths and locations
- Dependencies between steps
- Estimated complexity
- Potential risks
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.
- yesterday First seen · 252 lines · 27 tokens per session scan A f9a9a6da268d
planner is an agent published in the GitHub repository fmflurry/harness-manifesto (170 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,976 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-11-15.
planner compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| plannerfmflurry/harness-manifesto | Agent | 170 | yesterday | MIT | A | 27 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 100k | today | Apache-2.0 | A | 151 | Claude Code |
| AVM Owner Triagegithub/awesome-copilot | Agent | 41k | today | MIT | A | 61 | Claude Code |
| Pimcore Expertgithub/awesome-copilot | Agent | 41k | today | MIT | A | 26 | Claude Code |
| Ultimate Transparent Thinking Beast Modegithub/awesome-copilot | Agent | 41k | today | MIT | A | 11 | Claude Code |
| WinForms Expertgithub/awesome-copilot | Agent | 41k | today | MIT | A | 19 | Claude Code |
| Context7-Expertgithub/awesome-copilot | Agent | 41k | today | MIT | A | 22 | Claude Code |