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 skills add anombyte93/prd-taskmaster --skill handoffgit 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/handoff)<a href="https://agentmods.dev/skills/anombyte93/prd-taskmaster/handoff"><img src="https://agentmods.dev/badge/skills/anombyte93/prd-taskmaster/handoff/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/anombyte93/prd-taskmaster/handoff"><img src="https://agentmods.dev/badge/skills/anombyte93/prd-taskmaster/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 78 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 96 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 118 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 121 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 288 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.1 | $0.00158 | $0.05017 |
| Opus 5.5 | $0.00063 | $0.02007 |
| Sonnet 5.5 | $0.00032 | $0.01003 |
| Haiku 4.5 | $0.00016 | $0.00502 |
Grade A, and why
handoff 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 1mo 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 3: Handoff
Declarative phase skill. Invoked by the prd-taskmaster orchestrator when
current_phase is HANDOFF. Never called directly by a user.
The one rule: detect what the user has, recommend ONE mode, give the user a structured choice, dispatch the chosen mode. Mode D executes only on tier=premium; otherwise it is a locked teaser.
Entry gate
-
Call
mcp__plugin_prd_go__check_gate(phase="HANDOFF", evidence={})for diagnostics.check_gateis an EXIT gate: it requiresuser_mode_choiceandplan_file_exists— both produced by HANDOFF itself, i.e. evidence to advance, not to enter. On first entry neither exists 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 GENERATE.
-
Read the GENERATE outputs —
.taskmaster/docs/prd.md,.taskmaster/tasks/tasks.json,.taskmaster/reports/task-complexity-report.json. If any are missing, report and stop. The gate should have caught this, but belt-and-braces.
Handoff checklist
Copy into your response before running the procedure:
HANDOFF CHECKLIST:
- [ ] Capabilities detected (tier + per-capability flags)
- [ ] Recommended mode: ___ (reason: ___)
- [ ] Summary displayed (spec location, task count, capabilities)
- [ ] CLAUDE.md task workflow appended (idempotent)
- [ ] AskUserQuestion mode picker surfaced (or prose fallback if hook-blocked)
- [ ] User choice dispatched (Mode A / B / C, or D when tier=premium)
- [ ] Debrief scaffold emitted (optional, silently tolerated)
- [ ] Handoff complete
Step 1: Detect capabilities
MCP (preferred): mcp__plugin_prd_go__detect_capabilities()
CLI fallback: python3 script.py detect-capabilities
Returns a tier field ("free" or "premium") plus per-capability flags.
Key signals:
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.
- 1mo ago First seen · 437 lines · 158 tokens per session scan A efaba9fa17bd
handoff is a skill published in the GitHub repository anombyte93/prd-taskmaster (606 stars, last pushed 2mo ago), licensed MIT. It adds 158 tokens to every session and 5,017 once invoked, about $0.0006 per session on Opus 5.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
enterprise-prd-writer
A detailed product-requirements-document writer for regulated, financial, risk-management, and cross-functional projects. A PRD is a shared plan that explains what a product must do, who it serves, how it will be accepted, and what happens during release.
prd-writer
A lightweight tool for writing product requirements documents (PRDs), which describe what a feature should do and how it should be built. It produces detailed specifications with rules, screen states, acceptance checks, risks, and items excluded from the first version.
requirement-gap-finder
A requirements review assistant for brand-new products or systems that do not yet have a product requirements document (PRD), a written description of what should be built.
ai-prd-generator
PRD generator for AI features (LLM or ML). Before an AI feature goes to engineering, lists the decisions still open - failure handling, human review, evaluation - then builds a PRD with problem, users, scope, non-goals, user stories, and Given/When/Then acceptance criteria through 4 user-approved stages (or a one-shot…
test-case-writer
A test-case generator that turns product requirements and their acceptance criteria into executable QA cases. QA means checking that software behaves as required.
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.