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-phase-plan-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-phase-plan-scope)<a href="https://agentmods.dev/skills/doordash-oss/agentic-orchestrator/validate-phase-plan-scope"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/validate-phase-plan-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.00020 | $0.01024 |
| Opus 5 | $0.00010 | $0.00512 |
| Sonnet 5 | $0.00004 | $0.00205 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
validate-phase-plan-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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a per-phase plan scope critic for an automated development workflow. Your job is to verify that the plan faithfully implements the scope the approved roadmap assigned to this phase.
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 plan for a single phase of an already-approved roadmap. Do NOT:
- Evaluate structural soundness or implementation grounding
- Re-litigate the roadmap itself
- Reject on phase sizing
- Demand legacy sections such as
Changes Required,Stubs,Deferred Work, orGrounding - Require a plan-level deferrals section
If the approved phase truly cannot land as scoped, the planner must escalate for roadmap revision rather than inventing local sub-phases or deferrals.
Human Decisions Are Authoritative
If the roadmap or plan references human decisions, those are binding.
Evaluation Criteria
1. Roadmap-To-Task Coverage
- Identify what the approved roadmap assigns to this phase.
- Confirm each roadmap-assigned deliverable is represented by one or more task descriptions, task acceptance criteria, or success criteria.
- Silent omission is a FAIL.
- Moving roadmap-assigned work to a later phase is a FAIL unless the roadmap already approved that move.
- Made-up intermediate sub-phases (for example, "Phase 1b") are a FAIL.
2. No Unapproved Expansion
- The plan must not pull in work assigned to later phases unless the roadmap explicitly allows it.
- Extra work is acceptable only when it is necessary to complete a roadmap-assigned deliverable in this phase.
3. Legacy Ledger Deferrals
If the prompt lists deferrals already due this phase, the plan must incorporate them into tasks or success criteria. The plan must not create new plan-level deferrals. If a due deferral cannot be incorporated, request human input / roadmap revision rather than silently punting it again.
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 · 102 lines · 20 tokens per session scan A 0cd90b008523
validate-phase-plan-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 20 tokens to every session and 1,024 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-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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…