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.
git clone --depth 1 https://github.com/product-on-purpose/pm-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/commands/product-on-purpose/pm-skills/workflow-feature-kickoff)<a href="https://agentmods.dev/commands/product-on-purpose/pm-skills/workflow-feature-kickoff"><img src="https://agentmods.dev/badge/commands/product-on-purpose/pm-skills/workflow-feature-kickoff/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/commands/product-on-purpose/pm-skills/workflow-feature-kickoff"><img src="https://agentmods.dev/badge/commands/product-on-purpose/pm-skills/workflow-feature-kickoff.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.00016 | $0.00355 |
| Opus 5 | $0.00008 | $0.00178 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
workflow-feature-kickoff 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 10d 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
Run the Feature Kickoff workflow to go from problem to implementation-ready user stories.
This workflow uses multiple skills in sequence. For each step, read the skill instructions and follow them to create the artifact.
Workflow Steps
Step 1: Problem Statement
Use the define-problem-statement skill from skills/define-problem-statement/SKILL.md.
Create a clear problem framing document that defines:
- What problem are we solving?
- Who is affected?
- What does success look like?
Step 2: Hypothesis
Use the define-hypothesis skill from skills/define-hypothesis/SKILL.md.
Based on the problem statement, create a testable hypothesis:
- What do we believe will solve the problem?
- How will we measure success?
Step 3: PRD
Use the deliver-prd skill from skills/deliver-prd/SKILL.md.
Create a Product Requirements Document that specifies:
- What we're building
- What's in scope and out of scope
- Success metrics
- Technical considerations
Step 4: User Stories
Use the deliver-user-stories skill from skills/deliver-user-stories/SKILL.md.
Break the PRD into implementable user stories:
- Each story follows INVEST criteria
- Include acceptance criteria in Given/When/Then format
- Ready for sprint planning
Output
Create all four artifacts in sequence, ensuring each builds on the previous.
Reference the Feature Kickoff workflow at _workflows/feature-kickoff.md for additional guidance.
Context from user: $ARGUMENTS
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.
- 10d ago First seen · 54 lines · 16 tokens per session scan A 73b69f01598a
workflow-feature-kickoff is a command published in the GitHub repository product-on-purpose/pm-skills (657 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 355 once invoked, about $0.0001 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 commands, from other repositories
discover
Structured product discovery from problem to validated experiments.
competitive-intel
Deep competitive analysis from positioning to strategic moats.
growth
Design self-reinforcing growth loops and retention mechanics.
okr-planning
Structured OKR creation aligned with company objectives.
plan-launch
End-to-end launch planning from positioning to post-launch metrics.
pricing
Design pricing that captures value and validates willingness to pay.