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/generatenpx skills add anombyte93/prd-taskmaster --skill generategit clone --depth 1 https://github.com/anombyte93/prd-taskmasterWhat 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.00091 | $0.03727 |
| Opus 5 | $0.00046 | $0.01863 |
| Sonnet 5 | $0.00018 | $0.00745 |
| Haiku 4.5 | $0.00009 | $0.00373 |
Grade A, and why
generate 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.
How it starts
The opening of the file, as written. The whole thing — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 2: Generate
Declarative phase skill. Invoked by the prd-taskmaster orchestrator when
current_phase is GENERATE. Never called directly by a user.
The one rule: generate the spec, validate it catches placeholders, parse it into tasks, expand every task into subtasks. Quality over speed.
Entry gate
-
Call
mcp__plugin_prd_go__check_gate(phase="GENERATE", evidence={})for diagnostics.check_gateis an EXIT gate: it checkstask_count > 0,subtask_coverage >= 1.0, andvalidation_grade in (EXCELLENT, GOOD)— all of which are GENERATE's OWN OUTPUTS, i.e. evidence to advance, not preconditions to enter. On first entry none exist yet, so agate_passed: falsehere is EXPECTED — the state machine's legal transitions already guarantee only legal entry.- First entry (no evidence yet): note the result and continue with the Procedure.
- Re-entry: if the gate reports violations, report them and stop — it protects against re-running a completed phase or skipping ahead from DISCOVER.
-
Read the DISCOVER output (discovery summary +
CONSTRAINTS CAPTUREDblock- scale classification). If any of these are missing, report and stop — the gate should have caught this, but belt-and-braces.
Generate checklist
Copy into your response before running the procedure:
GENERATE CHECKLIST:
- [ ] Template loaded (comprehensive|minimal)
- [ ] Spec written with discovery answers (no bare placeholders remaining)
- [ ] CONSTRAINT CHECK: every DISCOVER constraint appears in the spec
- [ ] SCOPE CHECK: task count matches scale (Solo 8-12, Team 12-20, Enterprise 20-30)
- [ ] Validation score: ___ / ___ (grade: ___)
- [ ] placeholders_found: ___ (bare placeholders = 0 required)
- [ ] Warnings addressed or acknowledged
- [ ] Tasks parsed: ___ tasks created
- [ ] Complexity analyzed via TaskMaster: Y/N
- [ ] All tasks expanded into subtasks: Y/N
Step 1: Choose and load template
Decide based on discovery depth:
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.
- 2d ago First seen · 379 lines · 91 tokens per session scan A 1cfc57ae3fb3
generate is a skill published in the GitHub repository anombyte93/prd-taskmaster (593 stars, last pushed 19d ago), licensed MIT. It adds 91 tokens to every session and 3,727 once invoked, about $0.0005 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.
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…
enterprise-prd-writer
企業 PRD Writer — 受監管 / 金流 / 風控 / 跨職能團隊等級的產品需求文件撰寫與強化工具， 用於產出可直接進入 Refinement、Engineering Design、Development、QA 與 UAT 的 「施工藍圖」等級文件。相對於輕量版 prd-writer，此版本額外涵蓋權限矩陣、NFR、 依賴管理、合規、Analytics/Observability、Rollout/Migration/Rollback 與 UAT/Release Readiness。 預設以 interactive-html-report 規格輸出互動式 HTML（含常駐目錄側欄、捲動高亮）。 ⚠️ 版本選擇（重要）：…