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/anombyte93/prd-taskmaster/expand-tasksnpx skills add anombyte93/prd-taskmaster --skill expand-tasksgit clone --depth 1 https://github.com/anombyte93/prd-taskmasterWrote 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/anombyte93/prd-taskmaster/expand-tasks)<a href="https://agentmods.dev/skills/anombyte93/prd-taskmaster/expand-tasks"><img src="https://agentmods.dev/badge/skills/anombyte93/prd-taskmaster/expand-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.00068 | $0.01895 |
| Opus 5 | $0.00034 | $0.00948 |
| Sonnet 5 | $0.00014 | $0.00379 |
| Haiku 4.5 | $0.00007 | $0.00189 |
Grade A, and why
expand-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 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expand Tasks with Research v1.0
Expands TaskMaster tasks with research before coding begins.
Deterministic operations handled by script.py; AI handles judgment.
Script location: skills/expand-tasks/script.py (relative to plugin root)
Part of: prd-taskmaster plugin
Depends on: research-expander agent (parallel research worker), any research
provider configured via task-master models --set-research or registered as an
MCP research tool.
When to Use
Activate when user says: expand tasks, research tasks, research before coding for all, expand subtasks. Do NOT activate for: single task research (use /research-before-coding), PRD generation (use /prd:go).
Native-parallel first (token economy)
Before launching agent waves, check the cheaper path: the native engine expands tasks
in parallel for free. Prefer python3 script.py expand — backend op expand (native api) —
or the expand_tasks MCP tool: it runs structured expand across pending tasks
concurrently (inheriting the engine's ThreadPoolExecutor) on economy-tier models /
keyless host CLIs and merges atomically.
Use THIS skill's agent waves when: no provider/CLI is available, native expand reports
failures for specific tasks (rerun just those here), or the research must be repo-grounded
(agents can read the codebase; native expand cannot).
Prerequisites
- TaskMaster
tasks.jsonmust exist (run/prd:gofirst) - A research provider is configured — either (a)
task-master models --set-research <model> --<provider>for any task-master provider family, or (b) an MCP research tool registered in~/.claude.jsonthat Claude Code can call directly (for examplemcp__plugin_prd_go__*tools or an external search/reason MCP) - At least 1 task in
tasks.json
Workflow (5 Steps)
Step 1: Preflight
python3 skills/expand-tasks/script.py read-tasks
Returns JSON: total, expanded, pending_expansion, tasks[].
If pending_expansion is 0: Report all tasks already expanded. Exit skill.
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.
- 3d ago First seen · 215 lines · 68 tokens per session scan A 54b9076123f2
expand-tasks is a skill published in the GitHub repository anombyte93/prd-taskmaster (593 stars, last pushed 20d ago), licensed MIT. It adds 68 tokens to every session and 1,895 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
PRD Mastery: Context-Aware, Expert-Driven, and Token-Efficient Refinement
A skill that blends the wisdom of top industry experts, ensures token-efficient PRDs, and organizes outputs in a clear folder structure.
PRD Mastery: Context-Aware, Expert-Driven, and Token-Efficient Refinement
A skill that blends the wisdom of top industry experts, ensures token-efficient PRDs, and organizes outputs in a clear folder structure.
PRD Mastery: Context-Aware, Expert-Driven, and Token-Efficient Refinement
A skill that blends the wisdom of top industry experts, ensures token-efficient PRDs, and organizes outputs in a clear folder structure.
ai-delivery-spec
Use for creating, changing, reviewing, reverse-engineering or accepting requirements, PRDs, prototypes, competitor material or existing systems, including any small UI, field, column, tab, dropdown or legacy-HTML change. Supports /ads, /dig, /prd and /proto intent shortcuts where the host routes them. Always invoke…
productspec
Use when implementing, reviewing, planning, or changing work governed by a Product Spec. Treat .product-spec.md files as the product contract for the work.
productspec-authoring
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over…