sdlc-orchestrate

sdlc-orchestrate is a skill for Claude Code, Codex from UrRhb/agentflow. It costs 67 tokens per session (3,295 once invoked), scanned A, original, MIT.

A one-time coordinator for AgentFlow, a development pipeline that uses a Kanban board to track work. It reads project state, assigns tasks to worker agents, handles handoffs, and updates the board.

In plain words
What is it for?
Coordinating research, coding, review, and testing tasks across AgentFlow projects, including tracking costs and detecting inactive workers.
Why use it?
It removes the need to manually check task status, assign work, and move tasks between development stages. It runs once per invocation, so repeated runs require a scheduled job such as cron.

Skill for Claude CodeCodex

Part of the agentflow plugin — 6 skills, 4 agents, 1 MCP server shipped together

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.

agentmods
npx agentmods add skills/urrhb/agentflow/sdlc-orchestrate
Any agent
npx skills add UrRhb/agentflow --skill sdlc-orchestrate
Clone the repo
git clone --depth 1 https://github.com/UrRhb/agentflow

Made for: Claude Code, Codex.

Or install agentflow, the plugin that ships this one along with the rest of its 6 skills, 4 agents, 1 MCP server.

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,295 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00067 $0.03295
Opus 5 $0.00034 $0.01648
Sonnet 5 $0.00013 $0.00659
Haiku 4.5 $0.00007 $0.00330

Measured 3d ago against content hash a60f298eb0a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sdlc-orchestrate 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 3d 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.

plugin/skills/sdlc-orchestrate/SKILL.md · 327 lines

How it starts

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

/sdlc-orchestrate

Perform one stateless orchestration sweep of all AgentFlow projects.

This is a ONE-SHOT command. It reads state, makes decisions, updates the Kanban board, and exits. It does NOT run continuously. Durability comes from invoking this via real crontab:

# Default (every 15 min, ~$48/day):
*/15 * * * * ~/.claude/sdlc/agentflow-cron.sh >> /tmp/agentflow-orchestrate.log 2>&1

# Sprint mode (every 5 min, use during active dev only):
# */5 * * * * ~/.claude/sdlc/agentflow-cron.sh >> /tmp/agentflow-orchestrate.log 2>&1

Mode Detection

Detect whether running in plugin mode or standalone mode at startup:

  1. Check if SendMessage and TeamCreate tools are available in the current environment
  2. Check if the plugin manifest (plugin.json) is loaded
Condition Mode Behavior
SendMessage + TeamCreate available Plugin Use team management and message dispatch
Tools not available Standalone Fall back to slot-based terminal instructions (original behavior)

Set MODE = "plugin" or MODE = "standalone" and log it at sweep start.

Team Management (Plugin Mode Only)

When MODE = "plugin", the orchestrator manages worker agents directly instead of relying on terminal slots.

Spawning Workers

Use TeamCreate to spin up worker agents as needed:

TeamCreate:
  name: "sdlc-worker-T<N>"
  skill: "sdlc-worker"
  args: "--slot T<N>"

Rules:

  • Spawn workers on-demand when tasks are ready for dispatch (Step 6)
  • Maximum 4 concurrent workers (T2, T3, T4, T5) — matching the slot system
  • Track active workers in sweep state: { slot: "T2", agentId: "<id>", taskCode: "PROJ-003" }
  • Do NOT pre-spawn idle workers — only create when a task needs dispatch
  • If a worker agent exits or becomes unresponsive (no heartbeat for 10 min), mark the slot as available

Worker Lifecycle

Event Action
Task ready for dispatch TeamCreate a new worker for the assigned slot
Worker completes stage Worker self-terminates; slot becomes available
Worker unresponsive (>10 min) Log warning, mark slot available, task eligible for re-dispatch
All tasks done No workers running — zero cost when idle

Read the full file on GitHub · 327 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. 3d ago First seen · 327 lines · 67 tokens per session scan A a60f298eb0a8

Subscribe to this mod's changes

sdlc-orchestrate is a skill published in the GitHub repository UrRhb/agentflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 3,295 once invoked, about $0.0003 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

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens