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/hmbown/codewhale/interviewnpx skills add Hmbown/CodeWhale --skill interviewgit clone --depth 1 https://github.com/Hmbown/CodeWhaleWhat 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.00040 | $0.00187 |
| Opus 5 | $0.00020 | $0.00093 |
| Sonnet 5 | $0.00008 | $0.00037 |
| Haiku 4.5 | $0.00004 | $0.00019 |
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.
What it actually says
Interview
When to use
Use when the request lacks a material product or implementation choice that cannot be discovered from the workspace or tools.
Non-goals
- Do not interview for facts you can read, search, or measure.
- Do not ask multi-question dumps. One focused question at a time.
- Do not invent requirements.
Workflow
- State the missing decision and why it blocks progress.
- Offer concrete options when possible.
- Record the answer and continue the work.
- Produce a short brief/spec only when enough answers exist.
Failure mode
If the user declines to answer, proceed with explicit assumptions and label them.
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 · 25 lines · 40 tokens per session scan A 273bc3906c6b
interview is a skill published in the GitHub repository Hmbown/CodeWhale (40,889 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 187 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
Session Monitoring
Provides awareness of claudectl session state, health checks, and cost tracking. Activated when the user asks about session health, spending, brain decisions, or multi-session coordination.
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
organize-modules
Apply private modules with public re-exports (barrel export) pattern for clean API design. Includes conditional visibility for docs and tests. Use when creating modules, organizing mod.rs files, or before creating commits.
check-bounds-safety
Apply type-safe bounds checking patterns using VPIndex/VPLength types instead of usize. Use when working with arrays, buffers, cursors, viewports, or any code that handles indices and lengths.
check-code-quality
Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.
analyze-performance
Establish performance baselines and detect regressions using flamegraph analysis. Use when optimizing performance-critical code, investigating performance issues, or before creating commits with performance-sensitive changes.