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 davekilleen/Dex --skill roadmapgit clone --depth 1 https://github.com/davekilleen/DexWrote 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/davekilleen/dex/roadmap)<a href="https://agentmods.dev/skills/davekilleen/dex/roadmap"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/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/davekilleen/dex/roadmap"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/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.00014 | $0.01345 |
| Opus 5.5 | $0.00006 | $0.00538 |
| Sonnet 5.5 | $0.00003 | $0.00269 |
| Haiku 4.5 | $0.00001 | $0.00135 |
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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Produce a dated, source-backed roadmap review across the confirmed project cohort. Surface explicit blockers, alignment gaps, evidence freshness, and unknown status without inventing an aggregate health judgment.
Usage
/roadmap— review the confirmed roadmap cohort/roadmap [pillar]— filter by an exact configured pillar
Evidence, authority, and recovery
Treat the review as an evidence report, not a projection.
- Use the canonical status source and status date from each project record. Record the path/ID, status date, and review as-of time. Filesystem modified time is only a discovery clue, never a replacement status date.
- Cite source evidence for every status, blocker, milestone, pillar, alignment claim,
and feedback item. If sources contradict, show both source dates and leave the field
Unknown. - Unknown is distinct from blocked. Use
Blockedonly when the canonical source explicitly identifies an unresolved dependency preventing progress. - Define every denominator and disclose excluded projects. If the cohort or status is incomplete, report counts and coverage rather than a percentage or health score.
- Never invent status, dates, blockers, dependencies, milestones, tags, feedback, counts, or health scores.
- Keep analysis read-only. Preview requested changes, require explicit human authority, read back the target, and fail honestly on any mismatch.
Method
1. Confirm scope
Confirm:
- review as-of date and timezone;
- canonical project locations;
- which project states belong on the roadmap;
- requested pillar filter;
- strategic pillar and quarterly-goal sources;
- review window for stakeholder feedback;
- configured freshness policy, if the user wants freshness labels.
Without a confirmed freshness policy, show the status age but label the assessment
Unknown — no confirmed freshness policy.
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 · 169 lines · 14 tokens per session scan A f5019dd0b8df
roadmap is a skill published in the GitHub repository davekilleen/Dex (508 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 1,345 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-09-02.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…