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 julianoczkowski/product-manager --skill pm-use-scenariosgit clone --depth 1 https://github.com/julianoczkowski/product-managerWrote 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/julianoczkowski/product-manager/pm-use-scenarios)<a href="https://agentmods.dev/skills/julianoczkowski/product-manager/pm-use-scenarios"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-use-scenarios/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/julianoczkowski/product-manager/pm-use-scenarios"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-use-scenarios.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.00100 | $0.00984 |
| Opus 5 | $0.00050 | $0.00492 |
| Sonnet 5 | $0.00020 | $0.00197 |
| Haiku 4.5 | $0.00010 | $0.00098 |
Grade A, and why
pm-use-scenarios 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use Scenarios (Pragmatic Framework: Planning → Use Scenarios)
Rule: articulate problems from the persona's point of view. A use scenario
illustrates a market problem as a "story" that puts it in context (including current
results) — it is one component of requirements. See
../pm-copilot/references/framework.md. Personas should exist first (pm-personas).
Anatomy of a Problem Card
Map interrogatives to fields:
| Field | Interrogative |
|---|---|
| [Problem Name] | What problem |
| [Persona] | Who has it |
| has [use scenario] | Why it occurs |
| with [frequency] | When it occurs |
Reframing sentence (great for turning a feature request into a problem):
[Persona] struggles with [problem] when [context] because [why it matters].
What vs. How — stay on the WHAT
| WHAT = the problem → PM → DEFINE | HOW = the solution → Team → DESIGN/BUILD |
|---|---|
| Name, Persona, Use Scenario, Frequency, Market evidence, Impact | Overview, flow chart, use cases, UI, prototypes, error conditions |
A use scenario ≠ a use case. A use scenario tells the problem story; a use case enumerates every interaction in the functional spec (the team's job).
Three considerations when articulating a problem
- Avoid ambiguous terms — do not use: flexible, adaptable, user-friendly, TBD, adequate, rapidly/quickly/fast, fault tolerant, scalable, ASAP, maximize/minimize/optimize (any "-ize" word), and/or, etc. Replace each with a concrete, observable statement.
- Edge cases ("what if?") — will your persona actually do it? Don't design for situations that won't happen.
- Who is significant? — the U-curve: the vocal extremes (novices + experts) are where we listen; the proficient majority is where we should listen. Write for the majority.
Interview the user (batch questions)
- Which persona and which market problem is this scenario for?
- Walk me through a real situation where this happens — what triggers it, what do they do today, and what's the current (bad) result?
- How often does it occur (frequency)?
- What evidence shows this is real (counts across inputs) and how bad is it (impact)?
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 · 88 lines · 100 tokens per session scan A 03b704f1b130
pm-use-scenarios is a skill published in the GitHub repository julianoczkowski/product-manager (32 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 984 once invoked, about $0.0005 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
persona-import
This skill should be used when the user asks to "import a paperclip agent", "convert paperclip to woterclip", "migrate from paperclip", "import persona from paperclip", or wants to convert existing Paperclip agent directories into WoterClip persona format.
falsify
Adversarial falsification of sigint research findings. Generates disconfirming queries, executes web-only adversarial search, assigns ordinal verdicts (falsified | weakened | survived | inconclusive), and applies remediation (quarantine, confidence downgrade, follow-up queue). Invocable standalone via /sigint:falsify…
regulatory-review
This skill should be used when the user asks to "analyze regulations", "regulatory landscape", "compliance requirements", "legal considerations", "regulatory risk", "industry regulations", "compliance analysis", "regulatory trends", or needs guidance on understanding regulatory environments, compliance requirements…
report-writing
This skill should be used when the user asks to "write a report", "executive summary", "research report format", "report structure", "present findings", "business writing", "analysis documentation", or needs guidance on structuring research outputs, executive communication, or professional report formatting.
tech-assessment
This skill should be used when the user asks to "assess technology", "technology evaluation", "tech stack analysis", "technical feasibility", "technology trends", "build vs buy", "technology roadmap", "architecture assessment", or needs guidance on evaluating technologies, technical due diligence, or technology…
persona-create
This skill should be used when the user asks to "create a persona", "add a new persona", "set up a new agent role", "add a woterclip persona", or runs the /persona-create command. Interactively creates a new WoterClip persona with SOUL.md, TOOLS.md, and config.yaml.