sdlc-worker

A worker command for AgentFlow, a development pipeline that assigns tasks to coding agents through a Kanban board. It performs one assigned stage, such as research, building, review, or testing, and reports progress.

In plain words
What is it for?
Running a single pipeline stage with either direct agent handoffs or, when those tools are unavailable, board comments and terminal polling.
Why use it?
It gives each worker a consistent way to read its task, execute the correct stage, and report status to the coordinator.

Skill for Claude CodeCodex

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-worker
Any agent
npx skills add UrRhb/agentflow --skill sdlc-worker
Clone the repo
git clone --depth 1 https://github.com/UrRhb/agentflow

Made for: Claude Code, Codex.

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,495 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.00065 $0.02495
Opus 5 $0.00032 $0.01247
Sonnet 5 $0.00013 $0.00499
Haiku 4.5 $0.00006 $0.00249

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

Security

Grade A, and why

sdlc-worker 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 2d 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-worker/SKILL.md · 248 lines

How it starts

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

/sdlc-worker

Execute AgentFlow pipeline work for the assigned worker slot.

Mode Detection

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

  1. Check if SendMessage tool is available in the current environment
  2. Check if this worker was spawned by an orchestrator via TeamCreate
Condition Mode Behavior
SendMessage available + spawned by orchestrator Plugin Use message-based handoffs and progress reporting
Tools not available Standalone Fall back to comment-based updates and terminal polling (original behavior)

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

Handoff Protocol (Plugin Mode)

When MODE = "plugin", use SendMessage for all stage transitions and status updates instead of relying solely on PM tool comments.

Message Types

Event SendMessage Target Body Format
Stage started sdlc-orchestrate [<STAGE>:STARTED] Task <TASK_CODE>. Slot: T<N>.
Heartbeat sdlc-orchestrate [HEARTBEAT] Task <TASK_CODE>. Slot: T<N>. Elapsed: <MIN>m.
Stage complete (pass) sdlc-orchestrate [<STAGE>:<RESULT>] Task <TASK_CODE> complete. PR: <URL>. Cost: ~$<COST>.
Stage failed/rejected sdlc-orchestrate [<STAGE>:<RESULT>] Task <TASK_CODE> failed. Reason: <SUMMARY>.
Blocked sdlc-orchestrate [BUILD:BLOCKED] Task <TASK_CODE>. Reason: <REASON>.
Security warning sdlc-orchestrate [SECURITY:WARNING] Task <TASK_CODE>. Suspicious content detected.

Dual-Write Rule

In plugin mode, ALWAYS write updates to BOTH:

  1. SendMessage to the orchestrator (primary, low-latency)
  2. PM tool comment tags (secondary, persistence and auditability)

This ensures the PM tool remains the source of truth even if message delivery fails.

Progress Reporting (Plugin Mode)

When MODE = "plugin", send progress updates every 30 seconds during active work:

Read the full file on GitHub · 248 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. 2d ago First seen · 248 lines · 65 tokens per session scan A cfdf99a06313

Subscribe to this mod's changes

sdlc-worker is a skill published in the GitHub repository UrRhb/agentflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 2,495 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.