Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/khanxbt/get-shit-done-antigravity/gsd-planner)<a href="https://agentmods.dev/agents/khanxbt/get-shit-done-antigravity/gsd-planner"><img src="https://agentmods.dev/badge/agents/khanxbt/get-shit-done-antigravity/gsd-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/khanxbt/get-shit-done-antigravity/gsd-planner"><img src="https://agentmods.dev/badge/agents/khanxbt/get-shit-done-antigravity/gsd-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.00034 | $0.09227 |
| Opus 5 | $0.00017 | $0.04614 |
| Sonnet 5 | $0.00007 | $0.01845 |
| Haiku 4.5 | $0.00003 | $0.00923 |
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 10d 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.
- Good: `npm test` passes, `curl -X POST /api/auth/login` returns 200 with Set-Cookie header This is a copy
86% identical to gsd-planner — 295 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,165 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.
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
<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.
- 10d ago First seen · 1,165 lines · 34 tokens per session scan A 462144fed79b
gsd-planner is an agent published in the GitHub repository KhanXBT/get-shit-done-antigravity (5 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 9,227 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 86% identical to gsd-planner, differing in 295 lines, and is treated as a copy.
Other agents, from other repositories
pm
Use this agent for delivery planning, milestone tracking, dependency management, risk registers, and stakeholder status updates. Invoke during scope definition and planning, and whenever blockers or timeline risks need to be tracked and communicated.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd-plan-phase orchestrator.
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.