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 no-session/claude-code-skills --skill product-managementgit clone --depth 1 https://github.com/no-session/claude-code-skillsWrote 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/no-session/claude-code-skills/product-management)<a href="https://agentmods.dev/skills/no-session/claude-code-skills/product-management"><img src="https://agentmods.dev/badge/skills/no-session/claude-code-skills/product-management.svg" alt="Measured on agentmods" 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.00026 | $0.01286 |
| Opus 5 | $0.00013 | $0.00643 |
| Sonnet 5 | $0.00005 | $0.00257 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
product-management 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 8d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Product Management
Purpose
Assist with product management work by providing access to your team's foundational product documents, frameworks, and team context. This skill points you to the source of truth documents that should guide all product work.
When to use this skill
- Writing or reviewing PRDs and product specs
- Working on design documents
- Discussing feature prioritization
- Planning product work
- Understanding team ownership and pod structure
- Referencing product principles or positioning
Getting Started
- The
templates/folder contains starter frameworks for each document type - Customize the templates with your company's context
- Replace
[YOUR_LINK_HERE]placeholders below with URLs to your own docs (Notion, Confluence, Google Docs, etc.) - If no external links are configured, the bundled templates serve as defaults
Source of Truth Documents
IMPORTANT: Always fetch these documents to get the latest content. These are the authoritative sources for your team's product approach.
Core Product Philosophy
-
Product Principles — Our foundational beliefs about how we build product [YOUR_LINK_HERE] Template: templates/product-principles.md
-
Core Value Proposition — What we uniquely offer [YOUR_LINK_HERE] Template: templates/core-value-proposition.md
-
11-Star Experience — Our vision for the ideal user experience [YOUR_LINK_HERE] Template: templates/11-star-experience.md
-
Product Positioning — How we position ourselves in the market [YOUR_LINK_HERE] Template: templates/product-positioning.md
How We Work
-
How We Build — Our approach to building product [YOUR_LINK_HERE] Template: templates/how-we-build.md
-
Prioritization Framework — How we decide what to build [YOUR_LINK_HERE] Template: templates/prioritization-framework.md
-
Product Research Bets — Our current research areas and bets [YOUR_LINK_HERE] Template: templates/product-research-bets.md
What ships with it
11 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.
- examples/factory/SKILL.md 5.7 KB
- templates/11-star-experience.md 6.2 KB
- templates/core-value-proposition.md 4.8 KB
- templates/how-we-build.md 7.3 KB
- templates/prd-review-rubric.md 8.7 KB
- templates/prd-template.md 9.4 KB
- templates/prioritization-framework.md 6.8 KB
- templates/product-positioning.md 6.6 KB
- templates/product-principles.md 6.7 KB
- templates/product-research-bets.md 5.6 KB
- templates/quarterly-plan.md 6.0 KB
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.
- 8d ago First seen · 145 lines · 26 tokens per session scan A a014097da612
product-management is a skill published in the GitHub repository no-session/claude-code-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 1,286 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-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.