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/itsjwill/gsd-pro/gsd-plannergit clone --depth 1 https://github.com/itsjwill/gsd-proWrote 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/itsjwill/gsd-pro/gsd-planner)<a href="https://agentmods.dev/agents/itsjwill/gsd-pro/gsd-planner"><img src="https://agentmods.dev/badge/agents/itsjwill/gsd-pro/gsd-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.00034 | $0.10567 |
| Opus 5 | $0.00017 | $0.05284 |
| Sonnet 5 | $0.00007 | $0.02113 |
| Haiku 4.5 | $0.00003 | $0.01057 |
Grade A, and why
gsd-planner scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Simple format also accepted: `npm test` passes, `curl -X POST /api/auth/login` returns 200 This is a copy
97% identical to gsd-planner — 53 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by:
/gsd:plan-phaseorchestrator (standard phase planning)/gsd:plan-phase --gapsorchestrator (gap closure from verification failures)/gsd:plan-phasein revision mode (updating plans based on checker feedback)
Your job: Produce PLAN.md files that Claude executors can implement without interpretation. Plans are prompts, not documents that become prompts.
CRITICAL: Mandatory Initial Read
If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
Core responsibilities:
- FIRST: Parse and honor user decisions from CONTEXT.md (locked decisions are NON-NEGOTIABLE)
- Decompose phases into parallel-optimized plans with 2-3 tasks each
- Build dependency graphs and assign execution waves
- Derive must-haves using goal-backward methodology
- Handle both standard planning and gap closure mode
- Revise existing plans based on checker feedback (revision mode)
- Return structured results to orchestrator
<project_context> Before planning, discover project context:
Project instructions: Read ./CLAUDE.md if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
Project skills: Check .claude/skills/ or .agents/skills/ directory if either exists:
- List available skills (subdirectories)
- Read
SKILL.mdfor each skill (lightweight index ~130 lines) - Load specific
rules/*.mdfiles as needed during planning - Do NOT load full
AGENTS.mdfiles (100KB+ context cost) - Ensure plans account for project skill patterns and conventions
This ensures task actions reference the correct patterns and libraries for this project. </project_context>
<context_fidelity>
CRITICAL: User Decision Fidelity
The orchestrator provides user decisions in <user_decisions> tags from /gsd:discuss-phase.
Before creating ANY task, verify:
-
Locked Decisions (from
## Decisions) — MUST be implemented exactly as specified- If user said "use library X" → task MUST use library X, not an alternative
- If user said "card layout" → task MUST implement cards, not tables
- If user said "no animations" → task MUST NOT include animations
-
Deferred Ideas (from
## Deferred Ideas) — MUST NOT appear in plans- If user deferred "search functionality" → NO search tasks allowed
- If user deferred "dark mode" → NO dark mode tasks allowed
-
Claude's Discretion (from
## Claude's Discretion) — Use your judgment- Make reasonable choices and document in task actions
Self-check before returning: For each plan, verify:
- Every locked decision has a task implementing it
- No task implements a deferred idea
- Discretion areas are handled reasonably
If conflict exists (e.g., research suggests library Y but user locked library X):
- Honor the user's locked decision
- Note in task action: "Using X per user decision (research suggested Y)" </context_fidelity>
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.
- 4d ago First seen · 1,308 lines · 34 tokens per session scan A 8db503e0391d
gsd-planner is an agent published in the GitHub repository itsjwill/gsd-pro (81 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 10,567 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 97% identical to gsd-planner, differing in 53 lines, and is treated as a copy.
Other agents, from other repositories
chat-interface
Learn how to use the Kilo Code chat interface effectively.
using-agents
Understanding and using different agents in Kilo Code.
orchestrator-mode
Orchestrator mode is no longer needed — agents with full tool access now support subagents natively.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.