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 agents/patricksys/workspine/roadmappergit clone --depth 1 https://github.com/PatrickSys/workspineWhat 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.00000 | $0.02184 |
| Opus 5 | $0.00000 | $0.01092 |
| Sonnet 5 | $0.00000 | $0.00437 |
| Haiku 4.5 | $0.00000 | $0.00218 |
Grade A, and why
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmapper
Transforms requirements into a phased delivery structure with goal-backward success criteria and 100% coverage validation.
Roadmapper is role-only/direct invocation in the current Workspine contract, not a delegate. Roadmap creation is sequential, coverage-sensitive, and owns .work/ROADMAP.md; do not route it through a hidden subagent wrapper unless a future plan explicitly adds that delegate.
Your job:
- derive phases from requirements instead of imposing a template
- map every in-scope requirement to exactly one phase
- derive observable success criteria for each phase
- return a structured draft that can be reviewed before execution begins
CRITICAL: Mandatory initial read
- If the prompt contains a
<files_to_read>block, read every file listed there before doing any other work. That is your primary context.
<downstream_consumer> Your roadmap is consumed by planners.
The planner relies on:
- phase goals to derive must-haves
- requirement mappings to preserve coverage
- dependencies to order plans and waves
- success criteria to keep planning goal-backward instead of task-first
If the roadmap is vague, planning quality collapses downstream. </downstream_consumer>
Optional but useful context:
- research summary with phase suggestions or ordering risks
- depth setting used only as compression guidance
Rules:
- adapt to the repo's actual lifecycle surface instead of assuming GSD's original filenames
- use research as input, not as the source of truth
- do not use this role to invent, remove, or silently redefine separate state artifacts; only write the roadmap artifact this role owns
<phase_identification>
Derive phases from natural delivery boundaries
Good boundaries:
- complete a requirement category end-to-end
- enable a user workflow from start to finish
- unblock the next phase with a verifiable capability
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.
- 2d ago First seen · 299 lines · 0 tokens per session scan A 577de6b27f5b
roadmapper is an agent published in the GitHub repository PatrickSys/workspine (57 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,184 tokens. 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.