Borrowing it
Nothing to install: this file belongs to GeoloeG-IsT/agents-reverse-engineer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GeoloeG-IsT/agents-reverse-engineer/main/.claude/agents/gsd-planner.mdgit clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineerWrote 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/geoloeg-ist/agents-reverse-engineer/gsd-planner)<a href="https://agentmods.dev/agents/geoloeg-ist/agents-reverse-engineer/gsd-planner"><img src="https://agentmods.dev/badge/agents/geoloeg-ist/agents-reverse-engineer/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/geoloeg-ist/agents-reverse-engineer/gsd-planner"><img src="https://agentmods.dev/badge/agents/geoloeg-ist/agents-reverse-engineer/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.10328 |
| Opus 5.5 | $0.00014 | $0.04131 |
| Sonnet 5.5 | $0.00007 | $0.02066 |
| Haiku 4.5 | $0.00003 | $0.01033 |
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 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.
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 Copies of this mod
2 near-identical copies found in the catalogue:
- gsd-planner — 100% identical, 4 lines differ
- gsd-planner — 92% identical, 58 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are spawned by:
/gsd:plan-phaseorchestrator (standard phase planning)/gsd:plan-phase --gapsorchestrator (gap closure planning from verification failures)/gsd:plan-phaseorchestrator in 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:
- 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
Solo Developer + Claude Workflow
You are planning for ONE person (the user) and ONE implementer (Claude).
- No teams, stakeholders, ceremonies, coordination overhead
- User is the visionary/product owner
- Claude is the builder
- Estimate effort in Claude execution time, not human dev time
Plans Are Prompts
PLAN.md is NOT a document that gets transformed into a prompt. PLAN.md IS the prompt. It contains:
- Objective (what and why)
- Context (@file references)
- Tasks (with verification criteria)
- Success criteria (measurable)
When planning a phase, you are writing the prompt that will execute it.
Quality Degradation Curve
Claude degrades when it perceives context pressure and enters "completion mode."
| Context Usage | Quality | Claude's State |
|---|---|---|
| 0-30% | PEAK | Thorough, comprehensive |
| 30-50% | GOOD | Confident, solid work |
| 50-70% | DEGRADING | Efficiency mode begins |
| 70%+ | POOR | Rushed, minimal |
The rule: Stop BEFORE quality degrades. Plans should complete within ~50% context.
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 · 1,387 lines · 34 tokens per session scan A 8e2c08d582f5
gsd-planner is an agent published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (22 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 10,328 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
auditor
Quality assurance gate - verifies outputs, detects inconsistencies.
security-reviewer
Reviews a change to agent-context-doctor against its security rules. Use before finishing changes to file reading or writing, report output, or the CLI.
php-reviewer
PHP/Laravel-specific reviewer — SQL injection, mass assignment, CSRF, N+1 Eloquent, auth middleware, type safety, queue idempotency.
incident-commander
Triages production incidents. Stop the bleeding first, root-cause second, prevention third.
data-analyst
Use when: analyzing datasets, creating reports, or identifying trends via statistics and visualization. Do NOT use for: building production data pipelines/ETL code (use a domain expert).
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.