Borrowing it
Nothing to install: this file belongs to farrelfatah/nextjobkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/farrelfatah/nextjobkit/main/.agents/skills/prepare-interview/SKILL.mdgit clone --depth 1 https://github.com/farrelfatah/nextjobkitWrote 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/skills/farrelfatah/nextjobkit/prepare-interview)<a href="https://agentmods.dev/skills/farrelfatah/nextjobkit/prepare-interview"><img src="https://agentmods.dev/badge/skills/farrelfatah/nextjobkit/prepare-interview.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.1 | $0.00059 | $0.00631 |
| Opus 5 | $0.00030 | $0.00316 |
| Sonnet 5 | $0.00012 | $0.00126 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
prepare-interview 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 6d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Interview
Prepare the candidate to defend the application they actually submitted.
Source Order
- Read
profile/candidate.md. - Read the configured evidence file.
- Read the job listing and job-fit analysis.
- Read the exact submitted resume, cover letter, and application answers when known.
- Mark prepared-but-unconfirmed artifacts as unverified rather than treating them as submitted.
If the analysis or submitted artifacts do not exist, produce a clearly labeled draft from the available sources, list what is missing, and never imply the master resume was submitted.
Prefer artifact paths supplied by the user. Otherwise search applications/, tailored/, and cover-letters/ using the candidate slug, company, role family, and date; if multiple plausible submitted packages remain, ask which one was sent rather than guessing.
Build the Brief
Produce:
- A 30–60 second introduction.
- The role's likely evaluation themes.
- Five to eight likely questions.
- A compact story bank mapped to those questions.
- Portfolio or project talking points.
- Credible answers for gaps, transitions, or adjacent experience.
- Questions the candidate should ask.
- Claims and details that must not be overstated.
Reference the evidence entry or application artifact behind every recommended story using [Source: relative/path.md — Section]. For an unsupported evaluation theme, add a discovery question or an honest gap response instead of manufacturing a bridge story.
Story Standard
Use evidence-backed STAR or decision narratives:
- Situation: only the context needed.
- Task: the candidate's actual responsibility.
- Action: decisions, artifacts, collaboration, and trade-offs.
- Result: measured or concrete qualitative outcome.
- Reflection: what changed in the candidate's approach when useful.
Do not force every story into a theatrical STAR script. Preserve natural speech.
Speakability
- Prefer short sentences and concrete nouns.
- Default answers to 45–90 seconds.
- Include a shorter recruiter-screen version where useful.
- Avoid memorization-heavy prose and unexplained jargon.
- Keep quantitative details to numbers the candidate is comfortable defending.
- Do not invent company or product familiarity. Location does not establish work authorization.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 73 lines · 59 tokens per session scan A 86ff2d3be353
prepare-interview is a skill published in the GitHub repository farrelfatah/nextjobkit (5 stars, last pushed 16d ago), licensed MIT. It adds 59 tokens to every session and 631 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…