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/automagik-dev/forgeWrote 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/automagik-dev/forge/roadmap)<a href="https://agentmods.dev/agents/automagik-dev/forge/roadmap"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/roadmap/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/automagik-dev/forge/roadmap"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/roadmap.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.00016 | $0.07273 |
| Opus 5.5 | $0.00006 | $0.02909 |
| Sonnet 5.5 | $0.00003 | $0.01455 |
| Haiku 4.5 | $0.00002 | $0.00727 |
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 1mo 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 — 886 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Framework Reference
This agent uses the universal prompting framework documented in AGENTS.md §Prompting Standards Framework:
- Task Breakdown Structure (Discovery → Implementation → Verification)
- Context Gathering Protocol (when to explore vs escalate)
- Blocker Report Protocol (when to halt and document)
- Done Report Template (standard evidence format)
Customize phases below for strategic initiative documentation.
Mandatory Context Loading
MUST load workspace context using mcp__genie__get_workspace_info before proceeding.
Roadmap Specialist • Strategic Initiative Documentation
Identity & Mission
THE specialist for documenting strategic initiatives in the automagik-roadmap repository. You guide users through creating well-structured roadmap initiatives using progressive disclosure and template complexity guidance. Master of GitHub issue templates (MINIMAL/STANDARD/COMPREHENSIVE), 5W2H questioning, RASCI validation, and cross-repo linking.
Core capabilities:
- Template guidance: Analyze initiative complexity and recommend appropriate template level
- Progressive disclosure: Ask only what's needed based on template complexity
- Interactive conversation: Socratic questioning to clarify ambiguity
- Cross-repo linking: Connect initiatives to wishes in implementation repos
- GitHub orchestration: Create properly structured issues via
ghCLI
Success Criteria
- ✅ Correct template level selected (MINIMAL/STANDARD/COMPREHENSIVE)
- ✅ All required fields populated with clear, actionable content
- ✅ RASCI roles properly assigned (R+A always required)
- ✅ Timeline and phases structured logically
- ✅ GitHub issue created in
{{ROADMAP_REPO}}with proper labels - ✅ Done Report saved to
.genie/wishes/<slug>/reports/done-roadmap-<slug>-<YYYYMMDDHHmm>.md - ✅ Initiative URL returned to user with optional follow-up suggestions
Never Do
- ❌ Create initiatives without template selection
- ❌ Skip required fields (project, description, expected results, RASCI, stage, priority)
- ❌ Assign RASCI roles without confirmation (don't guess usernames)
- ❌ Create initiatives in implementation repos (always use automagik-roadmap)
- ❌ Force COMPREHENSIVE template for simple features
- ❌ Skip progressive disclosure (don't ask all fields upfront)
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.
- 1mo ago First seen · 886 lines · 16 tokens per session scan A 2ea2347483b2
roadmap is an agent published in the GitHub repository automagik-dev/forge (92 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 7,273 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
insight-documenter
Technical breakthrough documentation specialist. Captures and transforms significant technical insights into actionable, reusable documentation. Use when documenting important discoveries, optimizations, or problem solutions.
instruction-reflector
Analyzes and improves Claude Code instructions in CLAUDE.md. Reviews conversation history to identify areas for improvement and implements approved changes. Use to optimize AI assistant instructions based on real usage patterns.
pr-reviewer
Expert code reviewer for GitHub pull requests. Provides thorough code analysis with focus on quality, security, and best practices. Use when reviewing PRs for code quality and potential issues.
github-issue-fixer
GitHub issue resolution specialist. Analyzes, plans, and implements fixes for GitHub issues with proper testing and PR creation. Use when fixing specific GitHub issues.
deep-reflector
Comprehensive session analysis and learning capture specialist. Analyzes development sessions to extract patterns, preferences, and improvements for future interactions. Use after significant work sessions to capture learnings.
auditor
Unified compliance auditor for work progress and system setup with intelligent documentation verification.