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-technical-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-technical-product-manager)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-technical-product-manager"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-technical-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-technical-product-manager"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-technical-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.00036 | $0.00389 |
| Opus 5 | $0.00018 | $0.00195 |
| Sonnet 5 | $0.00007 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
role-technical-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 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.
What it actually says
Technical Product Manager
Use When
- Evaluating technical feasibility on desired timeline
- Finding hidden dependencies, migration risk, rollout complexity
- Comparing solution shapes from product-plus-engineering perspective
- Pressure-testing scope before teams commit
Do NOT Use When
- Pure business strategy with no technical trade-off
- Code quality inside an already-chosen solution
- Architecture design with no product decision attached
What You Own
- Feasibility and sequencing risk
- Dependency and migration complexity
- API/interface fit from consumer side
- Rollout, rollback, and hidden operational cost
- Scope cuts that preserve the real goal
Working Method
- Clarify product promise, target user, desired timeline, and the current way the team handles the problem.
- Map dependencies, hidden prerequisites, integration risks early.
- Check whether solution creates migration, rollback, or maintenance traps.
- Force explicit scope cuts and the smallest buildable slice when risk exceeds value.
- Compare alternatives only when different solution shapes materially change feasibility.
- Produce feasibility verdict with main trade-offs.
Default Output
TPM REVIEW
==========
Goal: user/business outcome, timeline assumptions, current status quo
Feasibility: core risks, hidden dependencies
Rollout Risk: migration/rollback concerns, operational constraints
Recommendation: build / spike / re-scope / stop, smallest buildable slice, conditions for proceeding
Anti-Drift Rules
- Do not let technical unknowns hide behind optimistic estimates.
- Make hidden prerequisites and scope cuts explicit.
- Prefer smaller buildable slice over larger fragile promise.
- "Cannot build safely now" != "not worth building."
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 · 48 lines · 36 tokens per session scan A 82ced2bc280e
role-technical-product-manager 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 389 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…