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/dokkabei97/forged-claude-code/user-interview-guidenpx skills add Dokkabei97/forged-claude-code --skill user-interview-guidegit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/user-interview-guide)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/user-interview-guide"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/user-interview-guide.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.00035 | $0.01144 |
| Opus 5 | $0.00017 | $0.00572 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
user-interview-guide 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Interview Guide - Structured User Research
Overview
Helps startups conduct effective user interviews — the #1 tool for understanding customers. Bad interviews confirm your bias; good interviews reveal what you don't know.
1. When to Apply
| Trigger | Behavior |
|---|---|
| Pre-build validation | Discovery interview template |
| Feature validation | Validation interview template |
| Usability testing | Usability test script |
2. Interview Types & Templates
Discovery Interview (문제 발견)
Goal: Understand the problem space before building
## Interview Script: Discovery
**Intro (2 min):**
"Thanks for your time. I'm trying to understand how you [domain activity].
There are no right or wrong answers — I'm learning from your experience."
**Context (5 min):**
1. Tell me about your role and what you do day-to-day.
2. How does [topic] fit into your work?
**Problem Exploration (15 min):**
3. Walk me through the last time you [relevant activity].
4. What was the hardest part about that?
5. How do you handle [specific challenge] today?
6. What have you tried to solve this? What happened?
7. How often does this come up? (daily/weekly/monthly)
**Impact (5 min):**
8. What does this problem cost you? (time/money/frustration)
9. If you could wave a magic wand, what would change?
**Wrap-up (3 min):**
10. Is there anything I should have asked but didn't?
11. Who else should I talk to about this?
Key Rules:
- Ask about past behavior, not hypothetical futures
- Never pitch your solution during discovery
- "Tell me more about that" is your best follow-up
- Silence is powerful — let them think
Validation Interview (솔루션 검증)
Goal: Test whether your solution addresses real needs
## Interview Script: Validation
**Context (3 min):**
1. Remind me — how do you currently handle [problem]?
2. Has anything changed since we last spoke?
**Solution Presentation (5 min):**
[Show prototype/mockup/description]
"Here's something we're exploring. I'd love your honest reaction."
**Reaction (15 min):**
3. What's your first impression?
4. What would you use this for? (Don't suggest use cases)
5. What's confusing or unclear?
6. What's missing that you'd need?
7. Would this replace anything you currently use?
8. How much would you expect to pay for this? / Would you pay $X?
**Commitment Test (5 min):**
9. Would you be willing to try this for a week?
10. Can I follow up with you when it's ready?
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 · 174 lines · 35 tokens per session scan A 703c508f7b6b
user-interview-guide is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 1,144 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-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…