agentmods.dev

dev-plan-orchestrator

dev-plan-orchestrator is a skill for Claude Code from cicababba/claude-plugins-marketplace. It costs 41 tokens per session (799 once invoked), scanned A, original, MIT.

A planning coordinator for software-development sessions. After context analysis and a specification exist, it asks a separate planning agent to create the development plan and save the session documents.

In plain words
What is it for?
Use it after project initialization or when planning is explicitly requested to create plan.md, session.md, and, for complex projects, an architecture plan.
Why use it?
It keeps planning tied to the existing project context and specification. It also checks that the required documents exist before moving the session to a ready state.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dev-workflow-automation plugin — 9 skills, 4 commands, 11 agents shipped together

not rated 3repo 9mo ago A scan 41 tokens original MIT

Good fit Use it after project initialization or when planning is explicitly requested to create plan.md, session.md, and, for complex projects, an architecture plan.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cicababba/claude-plugins-marketplace/dev-plan-orchestrator
View source ↗ cicababba/claude-plugins-marketplace
Install

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.

Any agent
npx skills add cicababba/claude-plugins-marketplace --skill dev-plan-orchestrator
Clone the repo
git clone --depth 1 https://github.com/cicababba/claude-plugins-marketplace

Made for: Claude Code.

Or install dev-workflow-automation, the plugin that ships this one along with the rest of its 9 skills, 4 commands, 11 agents.

Wrote 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.

agentmods badge for dev-plan-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/dev-plan-orchestrator/github.svg)](https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/dev-plan-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/dev-plan-orchestrator"><img src="https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/dev-plan-orchestrator/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.

agentmods 80×15 button for dev-plan-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/dev-plan-orchestrator"><img src="https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/dev-plan-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 799 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00799
Opus 5 $0.00020 $0.00400
Sonnet 5 $0.00008 $0.00160
Haiku 4.5 $0.00004 $0.00080

Measured 9d ago against content hash f953fc4b3b3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

dev-plan-orchestrator 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 9d 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.

dev-workflow-automation/skills/dev-plan-orchestrator/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dev Plan Orchestrator

This skill orchestrates the planning phase by coordinating with the development-planner agent.

When to Use

  • After /init completes with context-analysis.md and specification.md
  • When user explicitly requests planning
  • When session status needs to transition from PLANNING to READY

Input

  • sessionPath: Path to the current session directory (or read from .current-session)

Responsibilities

  • Load current session via session-manager
  • Verify context-analysis.md and specification.md exist via artifact-fs-manager
  • Read content of both artifacts
  • Call development-planner agent with artifact contents
  • Persist returned artifacts via artifact-fs-manager:
    • plan.md (always)
    • session.md with All Steps Overview and Execution Batches (always)
    • architecture-plan.yaml (only for Mode B complex projects)
  • Update session Status: PLANNING → READY

MUST NOT

  • Implement planning logic itself (all planning stays in development-planner)
  • Change the semantics or constraints of development-planner
  • Generate prompts or step breakdowns directly
  • Modify source code
  • Skip calling development-planner agent

Process

Step 1: Load Session

  1. Use session-manager to load or verify current session
  2. Confirm session exists and has Status that allows planning

Step 2: Verify Prerequisites

  1. Use artifact-fs-manager to check context-analysis.md exists
  2. Use artifact-fs-manager to check specification.md exists
  3. If either missing: Report error, suggest running /init

Step 3: Read Artifacts

  1. Read context-analysis.md content
  2. Read specification.md content
  3. Prepare input payload for development-planner

Step 4: Invoke development-planner

  1. Call development-planner agent with:
    • Session path
    • Context analysis content
    • Specification content
  2. Wait for agent to complete
  3. Receive:
    • plan.md content
    • session.md content (with steps and batches)
    • architecture-plan.yaml content (optional, Mode B only)

Read the full file on GitHub · 108 lines

Changes

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.

  1. 9d ago First seen · 108 lines · 41 tokens per session scan A f953fc4b3b3f

Subscribe to this mod's changes

dev-plan-orchestrator is a skill published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It adds 41 tokens to every session and 799 once invoked, about $0.0002 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-31.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens