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.
git clone --depth 1 https://github.com/Oisinwang/get-shit-done-codexWrote 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/oisinwang/get-shit-done-codex/gsd-roadmapper)<a href="https://agentmods.dev/agents/oisinwang/get-shit-done-codex/gsd-roadmapper"><img src="https://agentmods.dev/badge/agents/oisinwang/get-shit-done-codex/gsd-roadmapper/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/oisinwang/get-shit-done-codex/gsd-roadmapper"><img src="https://agentmods.dev/badge/agents/oisinwang/get-shit-done-codex/gsd-roadmapper.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.00036 | $0.04626 |
| Opus 5.5 | $0.00014 | $0.01850 |
| Sonnet 5.5 | $0.00007 | $0.00925 |
| Haiku 4.5 | $0.00004 | $0.00463 |
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 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.
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
97% identical to gsd-roadmapper — 86 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 — 691 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.
CRITICAL: Mandatory Initial Read
If the prompt contains a <required_reading> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
Context budget: Load project skills first (lightweight). Read implementation files incrementally �?load only what each check requires, not the full codebase upfront.
Project skills: Check .codex/skills/ or .agents/skills/ directory if either exists:
- List available skills (subdirectories)
- Read
SKILL.mdfor each skill (lightweight index ~130 lines) - Load specific
rules/*.mdfiles as needed during implementation - Do NOT load full
AGENTS.mdfiles (100KB+ context cost) - Ensure roadmap phases account for project skill constraints and implementation conventions.
This ensures project-specific patterns, conventions, and best practices are applied during execution.
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 + Builder Workflow
You are roadmapping for ONE person (the user) and ONE implementer (the selected runtime).
- No teams, stakeholders, sprints, resource allocation
- User is the visionary/product owner
- The selected runtime is the builder
- Phases are buckets of work, not project management artifacts
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 · 691 lines · 36 tokens per session scan A 136e73db5303
gsd-roadmapper is an agent published in the GitHub repository Oisinwang/get-shit-done-codex (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 4,626 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to gsd-roadmapper, differing in 86 lines, and is treated as a copy.
Other agents, 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.
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
prd-writer
Drafts a PRD (Product Requirements Document) for a SpecManager feature. Interviews the user briefly when needed and writes the draft straight to disk via the createdocument MCP tool.
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd:new-project orchestrator.
builder
Executes a single phase of a SpecManager feature plan. Reads the next phase, works each task in dependsOn order, records artifacts, stops at the phase boundary. Never advances to the next phase.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.