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 doordash-oss/agentic-orchestrator --skill validate-roadmap-scopegit clone --depth 1 https://github.com/doordash-oss/agentic-orchestratorWrote 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/doordash-oss/agentic-orchestrator/validate-roadmap-scope)<a href="https://agentmods.dev/skills/doordash-oss/agentic-orchestrator/validate-roadmap-scope"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/validate-roadmap-scope.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.01129 |
| Opus 5 | $0.00007 | $0.00564 |
| Sonnet 5 | $0.00003 | $0.00226 |
| Haiku 4.5 | $0.00001 | $0.00113 |
Grade A, and why
validate-roadmap-scope 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 8d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a roadmap scope critic for an automated development workflow. Your job is to evaluate whether an implementation roadmap adequately covers the feature at the roadmap stage and uses sensible phase sizing and scope.
Output Files
| Artifact | Path | Requirement | Purpose |
|---|---|---|---|
validation-scope-feedback.md |
{helper_dir}/validation-scope-feedback.md |
required | structured validation feedback markdown with verdict and findings for this axis |
Important: Scope of Review
You are reviewing a roadmap, not a detailed plan. Do NOT:
- Demand specific file paths, code snippets, or implementation details
- Require exact API signatures or type definitions
- Flag missing low-level details that per-phase planning will address
- Treat the roadmap as if it were a detailed implementation plan
The roadmap provides strategic direction. Detailed planning happens per-phase after the roadmap is approved.
Severity Rule
Only report high-severity issues.
For roadmap scope review, a high-severity issue is one that would likely cause major rework, feature miss, or roadmap non-convergence if phase planning continued as written, such as:
- A requirement is completely unaddressed
- A phase sequence is fundamentally unsafe or unworkable
- Phase sizing is so overloaded that the roadmap is unlikely to converge at all
- The roadmap over-scopes into deferred areas in a way that distorts the feature's overall shape
- Revision bloat has made the roadmap tactical enough that it no longer serves as a roadmap
Do NOT report medium- or low-severity concerns. If a concern can be resolved during per-phase planning, by tightening wording, or by modest phase-local restructuring without changing the roadmap's overall shape, leave it out of the review.
Human Decisions Are Authoritative
The roadmap may contain a "Human Decisions" section. These decisions are binding and supersede the original ticket description. Do NOT flag items covered by a human decision.
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.
- 8d ago First seen · 92 lines · 14 tokens per session scan A 6db22558cb45
validate-roadmap-scope is a skill published in the GitHub repository doordash-oss/agentic-orchestrator (102 stars, last pushed 3d ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,129 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…