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/setupnpx skills add anombyte93/prd-taskmaster --skill setupgit 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.00077 | $0.01892 |
| Opus 5 | $0.00039 | $0.00946 |
| Sonnet 5 | $0.00015 | $0.00378 |
| Haiku 4.5 | $0.00008 | $0.00189 |
Grade A, and why
setup 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Setup
Declarative phase skill. Invoked by the prd-taskmaster orchestrator when
current_phase is null or SETUP. Never called directly by a user.
Entry gate
-
Call
mcp__plugin_prd_go__check_gate(phase="SETUP", evidence={})for diagnostics.check_gateis an EXIT gate: it verifies you have the evidence to advance, not to enter. On first entry you have no evidence yet (Step 4 below producesvalidate_setup.ready=true), so agate_passed: falseresult here is EXPECTED — the state machine's legal transitions (None → SETUP) 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.
Enforce the gate when you ADVANCE (after the procedure), not on entry.
Procedure (5 steps, abort on hard failure)
Step 1: Backend detection
Run backend detection:
python3 script.py backend-detect
The native engine is the sole generator and needs no external binary — a
keyless host CLI (claude / codex / gemini) on PATH, or a provider API key,
is sufficient (see Chunk 7's atlas setup wizard). The task-master binary is
no longer required or supported; backend-detect reports its presence purely as
informational. Continue with the resolved (native) backend.
Step 2: Project init
Check whether the current project has a .taskmaster/ directory (the engine
still reads/writes the .taskmaster/ file format for tasks and config).
If missing, run backend op init:
python3 script.py init-project
This initialises the native project state and the .taskmaster/ file format. If
.taskmaster/ is present, continue.
Step 2.5: Customisation bootstrap (REQUIRED — closes execute-task deadlock)
execute-task requires .atlas-ai/customizations/system-prompt-template.md
to exist as a precondition (its Entry gate halts otherwise). It cannot
create the file from inside the loop — the failure mode is a hard halt with
no recovery path.
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 · 196 lines · 77 tokens per session scan A 7cfa5e3004ce
setup is a skill published in the GitHub repository anombyte93/prd-taskmaster (592 stars, last pushed 18d ago), licensed MIT. It adds 77 tokens to every session and 1,892 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（含常駐目錄側欄、捲動高亮）。 ⚠️ 版本選擇（重要）：…