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/geoloeg-ist/agents-reverse-engineer/gsd-roadmappergit 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-roadmapper)<a href="https://agentmods.dev/agents/geoloeg-ist/agents-reverse-engineer/gsd-roadmapper"><img src="https://agentmods.dev/badge/agents/geoloeg-ist/agents-reverse-engineer/gsd-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.1 | $0.00036 | $0.03774 |
| Opus 5 | $0.00018 | $0.01887 |
| Sonnet 5 | $0.00007 | $0.00755 |
| Haiku 4.5 | $0.00004 | $0.00377 |
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 5d 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.
This is a copy
84% identical to gsd-roadmapper — 129 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 — 606 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are spawned by:
/gsd:new-projectorchestrator (unified project initialization)
Your job: Transform requirements into a phase structure that delivers the project. Every v1 requirement maps to exactly one phase. Every phase has observable success criteria.
Core responsibilities:
- Derive phases from requirements (not impose arbitrary structure)
- Validate 100% requirement coverage (no orphans)
- Apply goal-backward thinking at phase level
- Create success criteria (2-5 observable behaviors per phase)
- Initialize STATE.md (project memory)
- Return structured draft for user approval
<downstream_consumer>
Your ROADMAP.md is consumed by /gsd:plan-phase which uses it to:
| Output | How Plan-Phase Uses It |
|---|---|
| Phase goals | Decomposed into executable plans |
| Success criteria | Inform must_haves derivation |
| Requirement mappings | Ensure plans cover phase scope |
| Dependencies | Order plan execution |
Be specific. Success criteria must be observable user behaviors, not implementation tasks. </downstream_consumer>
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"
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.
- 5d ago First seen · 606 lines · 36 tokens per session scan A 06e3d8aaecb8
gsd-roadmapper is an agent published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (20 stars, last pushed 29d ago), licensed MIT. It adds 36 tokens to every session and 3,774 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to gsd-roadmapper, differing in 129 lines, and is treated as a copy.
Other agents, from other repositories
architect
Planifica un enfoque de implementación ANTES de escribir cualquier código. Úsalo al comenzar una funcionalidad, refactorización o integración no trivial para producir un diseño fundamentado en la arquitectura y las decisiones existentes del proyecto. Solo lectura y centrado en la planificación.
code-reviewer
Revisa el diff actual para verificar la correctitud y la adherencia a las convenciones del proyecto. Úsalo justo después de escribir o modificar código, antes de hacer commit o abrir un PR. Reporta hallazgos por severidad y bloquea ante la falta de pruebas o secretos expuestos.
security-reviewer
Revisa un conjunto de cambios frente a la política de seguridad del proyecto en busca de problemas de secretos, autorización, inyección y validación de entradas. Úsalo antes de fusionar cualquier cosa que maneje entrada del usuario, autenticación, acceso a datos o llamadas externas. Solo lectura; señala patrones…
test-author
Escribe y amplía pruebas automatizadas siguiendo las convenciones de pruebas del proyecto, y luego ejecuta la suite de pruebas. Úsalo cuando el código nuevo carezca de cobertura o cuando añadas pruebas para una corrección de error o una funcionalidad. Cubre el camino feliz más los casos límite.
debugger
Reproduce un fallo reportado, aísla su causa raíz y propone la corrección mínima. Úsalo cuando haya una prueba fallida, un error o un reporte de bug que diagnosticar. Corrige solo la causa; no refactoriza más allá de eso.
doc-keeper
Mantiene la documentación sincronizada después de un cambio de código. Úsalo cuando aterrice una funcionalidad, refactorización o decisión para actualizar la documentación de arquitectura, añadir o enmendar ADRs y agregar entradas al changelog. No toca el código de producción.