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 skills/suxrobgm/jobpilot/interviewnpx skills add suxrobGM/jobpilot --skill interviewgit clone --depth 1 https://github.com/suxrobGM/jobpilotWrote 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/suxrobgm/jobpilot/interview)<a href="https://agentmods.dev/skills/suxrobgm/jobpilot/interview"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/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 | $0.00029 | $0.00611 |
| Opus 5 | $0.00015 | $0.00305 |
| Sonnet 5 | $0.00006 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
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 4d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Prep
Generate interview prep tailored to a JD and the candidate's resume.
Setup
Follow ../_shared/setup.md. Then Read the resume file at primaryResumeSourceAbsolutePath for the candidate's full background.
Step 1: Analyze the Role
From the argument, identify: role title + level + team, core technical requirements, domain/industry, key responsibilities, company size/stage, any interview-process hints.
Step 2: Generate Questions
Behavioral (5–7)
Focus on competencies the role requires. For each: question + suggested STAR answer (Situation, Task, Action, Result) using a real example from the resume + the experience to reference.
Example:
**Q: Tell me about a time you led a major migration.**
Suggested answer (STAR):
- Situation: At EmTech Care Labs, the platform was on AWS Amplify Gen 1 with slow builds.
- Task: Lead the migration to Gen 2 and unify the codebase.
- Action: Phased migration, unified TypeScript monorepo, consolidated 3 component libraries into one design system.
- Result: Cut build/deploy time 40%, created 40+ reusable components, improved velocity.
Technical (5–7)
Based on the role's stack and requirements: language/framework, architecture and patterns, technologies listed in the JD. For each: concise answer outline with talking points from the candidate's experience.
System Design (2–3)
Scenarios relevant to the company's product area. For each: outline the approach + which candidate projects demonstrate relevant experience.
Company / Domain (2–3)
Questions about the company's product, industry, competitors. Suggest research areas to explore before the interview.
Step 3: Identify Weak Spots
List requirements where the candidate's experience is thin. Suggest how to frame each gap positively (transferable skills, adjacent experience, quick-learner). Recommend areas to brush up on.
Step 4: Output
# Interview Prep: [Role] at [Company]
## Role Summary
[2-3 sentences]
## Behavioral Questions
## Technical Questions
## System Design
## Company Research
## Watch Out For
## Key Talking Points
[3-5 bullets to weave into any answer]
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.
- 4d ago First seen · 77 lines · 29 tokens per session scan A 5d2478d6951c
interview is a skill published in the GitHub repository suxrobGM/jobpilot (60 stars, last pushed 14d ago), licensed MIT. It adds 29 tokens to every session and 611 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 skills, from other repositories
interview-analysis
This skill should be used when the user asks to "/interview-analysis", "analyze my interview", "debrief my interview", "what did I miss in the interview", "review my interview transcript", or pastes a transcript / notes from a just-finished interview. Reads the transcript (pasted, from --from-file, or auto-pulled from…
case-practice
This skill should be used when the user asks for "/case-practice", "/pm-job-search:case-practice", "drill me on product cases", "practice PM case interviews", "MC case drill", or "test my case-interview recognition". Runs drill 1 of the case-practice methodology — a multiple-choice (MC) rapid-recognition drill that…
interview-prep
Prepare Korean interview follow-up questions and evidence-backed answer points from resume.md, JD analysis, cover letter text, and an evidence map. Use after HR review or final cover letter drafting when the user wants 면접 준비, 꼬리질문, interview defense, or claim verification before manual submission.
interview-prep
Use when the user wants to prepare for an interview tracked in Job Search HQ. Triggers: /interview-prep, "prep me for the X interview", "interview prep for ", "help me get ready for my final round", or accepting the prompt offered by /update-status when an interview is scheduled. Researches the company live and builds…
upskill
Compares tracked job postings against the candidate profile to identify skill gaps and generate a prioritized learning plan with study resources. Triggers on: /upskill, upskill, skill gaps, what should I learn, learning plan.
engineering-onboarding
Create an onboarding guide for an engineer joining a team that consumes the design system. Trigger when someone says: onboard new engineer, developer getting started guide, new engineer guide, engineering onboarding, first day for developers, frontend onboarding, or anything about helping an engineer new to the team…