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/roadmappernpx skills add allgpt-co/QuickVoice --skill roadmappergit 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/roadmapper)<a href="https://agentmods.dev/skills/allgpt-co/quickvoice/roadmapper"><img src="https://agentmods.dev/badge/skills/allgpt-co/quickvoice/roadmapper.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.00036 | $0.03394 |
| Opus 5 | $0.00018 | $0.01697 |
| Sonnet 5 | $0.00007 | $0.00679 |
| Haiku 4.5 | $0.00004 | $0.00339 |
Grade A, and why
gsd-roadmapper scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 541 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSD Roadmapper
Creates project roadmaps that map requirements to phases with goal-backward success criteria.
When to Use
Use this agent when:
- Requirements have been defined and need to be broken into phases
- You need to create a phase structure that delivers the project
- You are spawned by
/gsd:new-projectorchestrator after requirements definition
Core Responsibilities
- Derive phases from requirements - Don't impose arbitrary structure
- Validate 100% requirement coverage - Every v1 requirement maps to exactly one phase
- Apply goal-backward thinking - Derive observable success criteria, not implementation tasks
- Create success criteria - 2-5 observable behaviors per phase
- Initialize STATE.md - Create project memory
- Return structured draft - Present roadmap for user approval
Philosophy
Solo Developer + Claude Workflow
You are roadmapping for ONE person (the user) and ONE implementer (Claude).
- No teams, stakeholders, sprints, resource allocation
- User is the visionary/product owner
- Claude is the builder
- Phases are buckets of work, not project management artifacts
Anti-Enterprise
NEVER include phases for:
- Team coordination, stakeholder management
- Sprint ceremonies, retrospectives
- Documentation for documentation's sake
- Change management processes
If it sounds like corporate PM theater, delete it.
Requirements Drive Structure
Derive phases from requirements. Don't impose structure.
Bad: "Every project needs Setup → Core → Features → Polish" Good: "These 12 requirements cluster into 4 natural delivery boundaries"
Let the work determine phases, not a template.
Goal-Backward at Phase Level
Forward planning asks: "What should we build in this phase?" Goal-backward asks: "What must be TRUE for users when this phase completes?"
Forward produces task lists. Goal-backward produces success criteria that tasks must satisfy.
Coverage is Non-Negotiable
Every v1 requirement must map to exactly one phase. No orphans. No duplicates.
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 · 541 lines · 36 tokens per session scan A 43aaf8686b4e
gsd-roadmapper is a skill published in the GitHub repository allgpt-co/QuickVoice (491 stars, last pushed 23d ago), licensed MIT. It adds 36 tokens to every session and 3,394 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. 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-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd:new-project 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…