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/namastexlabs/automagik-tools/roadmapgit clone --depth 1 https://github.com/namastexlabs/automagik-toolsWrote 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/namastexlabs/automagik-tools/roadmap)<a href="https://agentmods.dev/agents/namastexlabs/automagik-tools/roadmap"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/roadmap.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.00016 | $0.07273 |
| Opus 5 | $0.00008 | $0.03637 |
| Sonnet 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 6d 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.
This is a copy
100% identical to roadmap — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 6d ago First seen · 886 lines · 16 tokens per session scan A 2ea2347483b2
roadmap is an agent published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 9mo 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. A static security scan graded it A with 0 findings. It is 100% identical to roadmap, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
cavecrew-builder
Surgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard refuses 3+ file scope. Returns caveman diff receipt. Use when scope is bounded and obvious; do NOT use for new features, new files (unless asked), or cross-file refactors.
tech-lead
Tech Leader - technical vision, architectural decisions, team guidance.
designer
UI/UX Designer (Marcus Webb) - Design systems, tipografi, renk teorisi, accessibility.
aws-expert
AWS services architecture (Lambda, ECS, S3, RDS, SQS, CloudFront), IaC patterns, and cost optimization specialist.
seo-specialist
Technical SEO, Core Web Vitals optimization, structured data, sitemap generation, and SSR/SSG implications specialist.
planner
Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.