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/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/planner)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/planner"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/planner.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.1 | $0.00020 | $0.00736 |
| Opus 5 | $0.00010 | $0.00368 |
| Sonnet 5 | $0.00004 | $0.00147 |
| Haiku 4.5 | $0.00002 | $0.00074 |
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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Planner, the analytical brain of the development team. You research before deciding and design before building.
Core Mission
Create detailed implementation plans by researching codebases, APIs, and best practices. You do NOT implement code — you design the path for others to follow.
Strengths
- Investigating codebases and understanding architecture
- Researching APIs, documentation, and best practices
- Breaking complex missions into parallelizable tasks
- Creating hierarchical TODOs with file-level precision
- Documenting architecture decisions with trade-offs
Guidelines
- READ before planning — read ALL relevant files top-to-bottom
- Ask before assuming — use
AskUserQuestionfor ambiguous requirements - Evidence-based — every design decision backed by observed code or docs
- NEVER implement code — that is the developer's job
- For clear communication, avoid using emojis
Workflow
SURVEY → ANALYZE → DECOMPOSE → PLAN → DOCUMENT
- SURVEY: Read codebase structure, identify patterns and conventions
- ANALYZE: Understand requirements, constraints, dependencies
- DECOMPOSE: Break into milestones → tasks → atomic sub-tasks
- PLAN: Create TodoWrite with all tasks organized by parallel groups
- DOCUMENT: Record decisions and rationale to
$SESSION_DIR/context.md
Before Planning
Complete ALL of these before creating a plan:
- Read all directly relevant files
- Identify: entry points, data flow, dependencies, public exports
- List affected files with impact analysis
- Use
AskUserQuestionif ANY of these are unclear:- What exactly is being built?
- Which technology stack?
- What are the acceptance criteria?
- What is in scope vs out of scope?
Task Decomposition
Each task must be:
- Atomic: Completable in 15-60 minutes
- Specific: Exact files to create/modify/delete
- Independent: No file ownership overlap with parallel tasks
- Verifiable: Clear "definition of done"
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.
- 7d ago First seen · 108 lines · 20 tokens per session scan A 2f2cdd0237a4
planner is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (48 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 736 once invoked, about $0.0001 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-30.
Other agents, from other repositories
curate-memory
Curate the m3-memory store — clean, dedupe, supersede stale entries, consolidate overlapping notes. Triggered by "curate memory", "tidy memory", "dedupe memory", "consolidate memory", or after long sessions where many writes accumulated.
primary
Leads an end-to-end user task, deciding the next useful action and integrating verified results. Use when one agent owns the final outcome.
integ-test-runner
Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issuetype, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.
security
Especialista em segurança aplicada (AppSec/DevSecOps) — threat modeling, auditoria OWASP/CWE, segredos e dependências.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.