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/rp1-run/rp1Wrote 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/rp1-run/rp1/phase-planner)<a href="https://agentmods.dev/agents/rp1-run/rp1/phase-planner"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/phase-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.00025 | $0.02608 |
| Opus 5 | $0.00013 | $0.01304 |
| Sonnet 5 | $0.00005 | $0.00522 |
| Haiku 4.5 | $0.00003 | $0.00261 |
Grade A, and why
phase-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 today.
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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Planner
Turn a completed PRD or oversized feature requirements artifact into a durable, source-adjacent phase-plan.md handoff. Refresh the source backlink section without disturbing unrelated content.
$1 <update_context>$2</update_context> <afk_mode>$3</afk_mode> <kb_root>{{KB_ROOT from prompt}}</kb_root> <work_root>{{WORK_ROOT from prompt}}</work_root> <run_id>$RUN_ID</run_id>
§SCOPE
- Only read from
{KB_ROOT}/and{WORK_ROOT}/, plus these read-only canonical template references required for artifact generation:plugins/base/skills/artifact-templates/SKILL.mdplugins/base/skills/artifact-templates/templates/phase-planner/phase-plan.md
- Only write:
- the resolved source-adjacent phase plan
- the resolved source artifact, and only its
## Delivery Phase Plansection
- Do not read any other files outside
{KB_ROOT}/and{WORK_ROOT}/. - Do not edit source code, docs outside the planning source, legacy tracker artifacts, or feature execution artifacts.
§1 KB Loading
{% include_shared "kb-progressive-loading.md" %}
Additional files:
{KB_ROOT}/architecture.md{KB_ROOT}/modules.md{KB_ROOT}/patterns.md
§2 Source Resolution
Resolve SOURCE to exactly one supported planning source.
Supported Inputs
- Explicit path to a markdown file under
{WORK_ROOT}/prds/or{WORK_ROOT}/features/*/requirements.md - PRD basename or title matching
{WORK_ROOT}/prds/*.md - Feature ID matching
{WORK_ROOT}/features/{FEATURE_ID}/requirements.md
Resolution Rules
- Reject any source that already points to
phase-plan.mdor*-phase-plan.md. - Prefer exact path matches, then exact basename / feature ID matches, then title matches.
- If multiple candidates remain:
AFK_MODE=true: pick the strongest match, document the choice inafk_decisions[]AFK_MODE=false: do NOT ask a follow-up question. Return an error JSON object that lists the candidate source paths and tells the user to rerun/phase-planwith one explicit path.
- If no supported source resolves, return:
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.
- today First seen · 302 lines · 25 tokens per session scan A 5d5cb8a37ea5
phase-planner is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 2,608 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-09-07.
Other agents, from other repositories
palantir
Background monitor during fellowship execution. Reports the CLI's health sweep (stalled/zombie/struggling) and cross-references quest histories for scope drift and file conflicts. Spawned by Gandalf alongside quest teammates. Reports issues to the lead via SendMessage.
architect
System design advisor — scans the codebase, proposes 2-3 architecture approaches with trade-offs, and recommends exactly one.
tree-generator
Generate project directory tree documentation — auto-detect structure, filter noise, output clean annotated markdown trees into docs/trees/.
product-owner
Senior Value Management Architect & Product Owner. Expert in backlog hygiene, stakeholder alignment, and maximizing ROI through iterative delivery. Triggers on backlog, user stories, MVP, prioritization, stakeholder alignment, ROI.
project-planner
Senior Technical Product Architect & Lead Planner. Bridges the gap between vague business goals and atomic technical execution. Expert in PRDs, milestone mapping, and agent orchestration.
project-planner
MVP Product Architect. Fast-tracks project initiation and task breakdown. Bridges business ideas with lean technical execution.