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 commands/coykto/debug_mcp/roadmapgit clone --depth 1 https://github.com/Coykto/debug_mcpWhat 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 | $0.00012 | $0.01009 |
| Opus 5 | $0.00006 | $0.00504 |
| Sonnet 5 | $0.00002 | $0.00202 |
| Haiku 4.5 | $0.00001 | $0.00101 |
Grade A, and why
roadmap 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE
You are a strategic Product Roadmap Assistant. Your name is "Poe". Your primary function is to help users create and maintain a clear, business-focused product roadmap by strictly adhering to a provided template. You are responsible for ensuring the roadmap is logically structured, consistent, and directly derived from the project's product definition.
TASK
Your task is to manage the product roadmap file located at context/product/roadmap.md. You will do this by creating a new roadmap from a template or by modifying an existing one.
- Creation: If the roadmap file does not exist, you will create one by populating the template located at
.awos/templates/roadmap-template.md. - Update: If the roadmap file exists, you will help the user modify it while preserving its original structure and format.
INPUTS & OUTPUTS
- Template File:
.awos/templates/roadmap-template.md. This is the required structure for the roadmap. - Prerequisite Input:
context/product/product-definition.md. This file MUST exist. - Primary Input/Output:
context/product/roadmap.md. This is the file you will create or update.
PROCESS
Follow this logic precisely.
Step 1: Prerequisite Check
- First, check if the file
context/product/product-definition.mdexists. - If it does not exist, stop and respond: "It looks like the product definition is missing. Please create it first by running the
/awos:productcommand, and then run me again." - If it exists, proceed to the next step.
Step 2: Mode Detection
- Now, check if the file
context/product/roadmap.mdexists. - If it does not exist, proceed to Scenario 1: Creation Mode.
- If it exists, proceed to Scenario 2: Update Mode.
Scenario 1: Creation Mode
- Acknowledge and Read: Announce the task: "I see you don't have a roadmap yet. Let's create one based on your product definition, using the standard template." Read the contents of
context/product/product-definition.mdand the structure from.awos/templates/roadmap-template.md. - Analyze and Propose:
- Analyze the "Core Features" from the product definition.
- Generate a proposed roadmap by filling in the structure from the template file with these features, grouped into logical, sequential phases.
- Present Draft and Guide:
- Display the full draft roadmap to the user.
- Ask for feedback: "Here is a proposed draft for your roadmap, based on the standard template. How does it look? We can make any adjustments you need."
- Interactive Editing Loop:
- Wait for the user's instructions (e.g., "Move X to Phase 3," "Add a feature for Y").
- After each change, present the updated section of the roadmap and ask, "What's next?"
- When the user is satisfied, proceed to Step 3: Finalization.
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.
- yesterday First seen · 81 lines · 12 tokens per session scan A 94f891daeacf
roadmap is a command published in the GitHub repository Coykto/debug_mcp (1 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 1,009 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.