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 wunki/dotfiles --skill interviewgit clone --depth 1 https://github.com/wunki/dotfilesWrote 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/wunki/dotfiles/interview)<a href="https://agentmods.dev/skills/wunki/dotfiles/interview"><img src="https://agentmods.dev/badge/skills/wunki/dotfiles/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/wunki/dotfiles/interview"><img src="https://agentmods.dev/badge/skills/wunki/dotfiles/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.00147 | $0.01499 |
| Opus 5.5 | $0.00059 | $0.00600 |
| Sonnet 5.5 | $0.00029 | $0.00300 |
| Haiku 4.5 | $0.00015 | $0.00150 |
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 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview
Exhaustive requirements elicitation through deep, structured questioning. This skill gathers requirements; writing the spec or plan is a separate step that follows it.
When to Use
- User explicitly asks to be interviewed about a feature
- Starting a complex feature that needs thorough thinking before any code is written
- Existing SPEC.md has gaps that need filling
- Any task where requirements must be extracted before action
Workflow
1) Read Existing Context
Before asking anything:
- Check if
SPEC.mdexists in the project root (cwd). If yes, read it. - Check for
README.md, any files indocs/, and any existing code files directly related to the feature being discussed. - Note what is already documented vs. what is missing or ambiguous.
Do not ask questions you can already answer from existing context.
If no existing context is found (greenfield project), skip directly to Step 2 and open with purpose and scope questions.
2) Interview Deeply
Cover all areas below. Ask only non-obvious questions — things that cannot be discovered by reading the codebase.
| Area | What to explore |
|---|---|
| Purpose | What problem? Why now? What triggered this? What does success look like? |
| Technical | Architecture choices, data model, APIs, integrations, performance requirements |
| UI/UX | User flows, states, feedback, accessibility, responsive behavior |
| Edge cases | What could go wrong? Invalid inputs, race conditions, failure modes |
| Tradeoffs | What are we optimizing for? What are we willing to sacrifice? |
| Security/Privacy | Data sensitivity, auth requirements, audit needs |
| Testing | How do we verify it works? What is critical to test? |
| Rollout | Feature flags? Migration? Backwards compatibility? |
Prioritization: Always lead with Purpose questions. Then Technical. Adjust order based on what existing context already covers — skip areas the codebase has answered. Security/Privacy and Edge cases are never skippable; surface them even if the user seems impatient.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -3 lines · -10 tokens per session 134a1100c500
- 1mo ago First seen · 143 lines · 157 tokens per session scan A 02d6ba7fe9f4
interview is a skill published in the GitHub repository wunki/dotfiles (47 stars, last pushed 10d ago), licensed MIT. It adds 147 tokens to every session and 1,499 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
assess-quality
Foundational quality framework: the five questions (readable, easy to start, expands without bloat, consistent, intentional) every other dev skill is judged against, plus the dual-audience and workshop principles. Use when onboarding to a project, defining a quality bar, setting an assessment checklist, or arbitrating…
create-oss-skill
Create well-formed Agent Skills following the agentskills.io specification. Scaffold directories, write SKILL.md files, bundle scripts, and structure instructions for progressive disclosure. Use when creating a new skill, reviewing skill structure, optimizing a skill description, or setting up evals for skill quality.
orchestrate-agents
Orchestrate multiple agent CLIs (Claude, Codex, Antigravity) via tmux with a shared fleet store, dispatching one guardian subagent per pane. Survey-first: inspects and adopts existing tmux sessions, windows, and agent panes before creating anything new. Use when running a multi-agent session, dispatching parallel…
extend-oss-skills-to-claude
Extend standard agentskills.io skills with Claude Code-specific features. Invocation control, subagent execution, dynamic context injection, string substitutions, model/effort overrides, and deployment scoping. Use when adapting a portable skill for Claude Code, adding Claude-specific frontmatter, setting up subagent…
merge-ready
Drive an existing pull request to a mergeable state: get CI green, resolve merge conflicts with the base branch, address and resolve review comments, trigger required bot reviews/approvals (e.g. commenting '@claude review'), link associated issues, and clean up the PR title and description. Ends with a readiness…
scaffold-go
Scaffold a complete Go project with CI/CD, release pipeline, Makefile, sr.yaml, .envrc, and standard files. Uses go toolchain and make as the native build system. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Go CLI, service, or module, or when the user…