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/mikeyobrien/ralph-orchestrator/code-task-generatornpx skills add mikeyobrien/ralph-orchestrator --skill code-task-generatorgit clone --depth 1 https://github.com/mikeyobrien/ralph-orchestratorWrote 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/mikeyobrien/ralph-orchestrator/code-task-generator)<a href="https://agentmods.dev/skills/mikeyobrien/ralph-orchestrator/code-task-generator"><img src="https://agentmods.dev/badge/skills/mikeyobrien/ralph-orchestrator/code-task-generator.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.00040 | $0.01381 |
| Opus 5 | $0.00020 | $0.00691 |
| Sonnet 5 | $0.00008 | $0.00276 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
code-task-generator 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 4d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Task Generator
Overview
Generate structured code task files from rough descriptions or PDD implementation plans. Auto-detects input type and creates properly formatted .code-task.md files. For PDD plans, processes one step at a time to allow learning between steps.
Important Notes
These rules apply across ALL steps:
- User approval required: Present the task breakdown plan and get explicit approval before generating any files.
- Tests are integrated: Include unit test requirements in each task's acceptance criteria. Never create separate "add tests" tasks.
- PDD mode references: Always include the design document path as required reading. Only include research docs if directly relevant to the specific task.
Parameters
- input (required): Task description, file path, or PDD plan path
- step_number (optional, PDD only): Specific step to process. Auto-determines next uncompleted step if omitted.
- output_dir (optional, default:
.ralph/tasks/): Output directory for code task files - task_name (optional, description mode only): Override auto-generated task name
Constraints:
- You MUST ask for all required parameters upfront in a single prompt
- You MUST support input as: direct text, file path, directory path (looks for plan.md), or URL
Steps
1. Detect Input Mode
Check if input is a file with PDD plan structure (checklist + numbered steps). Set mode to "pdd" or "description" and inform the user.
2. Analyze Input
- PDD mode: Parse the plan, extract steps and checklist status, determine target step (from step_number or first uncompleted)
- Description mode: Identify core functionality, technical requirements, complexity level (Low/Medium/High), and technology domain
3. Structure Requirements
- PDD mode: Extract the target step's title, description, demo requirements, constraints, and integration notes with previous steps. Identify relevant research documents.
- Description mode: Identify functional requirements, infer technical constraints and dependencies.
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.
- 4d ago First seen · 161 lines · 40 tokens per session scan A 302fa6a5a346
code-task-generator is a skill published in the GitHub repository mikeyobrien/ralph-orchestrator (3,121 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,381 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-30.
Other skills, from other repositories
azure-openai-to-responses
Migrate Python apps from Azure OpenAI Chat Completions to the Responses API. Covers AzureOpenAI/AsyncAzureOpenAI client migration to the v1 endpoint, streaming, tools, structured output, multi-turn, EntraID auth, and model compatibility checks. Python-focused, Azure OpenAI-specific. USE FOR: migrate to responses API…
chart
Use when the user asks to visualize data with charts, graphs, or plots using the chart tool (bar, line, scatter, pie, time series, etc.).
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
review
Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
brainstorm
Explore ambiguous or early-stage ideas interactively — tracks wish-readiness and crystallizes into a design for wish.