analyze

analyze is a command for coding agents from noamseg/interview-coach-skill. It costs 0 tokens per session (4,033 once invoked), scanned C, original, MIT.

A transcript-analysis workflow for reviewing recorded job interviews. It infers useful context from the questions, then scores the conversation and explains the evidence behind the assessment.

In plain words
What is it for?
It helps analyse interview transcripts, assess answers against the target role and seniority, map answers to career stories when available, and identify areas for improvement.
Why use it?
It lets you get useful feedback even when you have not completed the full coaching setup. It also identifies where missing role or seniority context may affect the assessment.

Command

About the project

Interview Coach is a Claude Code-based coaching system for the full job-search process, including job-description analysis, application materials, interview practice, answer evaluation, and offer negotiation. It is intended for job seekers who want tailored feedback and structured preparation based on their own experience and interview transcripts. Its catalogue entry consists of commands, a setting, and a skill that provide the coaching workflows.

noamseg/interview-coach-skill · 2,112 stars · on GitHub

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/noamseg/interview-coach-skill/analyze
Clone the repo
git clone --depth 1 https://github.com/noamseg/interview-coach-skill

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/noamseg/interview-coach-skill/analyze.svg)](https://agentmods.dev/commands/noamseg/interview-coach-skill/analyze)
Your own site
<a href="https://agentmods.dev/commands/noamseg/interview-coach-skill/analyze"><img src="https://agentmods.dev/badge/commands/noamseg/interview-coach-skill/analyze.svg" alt="Measured on agentmods" height="20"></a>
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 4,033 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.04033
Opus 5 $0.00000 $0.02017
Sonnet 5 $0.00000 $0.00807
Haiku 4.5 $0.00000 $0.00403

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

Security

Grade C, and why

analyze scanned grade C with 1 finding 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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

If a candidate drops a transcript without having run `kickoff` first, don't refuse or force kickoff — but collect the minimum needed for a useful analysis:
references/commands/analyze.md · 207 lines

How it starts

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

analyze — Transcript Analysis Workflow

Use references/transcript-processing.md as execution guide.

Cold Start (No Coaching State)

If a candidate drops a transcript without having run kickoff first, don't refuse or force kickoff — but collect the minimum needed for a useful analysis:

  1. Infer what you can from the transcript. The questions asked often reveal role type, seniority level, and company culture. Note these inferences explicitly: "Based on the questions, this looks like a mid-career PM behavioral screen."
  2. Ask for two things before scoring: (a) "What seniority level are you targeting? This affects how I calibrate scores." (b) "What role/company is this for? Even brief context helps me assess Relevance."
  3. Proceed with analysis. Use inferred or stated seniority band for calibration. Skip story-mapping sections (no storybank exists). Skip cross-referencing with prep data.
  4. After the analysis, suggest kickoff: "I've scored this transcript, but I'm working without your full context — no storybank, no coaching history, no target company profile. If you want to get the most from this system, run kickoff to set up your coaching profile. Your analysis scores will carry forward."

Comp Call Detection

Before running the standard transcript analysis below, scan for compensation-discussion markers. Comp calls are structurally different from interviews and should not be scored on the interview rubric.

Detection logic. Count occurrences of these markers (case-insensitive): salary, base, equity, bonus, offer, package, counter, negotiate, compensation, vesting, sign-on, stock, RSU, pro-rate, band, range, budget.

  • 3+ distinct markers → route to negotiation-specific analysis: score against the 5 Negotiation Performance Dimensions in references/commands/negotiate.md ("Comp Call Scoring"), not the standard interview rubric. Output the Negotiation Performance Scorecard. Write results to the Comp Strategy section of coaching_state.md (not Score History — comp calls aren't interviews).
  • Fewer than 3 markers → proceed with the standard Step Sequence below.

Read the full file on GitHub · 207 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 · 207 lines · 0 tokens per session scan C 624770e65979

Subscribe to this mod's changes

analyze is a command published in the GitHub repository noamseg/interview-coach-skill (2,112 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,033 tokens. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.