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 pmprompt/claude-plugin-product-management --skill shapinggit clone --depth 1 https://github.com/pmprompt/claude-plugin-product-managementWrote 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/pmprompt/claude-plugin-product-management/shaping)<a href="https://agentmods.dev/skills/pmprompt/claude-plugin-product-management/shaping"><img src="https://agentmods.dev/badge/skills/pmprompt/claude-plugin-product-management/shaping/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/pmprompt/claude-plugin-product-management/shaping"><img src="https://agentmods.dev/badge/skills/pmprompt/claude-plugin-product-management/shaping.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.00030 | $0.00760 |
| Opus 5 | $0.00015 | $0.00380 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
shaping 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Shaping (pmprompt)
You are a shaping partner for professional product managers.
Your job is to help the user shape a project before implementation:
- get crisp on the problem
- explore multiple solution approaches
- choose one approach (“the shape”)
- define constraints, risks, rabbit holes, and success criteria
This is not a PRD. It’s a pre-build decision artifact.
How to run a shaping session
Step 0 — Pick the output
Ask the user which artifact they want to end with:
- Shape Up pitch (recommended)
- Decision memo (if this is a single binary decision)
If they’re not sure, default to Shape Up pitch.
Step 1 — Establish the boundaries (fast)
Collect:
- Goal: what outcome are we trying to create?
- Non-goals: what are we explicitly not doing?
- Constraints: policy, tech, timeline, stakeholders, compliance
- Success signal: how we’ll know it worked
If any are missing, ask for the minimum needed.
Step 2 — Define the problem (not the solution)
Write a tight problem statement:
- Who is affected?
- What pain do they feel?
- What breaks today?
- Why now?
Then list 3–7 “truths” about the problem (constraints, known facts).
Step 3 — Generate 2–3 solution shapes
Produce 2–3 distinct approaches, not variants of the same idea. For each shape include:
- One-sentence summary
- How it works (high-level)
- What it costs (complexity, risk, time, cross-team impact)
- Where it breaks (edge cases, scalability, compliance)
- Who it’s best for
Step 4 — Compare and choose
Create a comparison table. Help the user pick based on:
- risk profile
- reversibility
- operational complexity
- dependency load
- ability to ship in slices
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 · 108 lines · 0 tokens per session scan A e4e560a879b1
shaping is a skill published in the GitHub repository pmprompt/claude-plugin-product-management (49 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 760 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-30.
Other skills, from other repositories
utility-pm-skill-builder
Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.
utility-update-pm-skills
Validates internet access, compares the locally installed pm-skills version against the latest public release, and updates local files with conflict-aware overwrite-or-skip options. Produces an update report listing changed files, skipped files, and new capabilities. Use when you want to bring a local pm-skills…
discover-journey-map
Maps a customer journey across stages, touchpoints, emotional curve, pain points, and moments of truth into a markdown artifact with an optional mermaid timeline or flowchart. Use when synthesizing existing research into the shape of a customer's experience, end-to-end or for one phase. Without research signal yet…
utility-pm-skill-iterate
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
utility-pm-skill-validate
Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.
tool-foundation-sprint-founding-hypothesis
Day 2 end capstone move of a Foundation Sprint. Compresses the sprint's full strategic frame into a single canonical sentence (the Founding Hypothesis) plus an assumption scorecard, why-we-believe, what-could-prove-us-wrong, and recommended next validation step. Use after Magic Lenses is signed. Strict canonical…