gsd-roadmapper

gsd-roadmapper is an agent for Claude Code from mrmyothet/zach-hair-studio. It costs 36 tokens per session (5,431 once invoked), scanned A, a copy of gsd-roadmapper, MIT.

A roadmap-planning agent that turns project requirements into ordered phases, with each requirement linked to one phase and each phase given measurable success criteria.

In plain words
What is it for?
It helps initialize projects, break work into phases, map requirements, define completion checks, and validate coverage.
Why use it?
It provides a clear delivery structure and checks that requirements are covered instead of leaving planning gaps.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: reads .claude/ paths; mentions AGENTS.md.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/templates/roadmap.md.

Good fit It helps initialize projects, break work into phases, map requirements, define completion checks, and validate coverage.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code.

Wrote 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.

agentmods badge for gsd-roadmapper

README.md
[![agentmods](https://agentmods.dev/badge/agents/mrmyothet/zach-hair-studio/gsd-roadmapper/github.svg)](https://agentmods.dev/agents/mrmyothet/zach-hair-studio/gsd-roadmapper)
Your own site
<a href="https://agentmods.dev/agents/mrmyothet/zach-hair-studio/gsd-roadmapper"><img src="https://agentmods.dev/badge/agents/mrmyothet/zach-hair-studio/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.

agentmods 80×15 button for gsd-roadmapper

Your own site · 80×15
<a href="https://agentmods.dev/agents/mrmyothet/zach-hair-studio/gsd-roadmapper"><img src="https://agentmods.dev/badge/agents/mrmyothet/zach-hair-studio/gsd-roadmapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,431 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.05431
Opus 5 $0.00018 $0.02715
Sonnet 5 $0.00007 $0.01086
Haiku 4.5 $0.00004 $0.00543

Measured 11d ago against content hash f6326ac5ba45, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 11d 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.

Origin

This is a copy

83% identical to gsd-roadmapper — 90 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.

landing-page/.claude/agents/gsd-roadmapper.md · 749 lines

How it starts

The opening of the file, as written. The whole thing — 749 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are spawned by:

  • /gsd-new-project orchestrator (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 .claude/skills/ or .agents/skills/ directory if either exists:

  1. List available skills (subdirectories)
  2. Read SKILL.md for each skill (lightweight index ~130 lines)
  3. Load specific rules/*.md files as needed during implementation
  4. Do NOT load full AGENTS.md files (100KB+ context cost)
  5. 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 + 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

Read the full file on GitHub · 749 lines

Changes

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.

  1. 11d ago First seen · 749 lines · 36 tokens per session scan A f6326ac5ba45

Subscribe to this mod's changes

gsd-roadmapper is an agent published in the GitHub repository mrmyothet/zach-hair-studio (11 stars, last pushed 26d ago), licensed MIT. It adds 36 tokens to every session and 5,431 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to gsd-roadmapper, differing in 90 lines, and is treated as a copy.