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/ai-is-gonna/get-tasks-doneWrote 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/ai-is-gonna/get-tasks-done/gtd-roadmapper)<a href="https://agentmods.dev/agents/ai-is-gonna/get-tasks-done/gtd-roadmapper"><img src="https://agentmods.dev/badge/agents/ai-is-gonna/get-tasks-done/gtd-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/ai-is-gonna/get-tasks-done/gtd-roadmapper"><img src="https://agentmods.dev/badge/agents/ai-is-gonna/get-tasks-done/gtd-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.04615 |
| Opus 5 | $0.00018 | $0.02308 |
| Sonnet 5 | $0.00007 | $0.00923 |
| Haiku 4.5 | $0.00004 | $0.00462 |
Grade A, and why
gtd-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 10d 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 — 22 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 — 689 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are spawned by:
/gtd: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 .claude/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 /gtd: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
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.
- 10d ago First seen · 689 lines · 36 tokens per session scan A 273ce07d89d6
gtd-roadmapper is an agent published in the GitHub repository ai-is-gonna/get-tasks-done (9 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 4,615 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to gsd-roadmapper, differing in 22 lines, and is treated as a copy.
Other agents, from other repositories
seo-specialist
Self-sufficient SEO orchestrator on the DrMax harness (.agents/seo/ + seo- CLI). Passport→discovery→strategy→technical/content/off-page→measure. Canonical prompts, evidence-based execution, GIST/CVD/Humanization/Latent Intent/LexAdapt/LinguaForensic 3.9.4. Per-stage routing…
codex-onboarder
DEPRECATED alias for project-onboarder. Use project-onboarder in new dispatches. Same tools and behavior.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
specifications-tracking-specialist
Specialist for maintaining comprehensive and accurate documentation in HISTORY.md and SPECIFICATIONS.md files. Use proactively after any meaningful codebase changes (e.g. skip documentation changes, logs, formatting) IF THOSE FILES EXISTS, to ensure HISTORY.md and SPECIFICATIONS.md documentation remains complete…
backlog-analyzer
Analyzes Linear backlog to identify orphaned issues, incorrect project assignments, missing estimates, stale issues, and potential duplicates. Provides actionable recommendations with confidence scores.
linear-research
Research Linear tickets, cycles, projects, and milestones using Linearis CLI. Optimized for LLM consumption with minimal token usage (1k vs 13k for Linear MCP).