interview-prep

interview-prep is a skill for Claude Code from Miracle-Aligner/job-search-hq. It costs 109 tokens per session (777 once invoked), scanned A, original, MIT.

An interview-preparation workflow for Job Search HQ, a system that tracks job applications and interview events. It creates a focused brief using the vacancy, candidate profile, résumé evidence, interview details, and current company research.

In plain words
What is it for?
Use it to prepare company and role summaries, likely discussion points, evidence from past projects, questions to ask, and guidance for the specific interview format.
Why use it?
It gathers the relevant preparation material in one place and adjusts the depth to the interview stage, from an initial recruiter call to a technical or final round.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/validate.py.

Part of the job-search-hq plugin — 9 skills shipped together

Good fit Use it to prepare company and role summaries, likely discussion points, evidence from past projects, questions to ask, and guidance for the specific interview format.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Miracle-Aligner/job-search-hq
agentmods
npx agentmods add skills/miracle-aligner/job-search-hq/interview-prep

Made for: Claude Code.

Or install job-search-hq, the plugin that ships this one along with the rest of its 9 skills.

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 interview-prep

README.md
[![agentmods](https://agentmods.dev/badge/skills/miracle-aligner/job-search-hq/interview-prep/github.svg)](https://agentmods.dev/skills/miracle-aligner/job-search-hq/interview-prep)
Your own site
<a href="https://agentmods.dev/skills/miracle-aligner/job-search-hq/interview-prep"><img src="https://agentmods.dev/badge/skills/miracle-aligner/job-search-hq/interview-prep/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for interview-prep

Your own site · 80×15
<a href="https://agentmods.dev/skills/miracle-aligner/job-search-hq/interview-prep"><img src="https://agentmods.dev/badge/skills/miracle-aligner/job-search-hq/interview-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 777 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00109 $0.00777
Opus 5 $0.00055 $0.00388
Sonnet 5 $0.00022 $0.00155
Haiku 4.5 $0.00011 $0.00078

Measured 9d ago against content hash 6ac9e7960f8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

interview-prep 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 9d 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.

.claude/skills/interview-prep/SKILL.md · 62 lines

How it starts

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

interview-prep

Produce one self-contained brief that gives the candidate everything to walk in prepared. Invoked standalone (/interview-prep <id> [eventId]) or from /update-status when an interview is scheduled.

Inputs (read these first)

  • The vacancy in data/vacancies.json — role, JD recap (summary, plus, minus), score/ss, statusDetail, the target event (stage, time, via, interviewer if noted).
  • profile/candidate.md + profile/profile.json — strengths, gaps, comp/level targets.
  • The CV digests (/ingest-cv) — concrete projects, metrics, evidence to cite.
  • Live researchWebSearch + WebFetch the company: what they do, product, stage/funding, recent news (last ~6 months), tech signals, Glassdoor-style interview-format hints. Cite nothing you didn't actually find; mark unknowns as unknown.

The brief (markdown → events[].prep)

Tailor depth to the stage (HR screen = light; tech/final = deep). Cover:

  1. Company snapshot — what they do, product, stage/size, 2–3 recent developments.
  2. Role & JD recap — the 3–5 things this role actually needs; how the candidate maps.
  3. Stage & format — what this round is (recruiter / tech / system design / final), who's on it if known, likely structure and length.
  4. Likely questions — behavioral + technical, tailored to the JD stack and the candidate's gaps. Make them specific to this company/role, not generic.
  5. Strong talking points — mapped to concrete CV evidence (project, metric, outcome).
  6. Gap defense — for each real gap (from the profile), an honest, confident framing.
  7. Smart questions to ask them — sharp, role/company-specific.
  8. Comp & level context — the candidate's target band vs this role; a negotiation anchor.
  9. Logistics — date/time, via, meeting URL, what to have open.

Keep it tight and skimmable (headers + bullets). It's a cheat-sheet, not an essay.

Persist

Write the markdown to the target event's prep field in data/vacancies.json (vacancies[i].events[j].prep). If no specific event, attach to the soonest upcoming interview-kind event, or create a follow-up event to hold it and say so.

Read the full file on GitHub · 62 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. 9d ago First seen · 62 lines · 109 tokens per session scan A 6ac9e7960f8d

Subscribe to this mod's changes

interview-prep is a skill published in the GitHub repository Miracle-Aligner/job-search-hq (1 stars, last pushed 3mo ago), licensed MIT. It adds 109 tokens to every session and 777 once invoked, about $0.0005 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-31.