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 skills add Xakki/ai-agents-skills --skill roadmapgit clone --depth 1 https://github.com/Xakki/ai-agents-skillsWrote 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/skills/xakki/ai-agents-skills/roadmap)<a href="https://agentmods.dev/skills/xakki/ai-agents-skills/roadmap"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/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/skills/xakki/ai-agents-skills/roadmap"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/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.00165 | $0.03157 |
| Opus 5 | $0.00082 | $0.01579 |
| Sonnet 5 | $0.00033 | $0.00631 |
| Haiku 4.5 | $0.00016 | $0.00316 |
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 9d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap — phased app build
Generate an exhaustive technical roadmap for building a whole application, then execute it autonomously. Detailed enough that an agent can pick up any phase and work it for hours without further clarification.
This is not a high-level strategy doc. It is a delivery blueprint: every phase has concrete tasks, every task is actionable, and the whole order is arranged to build from phase 1 to launch with no backtracking.
When to use
- Kicking off a large new product (after deep-research or from a product brief)
- Turning a fuzzy idea into an executable plan
- Planning a multi-week build spread across many sessions
- Before you say "build it" — the roadmap is what gets executed
Inputs
You need one of:
| Input | Where to get it |
|---|---|
| Deep-research brief | MemPalace (mempalace_search, scoped to the project wing) |
| Product brief | User describes what they want |
| Partially built app | Read CLAUDE.md + IDEA.md/ROADMAP.md + the codebase |
| Competitor to clone/improve | URL or name — analyze it |
If all you're told is "plan a notes app" — that's enough; ask clarifying questions as you go.
Modes
| Mode | Triggers | What it does |
|---|---|---|
plan |
"draft a roadmap", "plan it" | Generates/updates ROADMAP.md (see Generation workflow) |
start |
"start building", "execute the roadmap" | Executes from phase 1, phase by phase, no stops |
resume |
"keep going", "what phase are we on" | Finds the first open phase/task and continues |
status |
"roadmap status", "what's done" | Progress summary by phase |
Generation workflow (plan mode)
1. Pin the vision
Before any technical planning, nail down:
- One sentence: what is it? ("Cloud markdown knowledge workspace for teams and AI agents")
- Who: primary/secondary users, agents?
- Why: what can't existing tools do, what's the gap?
- Constraints: stack, budget, timeline, must-haves?
- What we're NOT building: what's explicitly out of scope?
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.
- 9d ago First seen · 281 lines · 165 tokens per session scan A 757c0d0bb932
roadmap is a skill published in the GitHub repository Xakki/ai-agents-skills (6 stars, last pushed 18d ago), licensed MIT. It adds 165 tokens to every session and 3,157 once invoked, about $0.0008 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-08-31.
Other skills, from other repositories
openpanel
Query self-hosted OpenPanel analytics — funnel counts, unique users, breakdowns by os/country/path, raw events. Use whenever analytics numbers are needed: funnel conversion, visitor counts, event counts over a window, period-over-period deltas, "how many signups/checkouts/sessions", or any /darkflow:analytics-review…
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
chart-rendering
Render governed Kun charts and tables from structured data for trustworthy comparison and lookup.
legal-risk-assessment
Structure legal-risk reviews by issue, rule source, likelihood, impact, evidence, uncertainty, controls, and escalation.