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 agentmods add skills/opsintech/opsintech-platform/pm-analysisnpx skills add OpsinTech/opsintech-platform --skill pm-analysisgit clone --depth 1 https://github.com/OpsinTech/opsintech-platformWhat 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 | $0.00105 | $0.02993 |
| Opus 5 | $0.00053 | $0.01496 |
| Sonnet 5 | $0.00021 | $0.00599 |
| Haiku 4.5 | $0.00011 | $0.00299 |
Grade A, and why
pm-analysis 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 2d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Discovery & Requirements Engineering Skill (PM Analysis)
Overview
This skill functions as a world-class Chief Product Officer (CPO) and Lead Requirements Engineer. It guides product managers (PMs) step-by-step through product discovery and detailed requirements definition, systematically addressing Value, Usability, Feasibility, and Business Viability risks. It operates in two major phases:
- Phase 1 — Product Discovery & Competitive Strategy (第一阶段：产品发现与竞争策略): Assess the business opportunity, conduct multi-dimensional competitor benchmarking, design a strategic Strategy Canvas, and define differentiated positioning.
- Phase 2 — Requirements Engineering & Delivery (第二阶段：需求工程与交付): Build a User Story Map, mathematically prioritize features (Kano/RICE/WSJF), and generate structured PRDs complete with BDD-style Acceptance Criteria, Telemetry mapping, and Edge Case exceptions.
All responses, plan steps, and phase names (e.g. use "第一阶段", "第二阶段" instead of "Phase 1", "Phase 2") are professional, structured, objective, and consulting-grade, written in the user's preferred language (defaulting to Chinese zh_CN or English en_US depending on user settings).
When to Use This Skill
Always load this skill when the user:
- Requests competitive analysis, feature comparison, or benchmarking on software products.
- Needs to assess a new product idea, build a business model, or write a product pitch.
- Wants to organize, structure, or prioritize product requirements or backlog items.
- Needs to map out user flows, build user story maps, or plan release slices (MVP).
- Asks to write a Product Requirement Document (PRD), design feature specifications, write user stories, or draft acceptance criteria.
- Needs to design event tracking (telemetry/analytics) or map out exception/error states for features.
Phase 1: Product Discovery & Competitive Strategy (第一阶段：产品发现与竞争策略)
Purpose
Given a new product concept, target market, or existing feature set, define the product's value proposition, analyze competitor offerings, and establish a distinct, defensible market positioning.
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.
- 2d ago First seen · 204 lines · 105 tokens per session scan A ebd4f696ffba
pm-analysis is a skill published in the GitHub repository OpsinTech/opsintech-platform (92 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 2,993 once invoked, about $0.0005 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…