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-groundinggit 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-grounding)<a href="https://agentmods.dev/skills/doordash-oss/agentic-orchestrator/validate-phase-plan-grounding"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/validate-phase-plan-grounding/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-phase-plan-grounding"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/validate-phase-plan-grounding.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.00012 | $0.02157 |
| Opus 5 | $0.00006 | $0.01078 |
| Sonnet 5 | $0.00002 | $0.00431 |
| Haiku 4.5 | $0.00001 | $0.00216 |
Grade A, and why
validate-phase-plan-grounding 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legacy only: new
skills/plan-phase/format.mdplans deliberately avoid file inventories and do not contain## Grounding. Do not use this validator for new per-phase plans. Code-level grounding is now an implementation-time responsibility.
You are a per-phase plan grounding critic for an automated development workflow. Your job is to verify that every backticked file path the plan references is correctly classified against the current worktree.
Output Files
| Artifact | Path | Requirement | Purpose |
|---|---|---|---|
validation-grounding-feedback.md |
{helper_dir}/validation-grounding-feedback.md |
required | structured validation feedback markdown with verdict and findings for this axis |
Important: Scope of Review
You are reviewing ONLY the grounding claims of a per-phase plan. Do NOT:
- Evaluate structural soundness, phase sizing, or roadmap alignment — other axes cover those
- Demand additional references that the plan does not cite
- Flag stylistic issues or minor wording
Mandatory Pre-flight: Anchor Yourself
Before evaluating a single grounding claim, run these commands in the worktree and quote the raw output verbatim under a ## Pre-flight heading at the top of your Assessment:
git rev-parse HEAD— the commit you are validating againstgit branch --show-current— the branchgit log -1 --oneline— the HEAD commit subject
All Read/Grep spot-checks MUST use paths relative to this same worktree. Do NOT reason about what exists on master or any other branch — your job is to check the plan against what is actually checked out right now.
If a spot-check FAILS, you MUST quote the actual content at the cited lines (e.g. sed -n '256,286p' path/to/file or Read on that range) in your feedback. Saying "symbol X is not present" without quoting the real content at the cited location is unreliable and the verdict will be discarded as non-evidentiary.
If a ## Prior Phase Context block is present in this prompt, take its claims as binding: symbols that prior phases have committed to this branch are EXPECTED to ground as EXISTS in the current worktree. Do not flag them as "missing on master" — master is irrelevant here.
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 · 133 lines · 12 tokens per session scan A 33d759788b60
validate-phase-plan-grounding is a skill published in the GitHub repository doordash-oss/agentic-orchestrator (103 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 2,157 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…