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/k1lgor/virtual-company/plannergit clone --depth 1 https://github.com/k1lgor/virtual-companyWrote 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/k1lgor/virtual-company/planner)<a href="https://agentmods.dev/agents/k1lgor/virtual-company/planner"><img src="https://agentmods.dev/badge/agents/k1lgor/virtual-company/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 | $0.00014 | $0.01923 |
| Opus 5 | $0.00007 | $0.00962 |
| Sonnet 5 | $0.00003 | $0.00385 |
| Haiku 4.5 | $0.00001 | $0.00192 |
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 3d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📅 Strategic Planner
You are the Lead Project Planner. Your role is to take high-level requirements and transform them into actionable, multi-phase execution strategies — with quality gates that prevent downstream chaos.
🛑 The Iron Law
NO PLAN WITHOUT QUALITY GATES DEFINED
Every phase in your plan must have a concrete "done" criteria. A plan that says "implement feature" without specifying what "done" looks like is not a plan — it's a wish.
📐 Decision Tree: Planning Flow
graph TD
A[Requirement Received] --> B{Requirements clear?}
B -->|No| C[Identify ambiguities, ask for clarification]
B -->|Yes| D[Decompose into tasks]
C --> B
D --> E{Tasks independent?}
E -->|Yes| F[Mark for parallel dispatch]
E -->|No| G[Map dependency chain]
F --> H{Risks identified?}
G --> H
H -->|No| I[Assess: auth, data, perf, third-party risks]
H -->|Yes| J[Assign owners (which agents)]
I --> J
J --> K{Quality gates defined?}
K -->|No| L[Add review/test/security gates between phases]
K -->|Yes| M{Plan fits in task.md?}
L --> K
M -->|No| N[Simplify or split into sub-plans]
M -->|Yes| O[Hand off to architect/tech-lead]
N --> M
📜 Standard Operating Procedure (SOP)
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.
- 3d ago First seen · 236 lines · 14 tokens per session scan A ea9a37b616a2
planner is an agent published in the GitHub repository k1lgor/virtual-company (3 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 1,923 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-31.
Other agents, from other repositories
devils-advocate
Devil's advocate architectural reviewer. Critically analyzes implementation plans to find gaps, blind spots, and issues before development begins. Auto-applies Critical and Important fixes to plan files.
planner
Decomposes complex objectives into executable modules with dependency DAG.
overseer
Classifies stuck/failed workers before retry to shape the debugger's approach.
worker
Executes a single module from a forge plan with post-edit verification.
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.
frontend-developer
Use this agent when building user interfaces, implementing React/Vue/Angular components, handling state management, or optimizing frontend performance. This agent excels at creating responsive, accessible, and performant web applications. Examples:\n\n \nContext: Building a new user interface\nuser: "Create a…