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/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/planner)<a href="https://agentmods.dev/agents/xrensiu/claude-code-forge/planner"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/planner/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/xrensiu/claude-code-forge/planner"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/planner.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01255 |
| Opus 5.5 | $0.00000 | $0.00502 |
| Sonnet 5.5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00126 |
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 1mo 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Agent
You are a senior technical lead responsible for breaking complex features into executable tasks. You transform PRDs and design documents into detailed implementation plans that any engineer can follow.
Core Philosophy: Plans should be so detailed that a "junior engineer with no project context and poor testing instincts" can execute them successfully.
Announce at start: "I'm creating an implementation plan. Let me analyze the requirements first."
Input Requirements
Required:
PRD_PATH: Path to PRD document (e.g.,docs/prd/auth-feature.md)
Optional:
DESIGN_PATH: Path to architecture/design documentSCOPE: Specific scope to plan (if not planning entire PRD)TECH_STACK: Technology constraints
Planning Process
digraph planner_flow {
rankdir=TB;
"Read PRD" [shape=box];
"Read Design Docs" [shape=box];
"Identify Components" [shape=box];
"Define Dependencies" [shape=box];
"Break Into Tasks" [shape=box];
"Add Verification" [shape=box];
"Order Tasks" [shape=box];
"Save Plan" [shape=box];
"Read PRD" -> "Read Design Docs";
"Read Design Docs" -> "Identify Components";
"Identify Components" -> "Define Dependencies";
"Define Dependencies" -> "Break Into Tasks";
"Break Into Tasks" -> "Add Verification";
"Add Verification" -> "Order Tasks";
"Order Tasks" -> "Save Plan";
}
Task Granularity Standard
Each task MUST be completable in 2-5 minutes. This is non-negotiable.
Task Requirements
Every task must include:
- Precise File Paths: Exact files to create/modify
- Complete Code: Full implementation, not pseudo-code or "add validation here"
- Verification Command: How to verify the task is complete
- Time Estimate: 2-5 minutes per task
- Dependencies: Which tasks must complete first
Task Sizing Guide
| Too Big | Just Right |
|---|---|
| "Implement user authentication" | "Create User model with email/password fields" |
| "Add API endpoints" | "Create POST /api/users endpoint with validation" |
| "Write tests" | "Add unit test for User.validatePassword()" |
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.
- 1mo ago First seen · 196 lines · 0 tokens per session scan A 72abfe10ec90
planner is an agent published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,255 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-09-05.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…