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/keychain-io/trustable-ai/roadmap-planninggit clone --depth 1 https://github.com/keychain-io/trustable-aiWrote 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/commands/keychain-io/trustable-ai/roadmap-planning)<a href="https://agentmods.dev/commands/keychain-io/trustable-ai/roadmap-planning"><img src="https://agentmods.dev/badge/commands/keychain-io/trustable-ai/roadmap-planning.svg" alt="Measured on agentmods" 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.00000 | $0.04456 |
| Opus 5 | $0.00000 | $0.02228 |
| Sonnet 5 | $0.00000 | $0.00891 |
| Haiku 4.5 | $0.00000 | $0.00446 |
Grade A, and why
roadmap-planning 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 5d 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 — 577 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Roadmap Planning Workflow
⚠️ DEPRECATED: This workflow has been renamed to /architecture-planning (v2.0.0)
Reason: The name "roadmap-planning" suggested business roadmap/product timeline planning, but the workflow actually focuses on technical architecture. The new name /architecture-planning better reflects its purpose: designing system architecture, validating technology choices, and documenting technical decisions.
Migration: Use /architecture-planning instead. This workflow will be removed in v3.0.0.
Project: trusted-ai-development-workbench Workflow: Product Roadmap Planning (DEPRECATED) Purpose: Transform business strategy into Epics that define what we're building
Output Formatting Requirements
IMPORTANT: Use actual Unicode emojis in reports, NOT GitHub-style shortcodes:
- :dart: Strategic goal | :trophy: Key result | :compass: Initiative
- :calendar: Quarterly | :date: Monthly | :soon: Near-term
- :moneybag: Revenue | :busts_in_silhouette: Users | :chart_with_upwards_trend: Growth
Where This Fits
┌─────────────────────────────────────────────────────────────────────────────┐
│ SOFTWARE LIFECYCLE - UPSTREAM WORKFLOWS │
│ │
│ ══════════════════ │
│ YOU ARE HERE: /roadmap-planning │
│ ══════════════════ │
│ │ │
│ │ Input: Business strategy, OKRs, market research │
│ │ Output: Epics in azure-devops │
│ ▼ │
│ /backlog-grooming │
│ │ Decomposes Epics into Features and Tasks │
│ │ Refines work items, assigns business value │
│ ▼ │
│ /sprint-planning │
│ │ Selects Features/Tasks for sprint │
│ ▼ │
│ /feature-implementation │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
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.
- 5d ago First seen · 577 lines · 0 tokens per session scan A ad6f8cf855e7
roadmap-planning is a command published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,456 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-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.