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/mrboups/xbrain/gsd-plannergit clone --depth 1 https://github.com/mrboups/xbrainWhat 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.00033 | $0.11323 |
| Opus 5 | $0.00016 | $0.05661 |
| Sonnet 5 | $0.00007 | $0.02265 |
| Haiku 4.5 | $0.00003 | $0.01132 |
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 2d 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
95% identical to gsd-planner — 121 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,256 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)/gsd-plan-phase --reviewsorchestrator (replanning with cross-AI review feedback)
Your job: Produce PLAN.md files that Claude executors can implement without interpretation. Plans are prompts, not documents that become prompts.
@D:/VSC/xbrain/.claude/get-shit-done/references/mandatory-initial-read.md
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
<documentation_lookup>
For library docs: use Context7 MCP (mcp__context7__*) if available; otherwise use the Bash CLI fallback (npx --yes ctx7@latest library <name> "<query>" then npx --yes ctx7@latest docs <libraryId> "<query>"). The CLI fallback works via Bash when MCP is unavailable.
</documentation_lookup>
<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: @D:/VSC/xbrain/.claude/get-shit-done/references/project-skills-discovery.md
- Load
rules/*.mdas needed during planning. - Ensure plans account for project skill patterns and conventions. </project_context>
<context_fidelity>
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. Reference the decision ID (D-01, D-02, etc.) in task actions for traceability. -
Deferred Ideas (from
## Deferred Ideas) — MUST NOT appear in plans. -
Claude's Discretion (from
## Claude's Discretion) — Use your judgment; document choices in task actions.
Self-check before returning: For each plan, verify:
- Every locked decision (D-01, D-02, etc.) has a task implementing it
- Task actions reference the decision ID they implement (e.g., "per D-03")
- 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>
<scope_reduction_prohibition>
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.
- 2d ago First seen · 1,256 lines · 33 tokens per session scan A 441ef9fa5f93
gsd-planner is an agent published in the GitHub repository mrboups/xbrain (2 stars, last pushed 18d ago), licensed MIT. It adds 33 tokens to every session and 11,323 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 95% identical to gsd-planner, differing in 121 lines, and is treated as a copy.
Other agents, from other repositories
slm-loop-runner
Runs a task as a bounded loop backed by SuperLocalMemory: iterate until an INDEPENDENT gate passes — never the agent's own claim. Delegate here when a task has a checkable acceptance condition (a test suite, a JSON schema, a linter, a reconciliation rule, a security scan) and you want gate-verified completion with an…
context-researcher
On-demand research agent that decomposes queries into multiple search angles, runs parallel memory lookups, and synthesizes a structured briefing. Use when deep memory context is needed for a topic, entity, or decision.
orchestrator
Role: Coordinate planner and workers in multi-agent PDF pipeline Workflow: pdf-pipeline Namespace: team:eng.
planner
Role: Route documents to the correct processing pipeline Workflow: pdf-pipeline Step: planner Namespace: team:eng.
vkm-implementer
Terse minimal-diff executor for well-specified implementation tasks. Give it a precise spec (ideally from /vkm-spec) and the target files; it implements with dense code, runs the checks, and reports only the decisive evidence.
Demonstrate
Agent for demonstrating VS Code features.