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-iterategit 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-iterate)<a href="https://agentmods.dev/skills/product-on-purpose/pm-skills/utility-pm-skill-iterate"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/utility-pm-skill-iterate/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-iterate"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/utility-pm-skill-iterate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 49 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00058 | $0.02853 |
| Opus 5 | $0.00029 | $0.01426 |
| Sonnet 5 | $0.00012 | $0.00571 |
| Haiku 4.5 | $0.00006 | $0.00285 |
Grade A, and why
utility-pm-skill-iterate 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Skill Iterate
This skill improves an existing pm-skills skill by applying targeted changes based on input you provide. It reads the current skill files, proposes changes as before/after previews grouped by file, and writes them on your confirmation. After applying changes, it suggests a version bump class and offers to update HISTORY.md.
The iterator accepts any of these as input:
- A validation report from
utility-pm-skill-validate - Direct feedback ("the template is missing section X")
- A convention change ("all skills now need a Limitations section")
- A general improvement request ("make the example more realistic")
When to Use
- After running
utility-pm-skill-validateand getting a report with findings - When you have specific feedback on a skill and want to apply it
- When a repo convention changes and a skill needs to conform
- When a skill's example, template, or instructions need improvement
- When iterating on a skill before a release
When NOT to Use
- To create a new skill from scratch -> use
utility-pm-skill-builder - To audit a skill before making changes -> use
utility-pm-skill-validatefirst - To make bulk convention changes across many skills -> run
utility-pm-skill-validate --allfirst to triage, then iterate one skill at a time
Instructions
When asked to iterate on a skill, follow these steps:
Step 1: Identify the Target Skill
Accept the skill name in any form:
- Directory name:
deliver-prd - Full path:
skills/deliver-prd/SKILL.md - Slash command:
deliver-prd
Resolve to the canonical directory path: skills/{name}/.
If the skill directory does not exist, stop and report: "Skill directory
skills/{name}/ does not exist. Use utility-pm-skill-builder to create it."
Step 2: Read Current Skill Files
Read all files in the skill directory:
| File | Required | Purpose |
|---|---|---|
SKILL.md |
yes | Frontmatter + instructions (the primary edit target) |
references/TEMPLATE.md |
yes | Output template |
references/EXAMPLE.md |
yes | Worked example |
HISTORY.md |
no | Version history (needed for Step 7) |
What ships with it
3 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 · 307 lines · 58 tokens per session scan A db3bed9f8f80
utility-pm-skill-iterate is a skill published in the GitHub repository product-on-purpose/pm-skills (658 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 2,853 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…