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 skills/abilityai/abilities/roadmapnpx skills add Abilityai/abilities --skill roadmapgit clone --depth 1 https://github.com/Abilityai/abilitiesWhat 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 | $0.00024 | $0.00834 |
| Opus 5 | $0.00012 | $0.00417 |
| Sonnet 5 | $0.00005 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00083 |
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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.roadmap vX.Y — recent: <summary>. Then proceed.
Shows the agent backlog grouped by affected skill rather than by priority. Use this to understand which parts of the agent need the most work, and to choose a sprint focus area. For the day-to-day priority-ordered view, use /backlog.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| GitHub Issues | Current repo | Yes | No | Open issues |
| GitHub Labels | skill:, priority:, status:* | Yes | No | Group and filter |
Process
Step 1: Verify GitHub CLI
gh auth status 2>&1 | head -3
Step 2: Fetch Open Issues
gh issue list --state open --json number,title,labels,updatedAt --limit 100
Step 3: Group by Skill
Parse the skill:* label from each issue. Group issues into buckets:
- One bucket per
skill:<name>label present - A separate bucket for project-level issues (no skill label)
For each bucket, sort issues by priority (p0 → p1 → p2 → unset).
Step 4: Format Output
## Agent Roadmap
### skill:adjust-playbook (3 open)
| # | Title | Priority | Status |
|---|-------|----------|--------|
| 14 | Fix archive flag behavior | p0 | todo |
| 9 | Support batch adjustments | p1 | todo |
| 11 | Better breaking-change detection | p2 | todo |
### skill:work-loop (2 open)
| # | Title | Priority | Status |
|---|-------|----------|--------|
| 6 | Handle blocked issues more gracefully | p1 | todo |
| 3 | Add skill-routing by label | p1 | in-progress |
### skill:groom (1 open)
| # | Title | Priority | Status |
|---|-------|----------|--------|
| 18 | Support bulk priority assignment | p2 | todo |
### Project-level (2 open)
| # | Title | Priority | Status |
|---|-------|----------|--------|
| 1 | Add onboarding checklist to README | p2 | todo |
| 5 | Update plugin.json description | p2 | todo |
---
Total open: 8 issues across 3 skills + project-level
Tip: Run `/groom` to tag untagged issues, or `/claim` to start the highest priority item.
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.
- 2d ago First seen · 105 lines · 24 tokens per session scan A bd307908b52d
roadmap is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. It adds 24 tokens to every session and 834 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-08-30.
Other skills, from other repositories
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.