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/nicepkg/ai-workflow/roadmapnpx skills add nicepkg/ai-workflow --skill roadmapgit clone --depth 1 https://github.com/nicepkg/ai-workflowWrote 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/nicepkg/ai-workflow/roadmap)<a href="https://agentmods.dev/skills/nicepkg/ai-workflow/roadmap"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/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 | $0.00034 | $0.02385 |
| Opus 5 | $0.00017 | $0.01192 |
| Sonnet 5 | $0.00007 | $0.00477 |
| Haiku 4.5 | $0.00003 | $0.00238 |
Grade A, and why
roadmap-prioritization-planning 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 yesterday.
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 — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap & Prioritization Skill
Master the art of saying "no". Create focused roadmaps that align your organization, drive strategic outcomes, and maximize impact with limited resources.
RICE Scoring System (Complete)
Formula
RICE Score = (Reach × Impact × Confidence) / Effort
Reach: How many users affected? (1-100+)
- 10+ = 10
- 100+ = 100
- 1000+ = 1000
Impact: Per-user impact (3, 2, 1, 0.5)
- 3 = Massive (10x improvement)
- 2 = High (significant improvement)
- 1 = Medium (noticeable improvement)
- 0.5 = Low (minor improvement)
Confidence: How confident? (0.25-1.0)
- 1.0 = High (research backed)
- 0.8 = Medium (some validation)
- 0.5 = Low (minimal validation)
- 0.25 = Very low (assumption)
Effort: Engineer-weeks needed (1-20+)
Scoring Example Matrix
Feature Reach Impact Confidence Effort RICE Score
────────────────────────────────────────────────────────
User Onboarding 50 3 0.8 8 (50×3×0.8)/8 = 15.0
Dark Mode 200 1 0.9 4 (200×1×0.9)/4 = 45.0
API Limits 500 2 0.7 10 (500×2×0.7)/10 = 70.0
Performance Fix 1000 0.5 1.0 5 (1000×0.5×1)/5 = 100.0
Custom Fields 30 3 0.6 12 (30×3×0.6)/12 = 4.5
PRIORITIZE: Performance > API Limits > Dark Mode > Onboarding > Custom Fields
RICE Confidence Levels
High (1.0) - Research-backed
- Customer interviews conducted
- Data from analytics
- Customer support tickets confirming
- Clear customer demand
Medium (0.8) - Some validation
- Logical assumption
- One or two customers requesting
- Industry trends suggest it
- Similar features successful elsewhere
Low (0.5) - Minimal validation
- Educated guess
- Competitive pressure (they have it)
- Opportunity emerged
- Needs deeper validation
Very Low (0.25) - Pure assumption
- "Seems like good idea"
- No customer feedback
- No validation whatsoever
- High risk of waste
Alternative Prioritization Methods
Value vs Effort Matrix
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 395 lines · 34 tokens per session scan A 7850091e4924
roadmap-prioritization-planning is a skill published in the GitHub repository nicepkg/ai-workflow (283 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 2,385 once invoked, about $0.0002 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-03.
Other skills, from other repositories
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…
triage
Triage open herdr GitHub issues into a concise decision-first Markdown table. Use when the user says "triage", asks to triage open issues, asks which issues need attention, or wants issue priority/recommendation lights for herdr.
backlog-technical-project-manager
Technical project management for Backlog.md workstreams using coordinated sub-agents. Use only when the user explicitly asks Codex to take over one or more existing Backlog.md tasks (for example: "act as TPM", "coordinate these tasks", "delegate to sub-agents"). Orchestrate planning, implementation, and finalization…
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
devloop
Goal-driven development loop — define objective, write rules with key-results, verify visually, sync to issue tracker.