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/yuusakuri/agent-skills/interview-scriptnpx skills add yuusakuri/agent-skills --skill interview-scriptgit clone --depth 1 https://github.com/yuusakuri/agent-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/yuusakuri/agent-skills/interview-script)<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/interview-script"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/interview-script.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.00062 | $0.01109 |
| Opus 5 | $0.00031 | $0.00554 |
| Sonnet 5 | $0.00012 | $0.00222 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
interview-script 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 3d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Interview Script
Create a structured interview script that surfaces real insights, not just opinions. Follows "The Mom Test" principles — ask about their life, not your idea.
Domain Context
Customer interviews are one source in Stage 1 (Explore) of continuous discovery. Other sources: stakeholder interviews, usage analytics, data analytics, surveys, market trends, SEO/SEM analysis. The PM needs direct access to users, stakeholders, engineers, and designers — "without proxies." The Product Trio (PM + Designer + Engineer — Teresa Torres) should work together on discovery, not just the PM alone.
Context
You are preparing a customer interview script for research on $ARGUMENTS.
If the user provides files (personas, hypothesis lists, product briefs, or previous interview notes), read them first.
Instructions
-
Clarify research objectives:
- What specific questions does the team need answered?
- What decisions will this research inform?
- What assumptions need validation?
-
Create the interview script with these sections:
Opening (2-3 min)
- Introduce yourself and the purpose (learning, not selling)
- Set expectations: "There are no right or wrong answers. We're here to learn from your experience."
- Ask permission to record (if applicable)
- Confirm time available
Warm-Up: Context & Background (5 min)
- "Tell me about your role and what a typical day/week looks like."
- "How long have you been doing [activity related to the product area]?"
- Goal: Build rapport and understand their context
Core Exploration: Jobs to Be Done (15-20 min)
Current situation and behavior (past tense, specific instances):
- "Walk me through the last time you [did the thing we're exploring]. What happened?"
- "What tools or methods did you use?"
- "How long did it take? Who else was involved?"
Pain points and frustrations (observe, don't lead):
- "What was the hardest part about that?"
- "If you could wave a magic wand, what would change?"
- "What have you tried to solve this? What happened?"
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.
- 3d ago First seen · 106 lines · 62 tokens per session scan A 892ca53da985
interview-script is a skill published in the GitHub repository yuusakuri/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,109 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…