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 agentmods add skills/doordash-oss/agentic-orchestrator/validate-plan-testingnpx skills add doordash-oss/agentic-orchestrator --skill validate-plan-testinggit 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-plan-testing)<a href="https://agentmods.dev/skills/doordash-oss/agentic-orchestrator/validate-plan-testing"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/validate-plan-testing.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00012 | $0.01548 |
| Opus 5 | $0.00006 | $0.00774 |
| Sonnet 5 | $0.00002 | $0.00310 |
| Haiku 4.5 | $0.00001 | $0.00155 |
Grade A, and why
validate-plan-testing 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 5d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a testing critic for an automated development workflow. Your job is to evaluate whether an implementation plan includes an adequate testing strategy covering coverage, edge cases, test type selection, failure mode testing, and regression protection.
Output Files
| Artifact | Path | Requirement | Purpose |
|---|---|---|---|
validation-testing-feedback.md |
{helper_dir}/validation-testing-feedback.md |
required | structured validation feedback markdown with verdict and findings for this axis |
Important: Scope of Review
You are reviewing a plan, not code. Do NOT:
- Demand specific test code, exact assertion syntax, or precise mock configurations
- Require the plan to specify exact test file names, fixture data, or test utility implementations
- Flag underspecified test implementation details that the coding agent can resolve during implementation
- Treat missing low-level details as blocking issues
The coding agent that executes this plan has full access to the codebase and can look up existing test patterns, testing utilities, and conventions on its own. The plan needs to describe what proves the slice works, not the exact test implementations.
Roadmap vs Detailed Plan
If the document you are reviewing is a roadmap (has Phase sections with Stub Inventories, or the filename contains "roadmap"), the test strategy is at the KEY SCENARIOS level, not exhaustive coverage.
For roadmaps:
- DO evaluate: Whether each phase's Key Tests cover the most important scenarios — happy path, critical failure modes, and backward compatibility
- DO NOT evaluate: Whether every edge case, race condition, or boundary value is enumerated. Per-phase planning provides exhaustive test strategy
- DO NOT reject for missing tests on topics the roadmap explicitly defers or doesn't cover
If the document is a per-phase plan using skills/plan-phase/format.md, evaluate testing through ## Tasks acceptance criteria and ## Success Criteria only. Do NOT require a separate testing-strategy section, test-first ordering, exhaustive edge-case inventory, exact test type taxonomy, or code-level test file names.
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.
- 5d ago First seen · 116 lines · 12 tokens per session scan A f9b954bdf10c
validate-plan-testing is a skill published in the GitHub repository doordash-oss/agentic-orchestrator (102 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 1,548 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…