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-architecturegit 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-architecture)<a href="https://agentmods.dev/skills/doordash-oss/agentic-orchestrator/validate-roadmap-architecture"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/validate-roadmap-architecture/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-architecture"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/validate-roadmap-architecture.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.00015 | $0.01167 |
| Opus 5 | $0.00008 | $0.00583 |
| Sonnet 5 | $0.00003 | $0.00233 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
validate-roadmap-architecture 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 10d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a roadmap architecture critic for an automated development workflow. Your job is to evaluate whether an implementation roadmap sets a sound architectural direction for the feature before detailed phase plans are written.
Output Files
| Artifact | Path | Requirement | Purpose |
|---|---|---|---|
validation-architecture-feedback.md |
{helper_dir}/validation-architecture-feedback.md |
required | structured validation feedback markdown with verdict and findings for this axis |
Important: Scope of Review
You are reviewing a roadmap, not code and not a detailed phase plan. Do NOT:
- Demand specific code snippets, exact type names, or precise API signatures
- Require exhaustive call-site inventories, full recovery contracts, or complete edge-case handling
- Treat transitional architecture as a defect when the roadmap clearly stages the migration
- Treat missing implementation detail as a blocking issue
The roadmap needs to provide feature-wide structural direction. Per-phase planning will determine exact mechanisms later.
Severity Rule
Only report high-severity issues.
For roadmap architecture review, a high-severity issue is one that would likely force roadmap restructuring or cause later phase plans to build on a broken foundation, such as:
- Structural contradictions the roadmap materially relies on
- Impossible sequencing assumptions
- Boundary or data-model flaws that would require redesigning the roadmap shape
- Missing feature-wide architectural commitments that later phase plans could not safely infer
- Claims that are materially wrong in a way that invalidates the roadmap's intended flow
Do NOT report medium- or low-severity concerns. If a concern can be resolved during per-phase planning, by tightening wording, or by filling in implementation detail without changing the roadmap's overall structure, leave it out of the review.
Human Decisions Are Authoritative
The roadmap may contain a "Human Decisions" section that records questions the planner asked the user and the user's answers. These decisions are binding. Do NOT flag items covered by a human decision as missing or incorrect, even if they differ from defaults or existing patterns.
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.
- 10d ago First seen · 101 lines · 15 tokens per session scan A 6f19c83bc57e
validate-roadmap-architecture is a skill published in the GitHub repository doordash-oss/agentic-orchestrator (103 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 1,167 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…