interview-coder

A qualitative research tool that reads interview transcripts and marks which topics from a supplied codebook appear in each one. It records supporting passages, uncertainty, and possible new themes.

In plain words
What is it for?
Use it to code batches of interview files into structured JSON records for later analysis. It is also for finding themes that the current codebook does not cover during a first review.
Why use it?
It reduces the manual work of applying the same topic labels consistently across many interviews. It also keeps evidence attached to each label without adding interpretations or conclusions.

Agent

Install

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.

agentmods
npx agentmods add agents/nanparth/ai-skill-hub/interview-coder
Clone the repo
git clone --depth 1 https://github.com/nanparth/ai-skill-hub
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 950 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash b8cf207719bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

biz-interview/agents/interview-coder.md · 80 lines

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

  1. Read the codebook fully. Internalise the inclusion and exclusion criteria for every code.
  2. Sort your interview batch into alternating order by customer side (one demand-side, one supply-side, alternating). Within each side, sort by interview number.
  3. 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.
  4. 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.
  5. Compile the coding record for all interviews in the batch.

Read the full file on GitHub · 80 lines

Changes

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.

  1. 2d ago First seen · 80 lines · 0 tokens per session scan A b8cf207719bf

Subscribe to this mod's changes

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.