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 commands/animalzinc/claude-plugins/analyze-interviewsgit clone --depth 1 https://github.com/animalzinc/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/commands/animalzinc/claude-plugins/analyze-interviews)<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>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 | $0.00011 | $0.02075 |
| Opus 5 | $0.00005 | $0.01038 |
| Sonnet 5 | $0.00002 | $0.00415 |
| Haiku 4.5 | $0.00001 | $0.00208 |
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.
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.mdorideal-customer-profile.mdresearch-goals.mdorobjectives.mdmethodology.mdcustomer-profile.mdorpersona.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
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.
- 5d ago First seen · 365 lines · 0 tokens per session scan A 1579eca15ed6
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.
Other commands, from other repositories
brand-setup
Configure brand voice, terminology, compliance guardrails, and style guide for content production.
resume
Resume a ContentForge pipeline run that was interrupted partway through.
output-folder
Print the absolute path to the user-visible ContentForge output folder and open it in the OS file manager.
create-content
Run the full 10-phase content production pipeline — research, draft, fact-check, humanize, and publish.
audit-content
Audit your content library for freshness decay, coverage gaps, and optimization opportunities.
publish
Publish finished content to Webflow or WordPress with preview, verification, and HTML export fallback.