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/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/doordash-oss/agentic-orchestrator/validate-roadmap-scope"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/validate-roadmap-scope.svg" alt="Reviewed on agentmods" width="80" 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.5 | $0.00006 | $0.00452 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (117 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 1,129 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-08-30.
Other skills, from other repositories
plan-pm
Principal PM skill — the autonomous PRD writer. Consumes a graded, fleshed-out row from the INTAKE.md backlog (idea, goal, type, grade) and drafts the full PRD solo — feature/acceptance table, edge cases, error handling — saved to features/planned/prd-[n]-[feature-slug]/. The requirements interview lives in /intake…
pre-merge
The quality gate. Takes a feature branch from "eng says done" to "checked, fixed and ready for /merge". Runs the project's preflight-resolved pipeline from devkit/policy.json components[]: sync → parallel correctness + security waves → coverage → regression tail → security/migration → PRD-consistency → verdict. A…
msg
Root menu for msg skills, plus harness modes. Bare /msg says the next step for each PRD in progress and offers to run it — use it when the user says "what's next", "where am I", "what should I run now". --init is the project setup — use it when the user says "initialise project", "bootstrap repo", "set up the…
plan-em
Engineering Manager skill. Reads an approved PRD, runs pre-flight checks against AHA.md, GLOSSARY.md and ARCHITECTURE.md, auto-runs plan-review certification inline (no ask), picks the specialist agents (it asks to approve the roster only when the roster is unusual for the project), spins them up to write engineering…
intake
The planning front-door. Captures feature ideas and bugs as graded rows in the root INTAKE.md ledger. Use it when the user says "log an idea", "capture a bug", "add to the backlog", "note this down", "track this feature", or invokes /intake. Opens with one prompt ("What are you trying to build?"), infers the rest from…
emulate
Runs this repo's app on a local simulator or emulator and opens the window on the user's desktop. Use it when the user says "run the app", "open the simulator", "launch the emulator", "boot the iOS sim", "start Expo", "see it running", "show me the app", or invokes /emulate. Takes the branch the user is standing on…