analyze-interviews

analyze-interviews is a command for coding agents from animalzinc/claude-plugins. It costs 11 tokens per session (2,075 once invoked), scanned A, original, MIT.

A command that reads interview transcript files and produces a report of recurring themes and ranked insights.

In plain words
What is it for?
Use it to scan a directory of text, Markdown, Word, or DOCX transcripts, check what was found, and analyse the collection after confirmation.
Why use it?
It reduces the manual work of reviewing many transcripts and helps keep findings tied to research context such as goals or customer profiles.

Command

Part of the interview-transcript-analyzer plugin — 3 commands, 3 agents shipped together

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 commands/animalzinc/claude-plugins/analyze-interviews
Clone the repo
git clone --depth 1 https://github.com/animalzinc/claude-plugins

Or install interview-transcript-analyzer, the plugin that ships this one along with the rest of its 3 commands, 3 agents.

Wrote 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.

agentmods badge for analyze-interviews

README.md
[![agentmods](https://agentmods.dev/badge/commands/animalzinc/claude-plugins/analyze-interviews.svg)](https://agentmods.dev/commands/animalzinc/claude-plugins/analyze-interviews)
Your own site
<a href="https://agentmods.dev/commands/animalzinc/claude-plugins/analyze-interviews"><img src="https://agentmods.dev/badge/commands/animalzinc/claude-plugins/analyze-interviews.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,075 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.00011 $0.02075
Opus 5 $0.00005 $0.01038
Sonnet 5 $0.00002 $0.00415
Haiku 4.5 $0.00001 $0.00208

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

Security

Grade A, and why

analyze-interviews 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 5d 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.

plugins/interview-transcript-analyzer/commands/analyze-interviews.md · 365 lines

How it starts

The opening of the file, as written. The whole thing — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyze Interview Transcripts

Analyze all interview transcripts in a directory, extract themes, rank insights, and generate a comprehensive report.

Step 1: Discover and Validate Transcripts

Scan the transcripts directory ($2):

  • Find all text files (.txt, .md, .doc, .docx)
  • Count total transcripts
  • Calculate total file size and estimated token count
  • Identify any context files (ICP, research goals, methodology docs)

Look for context file ($3):

  • If --context-file argument provided, read that file
  • If not provided, look for common files in directory:
    • icp.md or ideal-customer-profile.md
    • research-goals.md or objectives.md
    • methodology.md
    • customer-profile.md or persona.md

Report to user:

## 📁 Transcripts Discovered

**Directory:** $2
**Transcripts found:** [number] files
**Total size:** [size in MB]
**Estimated tokens:** ~[number]k tokens

**Files:**
- [filename 1] ([size])
- [filename 2] ([size])
- [etc.]

**Context documents found:**
- [ICP/research goals/methodology if found, or "None"]

Would you like to proceed with analysis?

Wait for user confirmation.


Step 2: Determine Agent Scaling Strategy

Based on workload, intelligently determine how many parallel agents to use:

Agent Scaling Logic:

If 1-3 transcripts:
  → Use 1 agent (sequential analysis is fine)

If 4-8 transcripts:
  → Use 3 parallel agents
  → Divide transcripts evenly (e.g., Agent 1: transcripts 1-3, Agent 2: 4-6, Agent 3: 7-8)

If 9-15 transcripts:
  → Use 5 parallel agents
  → Divide transcripts evenly

If 16+ transcripts:
  → Use 8 parallel agents (optimal for most systems)
  → Divide transcripts evenly

ALSO consider total token count:
If total tokens > 150k:
  → Increase agent count by 1-2
  → Example: 6 transcripts but 200k tokens → use 5 agents instead of 3

If total tokens < 30k:
  → Decrease agent count
  → Example: 10 short transcripts with 25k tokens → use 3 agents instead of 5

Present strategy to user:

## 🤖 Agent Strategy

Based on [number] transcripts totaling ~[number]k tokens, I recommend using **[number] parallel agents** for efficient analysis.

**How it works:**
- Each agent will analyze [number] transcripts
- Agents work simultaneously (faster than sequential)
- All findings will be synthesized into final report

**Agent assignments:**
- Agent 1: [transcript names]
- Agent 2: [transcript names]
- [etc.]

**Estimated time:** [minutes] minutes

Would you like to:
1. ✅ Proceed with this strategy
2. 🔄 Adjust agent count (tell me your preference)
3. ❌ Cancel

Read the full file on GitHub · 365 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. 5d ago First seen · 365 lines · 0 tokens per session scan A 1579eca15ed6

Subscribe to this mod's changes

analyze-interviews is a command published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 15d ago), licensed MIT. It adds 11 tokens to every session and 2,075 once invoked, about $0.0001 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.