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 skills/allgpt-co/quickvoice/plannernpx skills add allgpt-co/QuickVoice --skill plannergit clone --depth 1 https://github.com/allgpt-co/QuickVoiceWrote 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/skills/allgpt-co/quickvoice/planner)<a href="https://agentmods.dev/skills/allgpt-co/quickvoice/planner"><img src="https://agentmods.dev/badge/skills/allgpt-co/quickvoice/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.00030 | $0.04733 |
| Opus 5 | $0.00015 | $0.02367 |
| Sonnet 5 | $0.00006 | $0.00947 |
| Haiku 4.5 | $0.00003 | $0.00473 |
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.
- Good: `npm test` passes, `curl -X POST /api/auth/login` returns 200 with Set-Cookie header How it starts
The opening of the file, as written. The whole thing — 561 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSD Planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification.
When to Use
Use this agent when:
- You need to create detailed execution plans for a roadmap phase
- Decomposing a phase into parallel-optimized plans with 2-3 tasks each
- Building dependency graphs and assigning execution waves
- Deriving must-haves using goal-backward methodology
- Handling gap closure mode (from verification failures)
- Revising existing plans based on checker feedback
Core Responsibilities
- Decompose phases into parallel-optimized plans - 2-3 tasks max per plan
- Build dependency graphs - Identify what each task needs and creates
- Assign execution waves - Group independent tasks for parallel execution
- Derive must-haves - Use goal-backward methodology for verification criteria
- Handle gap closure - Create plans to address verification or UAT failures
- Revise existing plans - Make targeted updates based on checker feedback
- Return structured results - Provide clear output to orchestrator
Philosophy
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 |
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 · 561 lines · 30 tokens per session scan A 80808d7ec9cd
gsd-planner is a skill published in the GitHub repository allgpt-co/QuickVoice (491 stars, last pushed 23d ago), licensed MIT. It adds 30 tokens to every session and 4,733 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by plan-phase orchestrator.
lumina-frontend-ui
Build, refine, and debug the React/Vite frontend for Lumina. Use when editing files under client/src or client/package.json, changing chat UX, landing page content, auth flows, routing, theme behavior, markdown rendering, animations, responsive layout, or frontend API wiring.
lumina-agentic-mcp
Work on the Python multi-agent pipeline and MCP client in agenticai. Use when editing files under agenticai/, changing agent orchestration, configuration loading, MCP client connectivity, async execution flow, pipeline startup commands, or cloud deployment wrappers for the Python service.
lumina-backend-api
Implement and debug the Express and TypeScript backend for Lumina. Use when editing files under server/src or server/package.json, changing authentication, conversations, guest flows, chat routes, models, middleware, API contracts, or Gemini and Pinecone service wiring outside the dedicated knowledge-ingestion…
lumina-mcp-server
Develop and maintain the standalone Lumina MCP server. Use when editing files under mcpserver/, adding or modifying tools, resources, prompts, middleware, configuration, or transport behavior for the Model Context Protocol server.
lumina-rag-knowledge
Manage Lumina's retrieval-augmented generation and knowledge ingestion workflow. Use when editing server/src/services/knowledgeBase.ts, server/src/services/pineconeClient.ts, server/src/scripts/knowledgeCli.ts, server/src/models/KnowledgeSource.ts, files under server/knowledge, manifest-based sync inputs, or debugging…