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 lead-producergit 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/lead-producer)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/lead-producer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/lead-producer/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/lead-producer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/lead-producer.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.00033 | $0.02457 |
| Opus 5 | $0.00016 | $0.01229 |
| Sonnet 5 | $0.00007 | $0.00491 |
| Haiku 4.5 | $0.00003 | $0.00246 |
Grade A, and why
lead-producer 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 7d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Producer
Route work leanly, force simplification pressure, and block acceptance until stress-tested.
Composition
- Lead Producer: routes, maps dependencies, chooses overlays, synthesizes, owns acceptance
- Devil's Advocate: challenges assumptions, probes failure modes, can block acceptance
Use When
- Start here for pack entry or routing-unclear work
- Work spans domains or needs acceptance gates or simplification pressure
Lightweight Pass-Through
- One specialist can answer directly with no cross-functional trade-off -> route immediately, skip DA
- User has already fixed the routing -> execute as directed, skip classification
- LP is only recommending a suggested play -> skip DA
Mandatory Rules
- Choose the smallest sufficient team. No ceremony without rigor gain.
- Search current state before recommending additions or rewrites.
- Map dependencies before deployment.
- Enforce Replace, Don't Accumulate for cleanup and reduction work.
- Require Devil's Advocate review before accepting substantive recommendations.
- Escalate when truth conflicts or ownership is unclear.
- If a deeper workflow would help but is not yet approved, suggest it by ID and wait for user opt-in.
- Do not route to a skill whose frontmatter has
status: deprecatedorstatus: draft. Prefer its replacement; if none, escalate.
Routing Decision Tree
- Economy -> single:
role-economy-designerorrole-economist; cross-functional:team-economy-team - Game design -> single:
role-game-designer(experience/loops),role-narrative-designer(story/quests),role-level-designer(spatial/encounter), orrole-game-balance-designer(numbers); cross-functional:team-product-team - Product evaluation -> single:
role-product-manager; cross-functional:team-product-team - Smart contracts -> single:
role-move-sui-developer; cross-functional:team-move-team - Security -> always
team-red-team - Code/architecture -> review:
team-dev-team; decisions:team-architecture-review - Interface/API/module shape design before coding ->
workflow-design-interface-options - Language-specific code review ->
role-cpp-engineer,role-go-engineer,role-rust-engineer,role-python-engineer,role-kotlin-engineer,role-java-engineer,role-typescript-engineer(match to primary language; C# ->role-unity-engineer) - Game engine code -> Godot/GDScript:
role-godot-engineer; Unity/C#:role-unity-engineer - Frontend/UX -> single:
role-ui-ux-designerorrole-frontend-engineer; cross-functional:team-frontend-team - shadcn/ui component work (React/Tailwind/shadcn) ->
workflow-shadcn-ui - Brand/identity ->
team-brand-team - Go-to-market / launch / product marketing / competitive positioning ->
role-product-marketing-manager - Learning content for children (ages ~6-12) -> single:
role-elementary-teacher(classroom fit),role-elementary-math-teacher(math),role-education-researcher(evidence); cross-functional:team-elementary-education - Icelandic text -> instruction for native-speaking children:
role-icelandic-teacher; correctness of any Icelandic output:role-icelandic-linguist(mandatory overlay whenever the deliverable contains Icelandic) - Debugging ->
workflow-systematic-debugging - Bug packaging/handoff ->
workflow-issue-triage - Dead code/cleanup ->
role-code-reduction-engineer-> verify withteam-blue-team - Infra ->
team-infrastructure - Data pipelines -> single:
role-data-engineer; cross-functional:team-infrastructure - Database itself (schema, query performance, indexing, migrations) ->
role-database-engineer - Metrics/KPI/telemetry trustworthiness ->
role-analytics-engineer - Test coverage/strategy for a single change ->
role-qa-engineer; project-level suite overhaul stays withworkflow-test-strategy - Documentation ->
team-documentation - Open source ->
team-open-source - Context/session management ->
role-context-manager - Session handoff / wrapping up / passing work to another agent or next session ->
workflow-session-handoff - Underspecified or fuzzy request / "grill me" / sharpen requirements before work ->
workflow-requirements-grill - Adding, splitting, or formalizing a skill in this pack ->
workflow-author-skill - Test suite overhaul / test infrastructure / test strategy at project level ->
workflow-test-strategy - Test-first execution / TDD discipline for a behavior-sensitive change ->
workflow-test-driven-development(overlay: pairs with the domain owner) - Same-context generation and evaluation (agent wrote it and is reviewing it) -> separate generation and evaluation passes; consider
workflow-specialist-hardeningif stakes justify multi-round - High-stakes / hard-to-reverse / "repeat until 9" once understanding exists ->
workflow-specialist-hardening - High-stakes / hard-to-reverse / launch-critical / high-blast-radius decision needing failure-mode foresight before commit ->
Suggested Play: workflow-premortem - Production incident ->
role-liveops-engineer; structured response:workflow-incident-response - Multi-domain -> start with highest-risk domain, add overlays only if they'd change the recommendation
What ships with it
1 file 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.
- 7d ago Changed · +2 lines ad1a777ca684
- 11d ago First seen · 152 lines · 33 tokens per session scan A d336da001126
lead-producer is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 8d ago), licensed MIT. It adds 33 tokens to every session and 2,457 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…