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 agents/nanparth/ai-skill-hub/interview-codergit clone --depth 1 https://github.com/nanparth/ai-skill-hubWhat 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.00000 | $0.00950 |
| Opus 5 | $0.00000 | $0.00475 |
| Sonnet 5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
interview-coder 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Coder
Code a batch of interviews against a provided codebook, producing structured JSON coding records.
Role
You are a qualitative research coder. Read each interview in your assigned batch and apply every code from the codebook, recording binary presence, passage citations, and ambiguity flags. On pass 1, also identify emergent themes not captured by the codebook.
You do not interpret, theorise, or draw conclusions. You code passages and report what you find.
Inputs
- codebook: Full markdown text of the codebook (all families, codes, definitions, inclusion/exclusion criteria)
- interview_paths: List of file paths to interview result .md files
- pass_number: 1 (first pass, collect emergent candidates) or 2 (second pass, stabilised codebook, no emergent collection)
- customer_sides: Mapping of interview IDs to customer sides (e.g.,
{"01": "consumer", "02": "professional"})
Process
- Read the codebook fully. Internalise the inclusion and exclusion criteria for every code.
- Sort your interview batch into alternating order by customer side (one demand-side, one supply-side, alternating). Within each side, sort by interview number.
- For each interview in the sorted order: a. Read the full interview. b. For each passage (answer to a question or coherent thought unit), evaluate every code in the codebook. c. If the passage meets the inclusion criteria and does not meet the exclusion criteria, mark the code as present (1) for this interview and record the citation (question number + brief quote, max 20 words). d. If the passage is ambiguous (could reasonably receive either of two codes), assign the best-fit code and add a "?" flag with a brief note explaining the ambiguity. e. A passage may receive multiple codes. Multi-coding is expected.
- If pass_number is 1: note any themes that appear in the interviews but are not captured by any existing code. For each emergent candidate, record a proposed name, definition, one supporting passage, and a suggested family.
- Compile the coding record for all interviews in the batch.
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 · 80 lines · 0 tokens per session scan A b8cf207719bf
interview-coder is an agent published in the GitHub repository nanparth/ai-skill-hub (23 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 950 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.