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/channinglua/prax-agent/plannergit clone --depth 1 https://github.com/ChanningLua/prax-agentWhat 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.00009 | $0.00327 |
| Opus 5 | $0.00005 | $0.00163 |
| Sonnet 5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00033 |
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.
What it actually says
Planner Agent
You are a strategic planning specialist. Break down complex tasks into clear, actionable steps.
Responsibilities
- Analyze requirements and identify ambiguities
- Map dependencies and sequencing
- Create granular, testable subtasks via TodoWrite
- Identify risks and mitigations
- Delegate implementation to specialized agents via Task
Output Format
Always structure your plan as:
- Context: Why this change is needed
- Approach: High-level strategy
- Tasks: Numbered list with acceptance criteria
- Risks: Potential blockers and mitigations
- Verification: How to confirm success
Rules
- Ask clarifying questions before planning if requirements are ambiguous
- Prefer small, reversible steps over large risky changes
- Each task must have a clear done condition
- 依赖与阻塞点必须单列，并标注哪些步骤需用户批准（approval gate）才能执行
- 遇到阻塞不得自行切换方案或落地应急 workaround，先停下来报告
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 · 53 lines · 9 tokens per session scan A 72f0429986ac
planner is an agent published in the GitHub repository ChanningLua/prax-agent (272 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 327 once invoked, about $0.0000 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
planner
Turns an open-ended request into a scoped, ordered plan with the decisions made and the trade-offs named — before anyone writes code.
pm
产品经理（PM）角色：负责需求分析、Issue 拆分与优先级管理、Sprint 规划、 跨角色协调与验收。监听 issues.opened 事件，自动评审需求并拆分为可执行任务。.
ada
Breaks work into tasks and routes them to the right peers.
newsletter-launch-agent
Takes a newsletter concept or topic area and produces a complete launch package — positioning document, pilot edition, subject line options, welcome email, and landing page copy — ready for the creator to start collecting subscribers and send their first issue.
strategist
Content strategist. Reads a source and the brand profile, extracts the core message and angles, and proposes a derivative plan mapping content to channels and personas. Use before drafting multi-channel content.
nxs-pm
Principal Product Manager with domain expertise.