dev-execution-orchestrator

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

A development-session tool that carries out steps from plan.md and session.md, files that describe planned work and the current session. It dispatches suitable coding sub-agents, updates progress, and manages execution batches.

In plain words
What is it for?
Use it during a /run command to execute the next step, a full batch, or a specific available step. It verifies the plan, checks dependencies, and sends each step to an appropriate development agent.
Why use it?
It coordinates planned implementation work and checks that steps are valid and dependencies are complete before running them. It does not mark the overall session as completed.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

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

Good fit Use it during a /run command to execute the next step, a full batch, or a specific available step. It verifies the plan, checks dependencies, and sends each step to an appropriate development agent.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cicababba/claude-plugins-marketplace/dev-execution-orchestrator
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-execution-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-execution-orchestrator

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/dev-execution-orchestrator"><img src="https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/dev-execution-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,321 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.00043 $0.01321
Opus 5 $0.00022 $0.00660
Sonnet 5 $0.00009 $0.00264
Haiku 4.5 $0.00004 $0.00132

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

Security

Grade A, and why

dev-execution-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-execution-orchestrator/SKILL.md · 195 lines

How it starts

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

Dev Execution Orchestrator

This skill orchestrates the execution of development steps defined in the plan.

When to Use

  • During /run command execution
  • When executing one or more planned steps
  • When updating step progress and batch status

Input

  • sessionPath: Path to the current session (or read from .current-session)
  • mode: Execution mode:
    • next-step: Execute single next available step
    • full-batch: Execute all steps in next available batch
    • specific-step: Execute a specific step by ID (if dependencies satisfied)
  • stepId (optional): Specific step ID for specific-step mode

Responsibilities

  • Load session via session-manager
  • Read plan.md and session.md via artifact-fs-manager
  • Verify plan integrity:
    • Plan exists and contains Generated Prompts
    • Plan matches Session "All Steps Overview"
    • No circular dependencies between steps
  • Determine executable steps:
    • Status = NOT_STARTED
    • All dependencies have Status = COMPLETED
  • Dispatch execution to appropriate sub-agents using pre-generated prompts:
    • react-frontend-dev
    • angular-frontend-dev
    • nodejs-backend-dev
    • java-backend-developer
    • react-test-writer
    • backend-test-writer
    • database-architect
  • Update after each step:
    • Step status in session.md
    • Batch status in Execution Batches
    • Progress counter (X/Y steps completed)
  • Keep global Status = IN_PROGRESS

MUST

  • Set session Status to IN_PROGRESS at start of execution
  • Update step status to IN_PROGRESS before dispatching
  • Update step status to COMPLETED or FAILED after completion
  • Update progress after each step
  • NEVER set global session Status to COMPLETED

MUST NOT

  • Regenerate or alter the plan structure
  • Modify source code directly (sub-agents do this)
  • Create new steps not in the plan
  • Skip dependency validation
  • Auto-complete the session

Process

Step 1: Load Session and Artifacts

  1. Use session-manager to load current session
  2. Use artifact-fs-manager to read plan.md
  3. Use artifact-fs-manager to read session.md

Read the full file on GitHub · 195 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 · 195 lines · 43 tokens per session scan A 6bc139f6e8eb

Subscribe to this mod's changes

dev-execution-orchestrator is a skill published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It adds 43 tokens to every session and 1,321 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.

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