Borrowing it
Nothing to install: this file belongs to anthony-spruyt/claude-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/anthony-spruyt/claude-plugins/main/.claude/skills/interview/SKILL.mdgit clone --depth 1 https://github.com/anthony-spruyt/claude-pluginsWrote 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/anthony-spruyt/claude-plugins/interview)<a href="https://agentmods.dev/skills/anthony-spruyt/claude-plugins/interview"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/interview/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/anthony-spruyt/claude-plugins/interview"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/interview.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00064 | $0.00600 |
| Opus 5.5 | $0.00026 | $0.00240 |
| Sonnet 5.5 | $0.00013 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
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 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview
Main session only: a helper can't talk to the owner.
You build what you believe the owner wants, and that belief is thinner than it feels. An issue records the ask at the time it was written, not what the owner wants now. Find out what they want and why, so the calls they never mention get made their way.
Before the first question
Read the issue, its comments and the code it touches. Don't ask what those answer; play it back instead and ask what's wrong. A clear issue shortens the interview; only the owner's "skip" ends it.
First message
- One line: "Say 'skip' if you'd rather I just design it." On skip, state any big choice you're making (tool, layout, where it runs) in one plain line, then go to the design.
- One open question that gets them describing a real moment, e.g. "What happened last time this bit you?" or "Walk me through when you'd reach for this."
The conversation
While interviewing, this format replaces the Owner question rules in the orchestration skill.
- End each message with one question: one sentence, no list of example answers.
- Open questions first. Their words carry intent your options can't. Offer two options with your pick only when they're stuck; when they say "you pick", propose something concrete.
- A guess they can correct often beats a question: "I'm guessing this is because X keeps paging you?"
- Find out which choices they want to make and which they hand to you. A choice you make goes in the design as your call, never as something they agreed to.
- Ground to cover, never read out as a list: why now, what done looks like, goals, non-goals, anti-goals (what would make it a failure even if it works), what exists and what they've tried, prior art they liked or hated, the details they care about.
- Look things up yourself (repo, live systems, upstream docs) instead of asking facts you can check.
Play it back
As soon as you understand one part, describe it back in a short paragraph, then ask about the next part. Mark guesses as yours; only what they said goes in as theirs. End each playback by asking what's wrong or missing.
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 · 43 lines · 64 tokens per session scan A 94effd58bb3a
interview is a skill published in the GitHub repository anthony-spruyt/claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 600 once invoked, about $0.0003 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-10-16.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…