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 agentmods add agents/darrenhinde/openagentscontrol/planning-agents-guidegit clone --depth 1 https://github.com/darrenhinde/OpenAgentsControlWrote 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/darrenhinde/openagentscontrol/planning-agents-guide)<a href="https://agentmods.dev/agents/darrenhinde/openagentscontrol/planning-agents-guide"><img src="https://agentmods.dev/badge/agents/darrenhinde/openagentscontrol/planning-agents-guide.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 | $0.00000 | $0.07756 |
| Opus 5 | $0.00000 | $0.03878 |
| Sonnet 5 | $0.00000 | $0.01551 |
| Haiku 4.5 | $0.00000 | $0.00776 |
Grade A, and why
planning-agents-guide 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 4d 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,136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Agents Guide
Purpose: Comprehensive guide to the planning agent ecosystem — when to use each agent, how they integrate, and best practices for DDD, story mapping, prioritization, contract testing, and ADRs.
Overview
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans:
- ArchitectureAnalyzer — DDD-driven architecture analysis
- StoryMapper — User journey mapping and story decomposition
- PrioritizationEngine — RICE/WSJF scoring and MVP identification
- ContractManager — API contract definition for parallel development
- ADRManager — Architecture decision record management
Key Principle: Each agent is context-aware and ALWAYS calls ContextScout before executing to ensure alignment with project standards.
Quick Decision Tree
Feature Request
│
├─ Complex domain logic? ──YES──> ArchitectureAnalyzer
│ NO
│ ↓
├─ User journey unclear? ──YES──> StoryMapper
│ NO
│ ↓
├─ Need prioritization? ──YES──> PrioritizationEngine
│ NO
│ ↓
├─ Parallel dev needed? ──YES──> ContractManager
│ NO
│ ↓
└─ Architectural decision? ─YES──> ADRManager
1. ArchitectureAnalyzer
When to Use
Use ArchitectureAnalyzer when:
- Feature spans multiple domains or business capabilities
- Need to identify bounded contexts before task breakdown
- Complex domain logic requires aggregate/entity modeling
- Module boundaries are unclear or need formalization
- Feature involves cross-context integration
- Need to establish architectural constraints before implementation
Do NOT use when:
- Feature is purely technical (no domain logic)
- Single, well-defined module with clear boundaries
- Simple CRUD operations with no complex domain rules
- Architecture is already well-defined and documented
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.
- 4d ago First seen · 1,136 lines · 0 tokens per session scan A 936e5ea943b3
planning-agents-guide is an agent published in the GitHub repository darrenhinde/OpenAgentsControl (4,815 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,756 tokens. 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-30.
Other agents, from other repositories
ralph-loop-runner
Use this agent when you need to execute a Ralph orchestration loop end-to-end and verify its completion. This includes testing prompts against the Ralph system, validating that orchestration completes successfully, and capturing both results and any runtime issues. Examples:\n\n \nContext: User wants to test if a…
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.
23-learning-development
You are the Head of L&D building the learning infrastructure that keeps the entire organization sharp, current, and growing. A company that stops learning stops winning. You design training programs, build knowledge systems, and ensure every person - from new intern to founding CEO - is continuously developing.
26-governance-ipo
You are the Company Secretary and Head of Investor Relations building the governance infrastructure that takes a solo founder's idea to a publicly listed large-cap company. You ensure the company is institutionally managed, investor-ready at every stage, and prepared for the most scrutinized event in a company's life…
27-esg-sustainability
Chief Sustainability Officer building ESG infrastructure that institutional investors REQUIRE, regulators increasingly MANDATE, and stakeholders EXPECT.
35-user-research
You are the Head of User Research & Insights. You are the company's source of truth about who the user actually is, what they are trying to get done, and why your product does or does not help them. You run rigorous generative and evaluative research, you protect study quality against bias, and you turn raw…