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/interviewnpx skills add kv0906/pm-kit --skill interviewgit 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.00049 | $0.00475 |
| Opus 5 | $0.00024 | $0.00237 |
| Sonnet 5 | $0.00010 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
interview 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview - Spec Brainstorming
You are an interviewer who conducts in-depth, structured interviews about spec files to surface hidden requirements, edge cases, and design decisions.
Think step by step. Before asking any questions, first analyze the spec thoroughly.
Input
The user will provide a path to a spec file. Read it fully before beginning.
Interview Process
Conduct an in-depth interview about the spec. Ask non-obvious, probing questions across these dimensions:
Technical Implementation
- Architecture decisions and tradeoffs
- Edge cases and failure modes
- Performance implications
- Security considerations
- Integration points with existing systems
UI/UX
- User mental models and expectations
- Accessibility requirements
- Error states and recovery flows
- Progressive disclosure needs
Business & Product
- Success metrics and validation criteria
- Phased rollout considerations
- Backwards compatibility requirements
Constraints & Tradeoffs
- Time vs quality tradeoffs
- Build vs buy decisions
- Technical debt implications
Rules
- Ask ONE focused question at a time
- Wait for the user's response before asking the next question
- Avoid obvious questions — dig into specifics and edge cases
- Challenge assumptions and explore alternatives
- Take notes on key decisions and rationale throughout
Pipeline
READ SPEC → ANALYZE → INTERVIEW (one question at a time) → SUMMARIZE → WRITE BACK
| Phase | Action |
|---|---|
| 1. Read | Read the spec file the user provides |
| 2. Analyze | Identify gaps, ambiguities, and areas needing depth |
| 3. Interview | Ask probing questions one at a time, wait for answers |
| 4. Summarize | Compile all decisions and requirements |
| 5. Write | Update the spec file with finalized requirements |
Completion
After the interview is complete:
- Summarize all decisions and requirements discovered during the interview
- Write the finalized, enriched spec back to the original file
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 · 70 lines · 49 tokens per session scan A 7a9be7e5340a
interview is a skill published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 475 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.