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-positioninggit 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-positioning)<a href="https://agentmods.dev/skills/julianoczkowski/product-manager/pm-positioning"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-positioning/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-positioning"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-positioning.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.00090 | $0.01171 |
| Opus 5 | $0.00045 | $0.00585 |
| Sonnet 5 | $0.00018 | $0.00234 |
| Haiku 4.5 | $0.00009 | $0.00117 |
Grade A, and why
pm-positioning 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Positioning Document (Pragmatic Framework: Planning → Positioning)
Rule: Positioning focuses on the problems you solve, not features. Create a
separate positioning document for every persona whose problems differ. Write
problems in the persona's first-person voice. This is an internal document (an
"internal press release") used to gain buy-in, brief design/engineering, and hand
off to marketing to build external messaging. See the primitives in
../pm-copilot/references/framework.md.
Prepare
Ideally a team of 3–6 people with market knowledge, staying objective. Start with
one product and one persona/segment. If personas or market problems aren't defined
yet, run pm-personas and pm-market-problems first (or gather them inline).
Interview the user for inputs (batch questions)
- Product and the one persona + market segment this doc is for.
- The problem — why does this persona care? What's painful today? (Be empathetic; use their words.)
- The ideal solution from the persona's point of view — clear and specific.
- Evidence the problem is real (interviews, win/loss, support tickets, surveys).
- What the product does — enough to map features to capabilities.
Build it in three steps (per the Pragmatic method)
Step 1 — Draft the first four sections of the document:
- Problem — "There is a problem in the industry today…" (persona's first person).
- Solution — "The ideal solution to this problem is…" (clear, specific).
- Positioning Statement — the "billboard," ≤25 words, using the formula:
For [persona], [product] [verb] [problem] by [verb] [primary benefit].
- Product Description — overview, ≤50 words.
Step 2 — Problem-Oriented Capabilities (POC) worksheet. List every problem the
product solves for this persona (first person) → group similar problems and condense
to 3–5 problem groups → name the problem-oriented capability for each group →
map product features to each capability. Table: Market Problems | Problem-Oriented Capabilities | Product Features.
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 · 107 lines · 90 tokens per session scan A 1bb6b423ada0
pm-positioning is a skill published in the GitHub repository julianoczkowski/product-manager (31 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 1,171 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…
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.
augment
Deep-dive into a specific area of current research. Orchestrates a single dimension-analyst using full swarm pattern (TeamCreate, TaskCreate, SendMessage). Use when the user wants to augment current research with deeper analysis of a specific area.
market-sizing
This skill should be used when the user asks to "calculate market size", "TAM SAM SOM analysis", "estimate market opportunity", "market sizing", "total addressable market", "serviceable market", "market potential", or needs guidance on market size estimation methodologies, market opportunity calculations, or growth…