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 agentmods add skills/lukedj78/dev-flow/prd-to-tasksnpx skills add lukedj78/dev-flow --skill prd-to-tasksgit clone --depth 1 https://github.com/lukedj78/dev-flowWrote 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/lukedj78/dev-flow/prd-to-tasks)<a href="https://agentmods.dev/skills/lukedj78/dev-flow/prd-to-tasks"><img src="https://agentmods.dev/badge/skills/lukedj78/dev-flow/prd-to-tasks.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00175 | $0.01930 |
| Opus 5 | $0.00088 | $0.00965 |
| Sonnet 5 | $0.00035 | $0.00386 |
| Haiku 4.5 | $0.00017 | $0.00193 |
Grade A, and why
prd-to-tasks 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 5d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prd-to-tasks — PRD.md → executable task list
This skill turns a PRD into a flat, ordered list of tasks small enough to be picked up by a developer or an AI executor. The output is .workflow/tasks.md — Markdown with - [ ] checkboxes — designed to be:
- Readable by humans as a project punch-list.
- Importable into beads (the gstack convention), GitHub Issues (one task per issue), or fed to ralph-tui as the task source.
- Pushable to Linear via the
linear-scrumskill (Setup mode), which readstasks.mdthrough the Linear MCP and creates one issue per task — not a CSV import. - Atomic enough that each line items represents 2–8 hours of work for a typical developer (or one focused session for an AI agent).
When this skill applies
- A
.workflow/PRD.mdexists andphaseisprd_drafted. - The user asks to "make the issues", "split the PRD", "create the task list", "ticket this".
- The orchestrator routes here from
prd_drafted(optional next step before scaffolding).
If .workflow/tasks.md already exists, enter revise mode: read the existing tasks and propose specific edits (add, remove, re-order, re-size) rather than overwriting.
Contract
This skill follows the dev-flow contract — see references/contracts.md for the canonical schema. Key facts:
- Reads
<root>/.workflow/PRD.md(mandatory) and.workflow/PROJECT.md(for stack/audience context). - Writes
<root>/.workflow/tasks.md. - Sets
phase = "tasks_split"on success (only if current phase is earlier in the enum).
Workflow
Step 1 — Read inputs and decide structure
Read .workflow/PRD.md. Extract:
- The list of user stories (
As a … I want … so that …). - The acceptance criteria for each story.
- Any non-goals (these become negative tasks: explicit "do NOT do X" notes, not work items).
- Technical constraints (e.g., "must use Postgres" → tasks like "set up Drizzle + Neon" go on the list early).
Group tasks into epics when there are 3+ user stories. With fewer stories, keep a flat list.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 136 lines · 175 tokens per session scan A d202c329cf45
prd-to-tasks is a skill published in the GitHub repository lukedj78/dev-flow (6 stars, last pushed today), licensed MIT. It adds 175 tokens to every session and 1,930 once invoked, about $0.0009 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.
Other skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…