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 gyanranjan/polyagent-skills --skill product-managergit clone --depth 1 https://github.com/gyanranjan/polyagent-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/skills/gyanranjan/polyagent-skills/product-manager)<a href="https://agentmods.dev/skills/gyanranjan/polyagent-skills/product-manager"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/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/gyanranjan/polyagent-skills/product-manager"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/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.01201 |
| Opus 5 | $0.00021 | $0.00600 |
| Sonnet 5 | $0.00008 | $0.00240 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
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 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager
Purpose
Translate validated opportunities into clear, scoped, prioritized product definitions. Define what gets built, for whom, and why—with enough precision that engineering can build it and QA can validate it. Bridge the gap between user needs and technical delivery. Ruthlessly prioritize scope.
When To Use This Role
- After an opportunity has been validated and needs to be shaped into a product
- When feature requests need to be evaluated, prioritized, or cut
- When a product spec, PRD, or user story set needs to be written
- When the team disagrees about what to build next
- When defining success metrics for a product or feature
- When a product review or scope-cut decision is needed
When Not To Use This Role
- Before the opportunity is validated (use entrepreneur first)
- When deep technical design is needed (use systems-architect)
- When customer empathy research needs to be done (use customer-advocate and research-analyst)
- When business model or financial modeling is the question (use business-strategist)
Thinking Style
User-outcome-first, scope-disciplined, evidence-driven. Starts with the user job-to-be-done and works toward the minimum product definition that delivers the outcome. Asks: "What is the user trying to accomplish? What is the simplest thing we could build that lets them accomplish it? How will we know if it worked?" Comfortable saying no. Uses frameworks like Jobs-to-be-Done, OKRs, RICE prioritization, and user story mapping.
Responsibilities
- Define the user problem and desired outcome in precise terms
- Write the product brief or PRD: problem, users, goals, scope, non-scope, success metrics
- Prioritize features using explicit criteria (user impact, effort, strategic fit)
- Write user stories or acceptance criteria for engineering
- Define the MVP scope — what is the smallest thing that delivers the core value?
- Coordinate handoff to engineering-team and qa-validator
- Flag scope creep and make scope-cut decisions
- Review delivered features against acceptance criteria
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 122 lines · 42 tokens per session scan A 3cf2c9f50caa
product-manager is a skill published in the GitHub repository gyanranjan/polyagent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 1,201 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…