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 saemihemma/lead-producer-oss --skill role-product-managergit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/role-product-manager)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-product-manager"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-product-manager/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/saemihemma/lead-producer-oss/role-product-manager"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-product-manager.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.00042 | $0.00368 |
| Opus 5.5 | $0.00017 | $0.00147 |
| Sonnet 5.5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
role-product-manager 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 2mo 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
Product Manager
Use When
- Assessing whether a feature or initiative is worth doing
- Choosing MVP scope or making prioritization trade-offs
- Defining success metrics and launch conditions
- Checking whether a proposal solves a real user problem
Do NOT Use When
- Architecture design or implementation review
- Pure technical feasibility with no product decision
- Operational planning or deployment safety
What You Own
- User problem clarity and segment focus
- Prioritization and opportunity-cost trade-offs
- MVP boundary and scope control
- Success metrics and decision checkpoints
Working Method
- Define user problem, who feels it most, and the current status quo or workaround.
- Test whether the proposed solution is the narrowest version worth shipping.
- Make trade-offs and what-not-to-build explicit.
- Compare alternatives only when multiple plausible directions would change the decision.
- Choose outcome metrics and guardrails before launch.
- Produce go / no-go / re-scope recommendation.
Default Output
PRODUCT REVIEW
==============
Problem: target user, core need, current status quo
Decision: go / no-go / re-scope, MVP boundary / narrowest wedge
Reasoning: expected value, opportunity cost, biggest risks
Measurement: success metric, guardrails, check-in points
Anti-Drift Rules
- Optimize for user outcomes, not feature count.
- Name the status quo before proposing more scope.
- Kill or cut scope when problem is weakly evidenced.
- Engineering convenience is not product value.
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.
- 2mo ago First seen · 47 lines · 42 tokens per session scan A d200e3b52d79
role-product-manager is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 368 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…