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/jnPiyush/AgentXWrote 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/jnpiyush/agentx/roadmap-gen)<a href="https://agentmods.dev/commands/jnpiyush/agentx/roadmap-gen"><img src="https://agentmods.dev/badge/commands/jnpiyush/agentx/roadmap-gen.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.00021 | $0.00580 |
| Opus 5 | $0.00010 | $0.00290 |
| Sonnet 5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
Roadmap Generation 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Generation Prompt
Context
You are a Product Manager agent generating a shared roadmap for Epic #{{issue_number}}.
Before drafting, read these files first:
.github/templates/ROADMAP-TEMPLATE.md- related PRDs under
docs/artifacts/prd/ - any relevant ADR, UX, or execution-plan artifacts that establish delivery constraints
When to Use This Prompt
Use this prompt when one or more of these are true:
- the epic spans multiple workstreams, products, or business domains
- several PRDs need one shared milestone and release plan
- the user explicitly asks for a roadmap, release plan, portfolio calendar, or planning wave view
- UAT, pilot go-live, and later release waves need one coordinated schedule
Instructions
1. Analyze the Planning Scope
- Read the epic description and related PRDs thoroughly
- Identify the workstreams that need to be coordinated
- Determine whether the roadmap is MVP-only, annual, or multi-wave
- Capture shared dependencies, release gates, and operational readiness expectations
2. Build the Roadmap Structure
Using .github/templates/ROADMAP-TEMPLATE.md, populate:
- portfolio purpose and planning assumptions
- portfolio planning rules
- dated MVP sprint calendar and gate dates
- dated release plan with release owners and readiness statuses
- capability waves and planning workshops
- cross-workstream dependencies
- milestone timeline for the planning horizon
- Mermaid visuals for gantt, milestone sequence, and MVP release shape
- quality gates, release readiness, rollback, and hypercare expectations
- workstream mapping by release wave
3. File Naming Guidance
- If the workspace already uses semantic artifact names, preserve that pattern
- Otherwise create the roadmap at
docs/artifacts/prd/ROADMAP-{{issue_number}}.md - Link all related PRDs in the roadmap header
4. Quality Checklist
- Scope covers the full portfolio or multi-workstream release surface
- Sprint and release dates are explicit and internally consistent
- Shared dependencies are called out, not buried in PRDs
- Release readiness and hypercare expectations are operationally clear
- Milestones, waves, and workshops tell one coherent planning story
- Mermaid diagrams match the dates and sequencing in the tables
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 · 69 lines · 21 tokens per session scan A e9c2798d5497
Roadmap Generation is a command published in the GitHub repository jnPiyush/AgentX (15 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 580 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-09-06.
Other commands, from other repositories
deploy-release
Prepare and verify a staged or production deployment with rollback and smoke checks.
publish-notes
Draft user-facing release notes, store changelogs, and internal publish summaries.
traceability-audit
Map requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.
validate-data
Validate or fetch a market dataset before mining.
undo
Undo a change to your book by reverting a commit from its git history.
codex-loop
Claim the next dispatch:codex issue from the GitHub queue and work it end-to-end through codex exec: branch, implement, QA, PR. One invocation handles exactly one task — a local pull loop you trigger, not a daemon. The board/label safety model is identical to /loop; only the engine differs (the local Codex CLI instead…