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 liqiongyu/lenny_skills_plus --skill product-operationsgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/product-operations)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/product-operations"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/product-operations/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/liqiongyu/lenny_skills_plus/product-operations"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/product-operations.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.00021 | $0.02185 |
| Opus 5 | $0.00010 | $0.01092 |
| Sonnet 5 | $0.00004 | $0.00437 |
| Haiku 4.5 | $0.00002 | $0.00218 |
Grade A, and why
product-operations 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 9d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Operations
Scope
Covers
- Defining a Product Ops charter that clarifies accountability, boundaries, and “how we work”
- Building systems that help PMs thrive: cadences, standardized artifacts, and decision support (not decision-making)
- Creating cross-functional interfaces (Product ↔ Ops/Sales/CS/Eng/Data/Support) to reduce friction and surprises
- Standing up an insights pipeline (qual + quant) so product teams get the right signals at the right time
- Operationalizing shipping + enablement: release readiness, internal comms, training, and feedback loops
When to use
- “We need Product Ops—define what it is here and what it owns.”
- “Our product team is scaling; we need standard roadmaps/check-ins and better operating cadence.”
- “PMs are drowning in coordination; set up a system to reduce overhead.”
- “Create a release enablement process (readiness, comms, training, feedback).”
- “We need a repeatable insights → decisions pipeline across Product/CS/Sales.”
When NOT to use
- You need to choose what to build (use
prioritizing-roadmap/defining-product-vision) - You need to define metrics/OKRs from scratch (use
writing-north-star-metrics/setting-okrs-goals) - You need to write a decision-ready PRD (use
writing-prds) or build-ready spec (usewriting-specs-designs) - You need deep customer discovery, interviews, or usability testing (use
conducting-user-interviews/usability-testing) - You need to design a single team's rituals (standup, retro, planning) rather than an org-wide operating system (use
team-rituals) - You need to improve one specific meeting's format and facilitation (use
running-effective-meetings) - You need to plan and execute a specific product launch (use
shipping-products)
Inputs
Minimum required
- Product org context: stage, team shape, main frictions (“what’s breaking at scale?”)
- Current planning/shipping rhythm (if any): roadmap/OKR cadence, release process, comms touchpoints
- Primary stakeholders: Product/Eng/Data/Ops/Sales/CS/Support + decision owners
- Desired outcomes: what should be easier/faster/clearer after Product Ops exists
- Constraints: compliance/privacy, tooling limits, resourcing, timelines
What ships with it
13 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.
- eval/eval_config.json 467 B
- eval/SHOWCASE.md 4.7 KB
- eval/with_skill.md 25 KB
- eval/without_skill.md 15 KB
- README.md 1.8 KB
- references/CHECKLISTS.md 1.8 KB
- references/EXAMPLES.md 1.1 KB
- references/INTAKE.md 1.8 KB
- references/RUBRIC.md 2.1 KB
- references/SOURCE_SUMMARY.md 1.7 KB
- references/TEMPLATES.md 3.7 KB
- references/WORKFLOW.md 3.0 KB
- skillpack.json 378 B
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.
- 9d ago First seen · 141 lines · 21 tokens per session scan A 24bdd0853403
product-operations is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 2,185 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
exec-weekly-agenda-generator
Synthesize the past week across meetings, chat, email, and calendar to generate a ranked list of 5-10 topics for the weekly leadership team meeting. Use when the user asks to prep for their leadership meeting, generate meeting topics, build the agenda, or says "prep me for Monday.".
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.