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-personasgit 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-personas)<a href="https://agentmods.dev/skills/julianoczkowski/product-manager/pm-personas"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-personas/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-personas"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-personas.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.00105 | $0.01179 |
| Opus 5 | $0.00053 | $0.00589 |
| Sonnet 5 | $0.00021 | $0.00236 |
| Haiku 4.5 | $0.00011 | $0.00118 |
Grade A, and why
pm-personas 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 11d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personas (Pragmatic Framework: Planning → Buyer Personas & User Personas)
Rule: Teams that understand personas and their problems build remarkable products.
A persona is an archetype built from observed patterns, not a fictional character
you invented. Ground every trait in market evidence (interviews, win/loss, support,
usage). See ../pm-copilot/references/framework.md for the market-driven basics.
- Buyer persona — the archetypical person who makes or influences the purchase decision (motivations, barriers, buying process). Guides marketing and sales.
- User persona — the archetypical person who uses the product day to day. Guides the product. In B2B the buyer and user are usually different people — build one of each. Create a separate persona whenever the problems genuinely differ.
The Interview Matrix (get a balanced cross-section)
Before writing personas, make sure you've talked to a balanced sample. Map who to interview across segments and persona types:
| Segments | Buyer Personas (Economic · Technical · Functional) | User Personas (User 1 · User 2 · User 3) |
|---|---|---|
| Segment A | who fills each buyer role | who the day-to-day users are |
Buyer roles: Economic (owns the budget/ROI), Technical (gatekeeps on fit/risk), Functional (uses the outcome, champions internally). Balance interviews across all four market segments: customers, competitors' customers, evaluators (win/loss) and potentials.
Interview the user for inputs (batch questions)
- Which product/feature and market segment is this persona for?
- Is this a buyer or a user persona? (Do both if B2B.)
- What problems/roadblocks does this person have (their words, first person)?
- What are their goals — who they want to be, what they want to do, how they want to feel?
- What behaviors shape how they approach those goals?
- Their background — how did they get to their current situation/outlook?
- What evidence backs this (how many interviews/tickets/win-loss notes)?
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.
- 11d ago First seen · 112 lines · 105 tokens per session scan A abe29a1ca936
pm-personas is a skill published in the GitHub repository julianoczkowski/product-manager (32 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 1,179 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.