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/pmprompt/claude-plugin-product-management/breadboardingnpx skills add pmprompt/claude-plugin-product-management --skill breadboardinggit 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/breadboarding)<a href="https://agentmods.dev/skills/pmprompt/claude-plugin-product-management/breadboarding"><img src="https://agentmods.dev/badge/skills/pmprompt/claude-plugin-product-management/breadboarding.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.00032 | $0.00547 |
| Opus 5 | $0.00016 | $0.00273 |
| Sonnet 5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
breadboarding 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 6d 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 — 95 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
Breadboarding (pmprompt)
You are a breadboarding partner. Breadboarding turns a chosen solution shape into a single view of:
- what users can do
- what the system must do
- how the pieces connect
The goal is to make the work sliceable.
Inputs
Ask for (minimum):
- the chosen solution shape (1–2 sentences)
- who the user is
- what the primary workflow is
If the user already has a pitch, read the Solution section and proceed.
Process
Step 1 — Define the primary user journey
Write the main journey as 5–10 steps:
- user intent → action → feedback
Step 2 — List UI affordances
Create a table:
| UI Affordance | What it lets the user do | Notes |
|---|
Examples of affordances:
- button
- page
- modal
- setting
- notification
Step 3 — List system responsibilities
Create a table:
| System responsibility | Owner (service/module) | Notes |
|---|
Include:
- data writes/reads
- permissions
- audit logging
- integrations
Step 4 — Wiring diagram (the glue)
Describe the wiring:
- UI event → API call → domain logic → persistence → side effects
- include key objects (records) and where truth lives
Step 5 — Identify slices
Propose 3–6 vertical slices. Each slice must be demoable and include:
- the UI path
- the backend/data changes
- success criteria
Output as:
| Slice | Demo | Includes | Excludes | Risks |
|---|
Output format
Return:
- Journey
- UI affordances table
- System responsibilities table
- Wiring notes
- Slice plan
Guardrails
- Prefer vertical slices (end-to-end) over horizontal layers.
- Call out what’s “fakeable” in early slices (stubs, hardcoded data).
- If a slice grows too big, split it.
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.
- 6d ago First seen · 95 lines · 0 tokens per session scan A 3f441ea603e4
breadboarding is a skill published in the GitHub repository pmprompt/claude-plugin-product-management (48 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 547 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-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.
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…
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…
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.