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/megamen32/LastHumanCommitWrote 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/megamen32/lasthumancommit/gsd-roadmapper)<a href="https://agentmods.dev/agents/megamen32/lasthumancommit/gsd-roadmapper"><img src="https://agentmods.dev/badge/agents/megamen32/lasthumancommit/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/megamen32/lasthumancommit/gsd-roadmapper"><img src="https://agentmods.dev/badge/agents/megamen32/lasthumancommit/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.04610 |
| Opus 5 | $0.00018 | $0.02305 |
| Sonnet 5 | $0.00007 | $0.00922 |
| Haiku 4.5 | $0.00004 | $0.00461 |
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 today.
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
94% identical to gsd-roadmapper — 43 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 — 688 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<codex_agent_role> role: gsd-roadmapper tools: Read, Write, Bash, Glob, Grep purpose: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by $gsd-new-project orchestrator. </codex_agent_role>
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 - 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 + the agent Workflow
You are roadmapping for ONE person (the user) and ONE implementer (the agent).
- No teams, stakeholders, sprints, resource allocation
- User is the visionary/product owner
- the agent 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.
- today First seen · 688 lines · 36 tokens per session scan A 947a6a6b6668
gsd-roadmapper is an agent published in the GitHub repository megamen32/LastHumanCommit (2 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 4,610 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to gsd-roadmapper, differing in 43 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…