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/vault-opsnpx skills add kv0906/pm-kit --skill vault-opsgit clone --depth 1 https://github.com/kv0906/pm-kitWrote 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/kv0906/pm-kit/vault-ops)<a href="https://agentmods.dev/skills/kv0906/pm-kit/vault-ops"><img src="https://agentmods.dev/badge/skills/kv0906/pm-kit/vault-ops.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 | $0.00038 | $0.00903 |
| Opus 5 | $0.00019 | $0.00451 |
| Sonnet 5 | $0.00008 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
vault-ops 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 4d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Operations Skill
Core operations for reading, writing, and managing files in a PM-Kit vault.
Vault Structure
pm-kit/
├── CLAUDE.md # Vault context (read first)
├── _core/ # config.yaml, MANIFESTO.md, PROCESSING.md
├── _templates/ # Note templates (ALWAYS USE)
├── 00-inbox/ # Unprocessed captures
├── 01-index/ # Project MOCs
├── daily/ # YYYY-MM-DD.md (multi-project)
├── docs/{project}/ # PRDs, specs
├── decisions/{project}/ # Decision records
├── blockers/{project}/ # Active blockers
├── meetings/ # Meeting notes
├── reports/ # Generated reports
│ └── previews/ # HTML previews (/preview, /report --preview)
└── _archive/ # Archived by YYYY-MM/
Naming Conventions (Naming-as-API)
Strict filename patterns enable glob queries without a database:
| Type | Pattern | Example |
|---|---|---|
| Daily | daily/YYYY-MM-DD.md |
daily/2026-01-15.md |
| Doc | docs/{project}/{slug}.md |
docs/project-a/checkout-flow.md |
| Decision | decisions/{project}/YYYY-MM-DD-{slug}.md |
decisions/project-a/2026-01-15-auth-approach.md |
| Blocker | blockers/{project}/YYYY-MM-DD-{slug}.md |
blockers/project-a/2026-01-15-api-rate-limit.md |
| Meeting | meetings/YYYY-MM-DD-{type}-{slug}.md |
meetings/2026-01-15-sync-sprint-review.md |
| Inbox | 00-inbox/YYYY-MM-DD-{slug}.md |
00-inbox/2026-01-15-quick-thought.md |
| Index | 01-index/{project}.md |
01-index/project-a.md |
File Operations
Creating Notes
- Check if note already exists (naming-as-API enables fast lookup)
- Load appropriate template from
_templates/ - Replace template variables (Handlebars syntax)
- Add YAML frontmatter with type, project, status, date, tags
- Insert wiki-links to related notes
- Write to correct folder per naming convention
Editing Notes
- Preserve YAML frontmatter structure
- Maintain existing wiki-links
- Use consistent heading hierarchy
- Apply standard tag format
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.
- 4d ago First seen · 105 lines · 38 tokens per session scan A b6c41ed2fad7
vault-ops is a skill published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 903 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
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.