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/helpnpx skills add kv0906/pm-kit --skill helpgit 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.00051 | $0.00898 |
| Opus 5 | $0.00026 | $0.00449 |
| Sonnet 5 | $0.00010 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
help 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 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.
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/help — PM-Kit Help Guide
Surface the command reference and workflow guide. Read-only — no files created.
Context
Full guide: @handbook/HELP_GUIDE.md Config: @_core/config.yaml Workflow examples: @handbook/WORKFLOW_EXAMPLES.md Processing flows: @_core/PROCESSING.md
Usage
/help
/help daily
/help preview
/help report
/help export
/help integrations
/help workflow
/help folders
Processing Steps
1. Parse Topic
| Input | Action |
|---|---|
| No args | Show quick cheat sheet + category overview |
daily, today |
Daily operations section |
preview, html |
Preview & HTML artifact section |
report, executive |
Report to me section + vs /progress |
export, xlsx, docx, pdf, pptx |
Export flags section |
integrations, jira, linear, notion |
Integrations section |
workflow, routine |
Recommended workflows section |
folders, structure, paths |
Folder map section |
ask, qmd |
Capture & retrieval section |
setup, onboard |
Setup & maintenance section |
{command} |
Look up specific command in HELP_GUIDE.md |
If topic not found, show cheat sheet and suggest closest match.
2. Load Content
Read handbook/HELP_GUIDE.md and extract the relevant section(s).
For specific commands, also check if .claude/skills/{command}/SKILL.md exists — include one-line description and example invocation.
3. Format Output
Default (/help):
# PM-Kit Help
## Quick Cheat Sheet
{table from HELP_GUIDE.md}
## Categories
- **Daily:** /today, /daily, /progress, /report, /weekly, /push
- **Artifacts:** /doc, /decide, /block, /meet
- **Preview:** /preview, /report --preview
- **Export:** --xlsx, --docx, --pdf, --pptx
- **Capture:** /inbox, /ask
- **Maintenance:** /onboard, /health, /update, /help
## New here?
/onboard → /today → /daily project-a: shipped X, wip Y
Full guide: handbook/HELP_GUIDE.md
Topic-specific (/help preview):
Return only that section from HELP_GUIDE.md, plus 2-3 example commands.
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 · 115 lines · 51 tokens per session scan A 0cb440e5e122
help is a skill published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 898 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-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-product-brief
Write concise (2-page) product briefs to get buy-in before investing in full specs. Use when: product brief, one pager, feature brief, quick spec, feature proposal, pitch idea.