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 product-on-purpose/pm-skills --skill utility-pm-skill-buildergit clone --depth 1 https://github.com/product-on-purpose/pm-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/product-on-purpose/pm-skills/utility-pm-skill-builder)<a href="https://agentmods.dev/skills/product-on-purpose/pm-skills/utility-pm-skill-builder"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/utility-pm-skill-builder/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/product-on-purpose/pm-skills/utility-pm-skill-builder"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/utility-pm-skill-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00060 | $0.04669 |
| Opus 5 | $0.00030 | $0.02335 |
| Sonnet 5 | $0.00012 | $0.00934 |
| Haiku 4.5 | $0.00006 | $0.00467 |
Grade A, and why
utility-pm-skill-builder 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Skill Builder
This skill creates new PM skills for the pm-skills library. It produces a Skill Implementation Packet - a complete design document with draft files in a staging area for review before promotion to canonical locations.
When to Use
- When you have an idea for a new PM skill
- When you want to add a domain skill (phase-specific), foundation skill (cross-cutting), or utility skill (meta/tooling) to the pm-skills library
- When a contributor needs guided skill creation that follows repo conventions
When NOT to Use
- To modify or improve an existing skill → use
utility-pm-skill-iterate - To audit an existing skill against conventions → use
utility-pm-skill-validate - To create a skill for a non-pm-skills context → use a general agent skill builder
- To create a workflow → workflows are authored directly, not via this builder
Instructions
When asked to create a new PM skill, follow these steps:
Step 1: Understand the Idea
Accept the idea in either form:
- Problem-first: "What PM problem does this skill solve? Who runs into this problem, and what do they currently produce (or fail to produce)?"
- Skill-first: "Describe the skill you want to create. What artifact does it produce? What PM activity does it support?"
Both entry points produce the same downstream flow. If the user provides one form, do not ask for the other - extract what you need and proceed.
If the idea is vague, ask ONE follow-up question to clarify the artifact type and target audience before proceeding.
Step 2: Gap Analysis
Check ALL existing skills for overlap. Use the Current Library Reference
below (derive the live inventory from skill-manifest.json or AGENTS.md)
AND scan the skills/ directory for the latest inventory. Include all four
families - domain, foundation, utility, and tool - the tool family is easy
to miss since it has no phase prefix pattern in common conversation.
What ships with it
4 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.
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 · 353 lines · 60 tokens per session scan A dcf36ec3145c
utility-pm-skill-builder is a skill published in the GitHub repository product-on-purpose/pm-skills (658 stars, last pushed yesterday), licensed Apache-2.0. It adds 60 tokens to every session and 4,669 once invoked, about $0.0003 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
status-update-writer
Use when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR. Do NOT use for writing a PRD or a retro doc — those need different structures.
stakeholder-update
Translate the same underlying project status into audience-appropriate versions (exec-brief, engineering-detail, customer-facing) without changing the underlying facts. Use when a PM needs to write a status update, especially when the same update needs to go to multiple different audiences. Pairs with…
scope-cut
Decision framework for what to cut when a spec, sprint, or launch is too big for the time or team available. Use whenever a PM says a scope needs to shrink, a deadline is fixed and the work isn't, or someone asks "what can we cut" or "what's the MVP version of this." Also trigger when reviewing a spec that feels…
escalation-judgment
Decision framework for whether a blocker, risk, or conflict is actually worth escalating to leadership versus resolving at the working level. Use when a PM is unsure whether to "loop in" a director/VP, when a team is stuck and someone suggests escalating, or when reviewing whether a past escalation was warranted. Also…
okrs
Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and create a cadence of progress. The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at…
shape-up
Use when asked to "shape up", "run a shaping session", "set an appetite", "scope a project without estimates", "betting table", or "ship in fixed cycles". Helps teams escape estimate-driven development and Scrum fatigue. The Shape Up method (created by Ryan Singer at Basecamp/37signals) uses fixed time boxes, variable…