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 revise-phase-plangit 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/revise-phase-plan)<a href="https://agentmods.dev/skills/doordash-oss/agentic-orchestrator/revise-phase-plan"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/revise-phase-plan/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/revise-phase-plan"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/revise-phase-plan.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.00011 | $0.00832 |
| Opus 5 | $0.00005 | $0.00416 |
| Sonnet 5 | $0.00002 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
Grade A, and why
revise-phase-plan 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 12d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Plan Revision
Your job is NEVER to write code. Your only deliverable is the revised phase plan markdown inside the output directory.
Output Files
| Artifact | Path | Requirement | Purpose |
|---|---|---|---|
phase plan markdown |
{artifact_dir}/phase-plan.md |
required | phase plan markdown matching the plan-phase format contract |
Critical Rules
- Do NOT re-research the codebase. The previous plan already incorporates codebase exploration. Only read additional source files if the critic feedback specifically requires it.
- Do NOT start from scratch. Read the previous plan (provided inline below) and make targeted edits.
- Do NOT rewrite the plan if the critic has no substantive changes. If the feedback is purely positive, simply copy the previous plan file to the output directory unchanged.
- Respect approved roadmap scope — if the critic pushes you to shrink the plan below the Phase N contract approved in the roadmap, do NOT silently drop roadmap-assigned deliverables. Phase sizing is a roadmap concern; if the approved phase truly cannot land in one iteration, escalate via
AGENT_LOOP_NEED_INPUT: phase too large — revise roadmapso the roadmap itself gets re-sliced rather than diverging from it here. - Sticky axis approvals — if the revise prompt includes a
## Prior Axis Approvalsblock, treat the listedfrozen_sectionsfor each approved axis as no-touch boundaries. Do NOT rewrite or restructure them unless the currently-failing axis's feedback explicitly cites that section. Treat frozen sections as narrow — they list only the headings the approving axis specifically inspected, not every heading in the plan. If the currently-failing axis's feedback points at a section that another axis also froze, the currently-failing feedback wins: edit the section to address the active feedback. "No-touch" applies to gratuitous edits, not to edits demanded by an active rejection.
Revision Process
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.
- 12d ago First seen · 53 lines · 11 tokens per session scan A 56c48d944f4c
revise-phase-plan is a skill published in the GitHub repository doordash-oss/agentic-orchestrator (104 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 832 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…