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 team-product-teamgit 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/team-product-team)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/team-product-team"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/team-product-team/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/team-product-team"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/team-product-team.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.00036 | $0.00500 |
| Opus 5 | $0.00018 | $0.00250 |
| Sonnet 5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
team-product-team 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Team
Purpose
Decide whether a feature or product move is worth doing, feasible to ship, and measurable after launch.
Composition
- role-product-manager: user value, prioritization, outcome framing
- role-technical-product-manager: feasibility, dependencies, hidden complexity
- role-game-designer: player experience quality, engagement, progression
- role-analytics-engineer: success metrics, experiments, validation plan
- Synthesis: conflict handling, acceptance
Use When
- Evaluating feature proposal, roadmap item, scope trade-off
- Making go/no-go product decision
- Deciding MVP vs later phases
- Checking measurable success criteria
Do NOT Use When
- Pure implementation review with no product decision
- Architecture-only or deployment-only
- Economy-specialist question (use
team-economy-team)
Workflow
- Define user problem, audience, expected outcome, and current status quo or workaround.
- Pressure-test the narrowest buildable wedge before endorsing broader scope.
- Review value, feasibility, experience quality, and measurement together.
- Make scope cuts explicit; compare alternatives only when multiple plausible directions would change the decision.
- Produce recommendation with launch conditions and success checks.
Default Output
PRODUCT TEAM REVIEW
===================
Problem: user need, target segment, current status quo
Recommendation: go / no-go / re-scope, narrowest wedge
Scope: explicit cuts, alternatives if decision-relevant
Risks: feasibility, experience, adoption/measurement risks
Measurement: success metric, guardrails, post-launch checks
Conflict Resolution
- Product Manager has final go/no-go decision. TPM escalates feasibility blockers as hard constraints, not suggestions.
- Game Designer can request experience-quality gates but cannot override product-value judgment.
- Disagreements between specialists are documented in the output, not hidden.
Anti-Drift Rules
- Do not let feature momentum substitute for user-value evidence.
- Name the current status quo before expanding scope.
- Do not expand scope beyond the feature under review.
- If team cannot reach consensus, state the disagreement and escalate.
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 · 58 lines · 36 tokens per session scan A ddf761b3decf
team-product-team is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 500 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…