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/brazil-bench/pourpoise/code-task-generatornpx skills add brazil-bench/pourpoise --skill code-task-generatorgit clone --depth 1 https://github.com/brazil-bench/pourpoiseWrote 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/brazil-bench/pourpoise/code-task-generator)<a href="https://agentmods.dev/skills/brazil-bench/pourpoise/code-task-generator"><img src="https://agentmods.dev/badge/skills/brazil-bench/pourpoise/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.00066 | $0.02716 |
| Opus 5 | $0.00033 | $0.01358 |
| Sonnet 5 | $0.00013 | $0.00543 |
| Haiku 4.5 | $0.00007 | $0.00272 |
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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Task Generator
Overview
This sop generates structured code task files from rough descriptions, ideas, or PDD implementation plans. It automatically detects the input type and creates properly formatted code task files following Amazon's code task format specification. For PDD plans, it processes implementation steps one at a time to allow for learning and adaptation between steps.
Parameters
- input (required): Task description, file path, or PDD plan path. Can be a simple sentence, paragraph, detailed explanation, or path to a PDD implementation plan.
- step_number (optional): For PDD plans only - specific step to process. If not provided, automatically determines the next uncompleted step from the checklist.
- output_dir (optional, default: ".sop/planning"): Directory where the code task file will be created
- task_name (optional): For descriptions only - specific task name. If not provided, will be generated from the description.
Constraints for parameter acquisition:
- You MUST ask for all required parameters upfront in a single prompt rather than one at a time
- You MUST support multiple input methods for input including:
- Direct text input
- File path containing the description or PDD plan
- Directory path (will look for plan.md within it)
- URL to internal documentation
- You MUST confirm successful acquisition of all parameters before proceeding
Steps
1. Detect Input Mode
Automatically determine whether input is a description or PDD plan.
Constraints:
- You MUST check if input is a file path that exists
- If file exists, You MUST read it and check for PDD plan structure (checklist, numbered steps)
- If file contains PDD checklist format, You MUST set mode to "pdd"
- If input is text or file without PDD structure, You MUST set mode to "description"
- You MUST inform user which mode was detected
- You MUST validate that PDD plans follow expected format with numbered steps
2. Analyze Input
Parse and understand the input content based on detected mode.
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 · 315 lines · 66 tokens per session scan A 7d0eb825d60f
code-task-generator is a skill published in the GitHub repository brazil-bench/pourpoise (11 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 2,716 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…