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/gonpx skills add anombyte93/prd-taskmaster --skill gogit 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.00076 | $0.00554 |
| Opus 5 | $0.00038 | $0.00277 |
| Sonnet 5 | $0.00015 | $0.00111 |
| Haiku 4.5 | $0.00008 | $0.00055 |
Grade A, and why
go 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.
What it actually says
go (orchestrator)
Pure routing. Reads pipeline state, dispatches to the correct phase skill.
Deferred MCP tools: in Claude Code the engine's MCP tools are often deferred — not
callable until loaded. If a tool below is not directly callable, first run
ToolSearch(query="select:mcp__plugin_prd_go__preflight") (keyword fallback
ToolSearch(query="+atlas engine preflight", max_results=10)) and use whichever prefix
matches (mcp__plugin_prd_go__ or mcp__atlas-engine__).
Flow
-
Call
mcp__plugin_prd_go__preflight()— get environment state -
Call
mcp__plugin_prd_go__current_phase()— get pipeline state -
Route via Skill tool:
- current_phase is null or SETUP → invoke
/prd:setup - current_phase is DISCOVER → invoke
/prd:discover - current_phase is GENERATE → invoke
/prd:generate - current_phase is HANDOFF → invoke
/prd:handoff - current_phase is EXECUTE → invoke
/prd:execute-task
- current_phase is null or SETUP → invoke
-
After phase skill returns, re-check current_phase. If it advanced, route to the next phase. If not, report the blocker.
Stateless routing
This skill does NOT hold procedure. Each phase skill owns its own logic. The orchestrator survives context loss because every phase skill reads current_phase() on entry.
Red flags
These thoughts mean STOP, you're rationalising:
- "I know which phase we're in, skip preflight" → NO. Preflight is cheap.
- "The phase skill already ran, I don't need to re-check" → NO. Context might have died.
- "I can just do the work myself" → NO. Dispatch to the phase 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.
- 2d ago First seen · 54 lines · 76 tokens per session scan A a3f471e198b5
go is a skill published in the GitHub repository anombyte93/prd-taskmaster (593 stars, last pushed 18d ago), licensed MIT. It adds 76 tokens to every session and 554 once invoked, about $0.0004 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（含常駐目錄側欄、捲動高亮）。 ⚠️ 版本選擇（重要）：…