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/kv0906/pm-kit/updatenpx skills add kv0906/pm-kit --skill updategit clone --depth 1 https://github.com/kv0906/pm-kitWhat 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 | $0.00033 | $0.00681 |
| Opus 5 | $0.00016 | $0.00341 |
| Sonnet 5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
update scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS "https://api.github.com/repos/${REPO_SLUG}/releases/latest" How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/update — Framework Updates
Check for new PM-Kit releases and safely apply framework updates without touching your notes or config.
Usage
/update # Check + apply if available
/update --check # Check only, no download
/update --dry-run # Preview what would change without applying
What This Skill Does
1. Check Current Version
Read the local VERSION file to determine the installed version.
cat VERSION
If VERSION doesn't exist, tell the user to run ./scripts/setup.sh first.
2. Check Latest Release
Query the GitHub API for the latest release:
# Detect repo from git remote, fallback to kv0906/pm-kit
REPO_SLUG="kv0906/pm-kit"
REMOTE_URL="$(git remote get-url origin 2>/dev/null || true)"
if [ -n "$REMOTE_URL" ]; then
REPO_SLUG="$(echo "$REMOTE_URL" | sed -E 's#.*[:/]([^/]+/[^/.]+)(\.git)?$#\1#')"
fi
curl -sS "https://api.github.com/repos/${REPO_SLUG}/releases/latest"
3. Compare Versions
- If local version matches latest: report "You're on the latest version (vX.Y.Z)"
- If update available: show the version diff and changelog excerpt
4. Apply Update (if user confirms)
Run the update script, passing through any flags the user provided:
# If user ran /update --check:
./scripts/update.sh --check
# If user ran /update --dry-run:
./scripts/update.sh --dry-run
# If user ran /update (no flags):
./scripts/update.sh
The script will:
- Back up current framework files to
_archive/_updates/{date}/ - Download and extract the latest release
- Overwrite framework files (skills, templates, scripts, docs)
- Skip hybrid files (
_core/config.yaml,.gitignore) — shows diff instead - Never touch user content (notes, meetings, etc.)
- Update the
VERSIONfile
5. Post-Update Summary
After the script completes, summarize:
- Files updated and files skipped
- Backup location
- Any hybrid files that need manual merge
- Remind user to run
/pushto commit changes
What Gets Updated vs Preserved
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.
- 2d ago First seen · 90 lines · 33 tokens per session scan A b11808eba74e
update is a skill published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 681 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
critique-agent
Pressure-test an existing product brief or PRD pack — find gaps, hidden assumptions, inconsistencies, and failure modes before stakeholder review. Use when: critique brief, critique PRD, devils advocate, red team, pressure test, find holes, what could go wrong, stress test the doc, pre-mortem.
interview-frameworks
Frameworks for user interviews, question design, and qualitative research. Use when conducting user interviews, designing interview guides, researching user needs, or gathering qualitative insights. Trigger on: 'create an interview guide', 'how do I interview users', 'customer discovery questions', 'user research…
query-datasets
Answer grounded yes/no questions about what exists in the 03-datasets/ example corpora (supporttickets, calltranscripts) using the local SQLite + FTS5 + vector hybrid index. Use when the user asks 'do/does [corpus] contain/mention/include/have requests for X?', 'any [corpus] about Y?', or similar factual queries over…
critique-prd
Rubric-score a PRD pack (02 + 03) against the 7-dimension PM Brain rubric and run a 4-persona panel review. Returns scores, panel critiques, the single weakest section, a concrete rewrite, and P0/P1 fix lists. Use when: PRD review, score my PRD, rubric review, panel review, rewrite weakest section, critique-prd.
create-prd
Write the PRD pack (02-product-requirements.md + 03-success-metrics.md) on top of an approved product brief. Use when: PRD, product requirements, requirements doc, success metrics, spec writeup, shape the PRD.
create-internal-feature-announcement
Drafts an internal feature announcement (IFA) from the PRD pack and user sources using the repo template, then writes 04-internal-feature-announcement.md. Use when: IFA, internal feature announcement, internal FAQ, Slack IFA prep, launch comms pack, or internal product documentation from the template.