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 skills add nWave-ai/nWave --skill nw-interviewing-techniquesgit clone --depth 1 https://github.com/nWave-ai/nWaveWrote 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/nwave-ai/nwave/nw-interviewing-techniques)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-interviewing-techniques"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-interviewing-techniques/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-interviewing-techniques"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-interviewing-techniques.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00026 | $0.00949 |
| Opus 5.5 | $0.00010 | $0.00380 |
| Sonnet 5.5 | $0.00005 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
nw-interviewing-techniques 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 1mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interviewing Techniques
Questioning Toolkit by Purpose
Problem Discovery
Understand if problem is real and worth solving.
- "Tell me about the last time you [encountered this problem]."
- "What was the hardest part about that?"
- "What did you do about it?" | "What don't you love about that solution?" | "What else have you tried?"
Understanding the Job
Map the job-to-be-done and desired outcomes.
- "What are you ultimately trying to accomplish?"
- "Walk me through your process step by step."
- "At each step, how do you know if you've succeeded?"
- "What slows you down or frustrates you most?" | "What workarounds have you created?"
Probing Assumptions
Challenge beliefs and uncover truth.
- "What makes you believe that?" | "What would need to be true for this to work?"
- "What could we assume instead?" | "What would change your mind?"
Testing Commitment
Distinguish interest from commitment.
- "Would you be willing to [specific action]?" | "What would you pay for this?"
- "Can you introduce me to someone else with this problem?" | "When can we schedule a follow-up?"
Exploring Implications
Understand impact and urgency.
- "If this were solved, what would change?" | "What would that enable you to do?"
- "What would happen if we didn't solve this?"
Interview Conduct Rules
Do: Ask about past specifics | Open, non-directive questions | Seek commitment not praise | Keep informal | 80% listening | Talk about their life first
Avoid: Future behavior questions | Leading questions | Accepting compliments as validation | Talking >20% | Mentioning idea before understanding problem | Formal settings
Assumption Challenging
Triggers
Challenge when: belief without evidence | prediction about future | negative feedback dismissed | skipping to solution | single data point relied on
Challenge Format
- "What evidence supports this?" -- specific past examples
- "What would disprove this?" -- falsification criteria
- "What's the opposite assumption?" -- explore alternatives
- "Who would disagree and why?" -- disconfirming perspectives
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.
- 1mo ago First seen · 109 lines · 26 tokens per session scan A 4b0e4c1cbfda
nw-interviewing-techniques is a skill published in the GitHub repository nWave-ai/nWave (620 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 949 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
engineering-workflow
A Chinese-language workflow for reliable software development. It describes exploring the problem, making a plan, using TDD (test-driven development, where tests are written before the code), debugging methodically, reviewing code, and verifying the result.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
moai-run
Implement SPEC requirements using DDD/TDD methodology.
test-driven-development
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
story-development
Implement user stories with test-driven development methodology.