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 stanislavnianko/product-discovery-claude-skills --skill discovery-handoffgit clone --depth 1 https://github.com/stanislavnianko/product-discovery-claude-skillsWrote 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/stanislavnianko/product-discovery-claude-skills/discovery-handoff)<a href="https://agentmods.dev/skills/stanislavnianko/product-discovery-claude-skills/discovery-handoff"><img src="https://agentmods.dev/badge/skills/stanislavnianko/product-discovery-claude-skills/discovery-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/stanislavnianko/product-discovery-claude-skills/discovery-handoff"><img src="https://agentmods.dev/badge/skills/stanislavnianko/product-discovery-claude-skills/discovery-handoff.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00072 | $0.01210 |
| Opus 5 | $0.00036 | $0.00605 |
| Sonnet 5 | $0.00014 | $0.00242 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
discovery-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 12d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery Handoff
Part of the discovery-phase skill pack ·
deliverablesgroup · readsdiscovery-context.md(runprofile-builderfirst if missing).
When discovery ends and delivery begins — possibly with a different team. This document is the bridge. Reading it cold should be enough to start delivery work.
When to run
- End of paid discovery sprint, transitioning to delivery contract
- End of pre-sale discovery, transitioning to client's internal team (PIVOT/KILL or "we'll do it ourselves" outcomes)
- Mid-engagement transition between agency teams
- Post-discovery internal handoff (PM → engineering)
Distinct from proposal (commercial) and go-nogo-memo (decision). Handoff is operational.
Step 1 — Read context + scan available artifacts
Read discovery-context.md. If missing, ask the BA inline: "who's the receiving team — same agency / different agency / client internal / mixed?" — tag the output [ASSUMED RECEIVER]. Never block; recommend profile-builder for high-stakes work.
Then scan the ./discovery/ directory for what's actually present. Build an inventory at top of doc — this is critical: a handoff doc that overstates what's been discovered misleads the delivery team.
Step 2 — Identify the receiving team
Ask BA:
- Who's receiving this? (named team / org / lead)
- What's their context? (familiar with the client / new to the domain / experienced with the tech stack)
- What format do they prefer? (doc / wiki / Linear / Notion)
- Will there be a live walkthrough, or async-only?
This shapes voice and depth. A familiar team needs links + summary. A cold team needs context-rich narrative.
Step 3 — Required sections
3.1 Inventory of artifacts
Bullet list of every file in ./discovery/. For each, one-sentence "what's in it".
3.2 The 30-second pitch
What was discovered, in 4 bullets max. Anyone reading this should know: the problem, the chosen direction, the top risks, the next concrete action.
3.3 Decisions made (with reasoning)
A table:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 120 lines · 72 tokens per session scan A 2096a32261db
discovery-handoff is a skill published in the GitHub repository stanislavnianko/product-discovery-claude-skills (1 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 1,210 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-31.
Other skills, from other repositories
customise-workflow
Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default…
expand-tasks
Expand all TaskMaster tasks with deep research before coding begins. Reads tasks.json, launches parallel research agents per task in waves using the research-expander agent. Writes findings back to tasks.json. Part of the prd-taskmaster toolkit. Use after PRD is parsed and before implementation. Invoke with…
eol-process
Run a product sunset end to end — decide, align, plan, prepare, announce, close. Use when you need the whole EOL process, not just one artifact.
epic-breakdown-advisor
Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
altitude-horizon-framework
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.