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/tam159/next-role/interview-coachnpx skills add tam159/next-role --skill interview-coachgit clone --depth 1 https://github.com/tam159/next-roleWrote 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/tam159/next-role/interview-coach)<a href="https://agentmods.dev/skills/tam159/next-role/interview-coach"><img src="https://agentmods.dev/badge/skills/tam159/next-role/interview-coach.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.00058 | $0.00967 |
| Opus 5 | $0.00029 | $0.00483 |
| Sonnet 5 | $0.00012 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
interview-coach 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Coach
Give the candidate everything they need to walk into the interview rounds prepared.
Inputs
The caller passes exact filesystem paths in the task description:
resume_path— the candidate's processed resumejd_path— the processed job descriptionintake_path— optional intake notes (especially: prep timeline, interview process)research_path— the hiring-recon reportoutput_path— where to write the prep doc
Read all four input files in full with read_file(path, limit=1000).
Determining the rounds
Check the intake for an interview process (e.g. "recruiter screen → hiring-manager → tech → onsite"). If present, prep every named round.
If no round info is given, default to a 3-round taxonomy:
- Recruiter screen (logistics, fit, salary expectations)
- Hiring-manager behavioral (leadership, problem-solving, motivation)
- Technical / role-specific (deep skills check)
If the prep timeline is short (< 3 days), prepend a ## Triage section recommending the 2 rounds to focus on.
Output structure
# Interview prep — <Role> at <Company>
_Captured <UTC date>_
## Self-introduction
**60-second elevator pitch** (~120 words):
> <first-person: role identity → 2 strongest accomplishments → why this company/role specifically, informed by the research's Company snapshot>
**30-second short version** (~60 words):
> <same arc, less detail — used when interviewer says "keep it brief">
_These two versions are reused across every round. Do not rewrite per round._
## Triage ← include only if prep timeline < 3 days
- Focus on: <Round X>, <Round Y>
- Reason: <one short line>
## Round-by-round prep
### Round 1 — <Name> (<format>)
**Likely question themes:**
- <Pick 2-3 from: Leadership / Problem-solving / Collaboration / Achievement / Failure & growth / Role-specific>
**STAR stories ready (3-5):**
1. **<Story title>** — maps to: <theme>
- **Full (~2 min):** S — ... | T — ... | A — ... | R — ...
- **Short (~60 sec):** <condensed>
2. ...
**Questions to ask back (2-3):**
- <question grounded in research's Hiring team / Reputation>
- ...
**Watch-outs:**
- <risk from research's Reputation & culture, and how to navigate>
### Round 2 — <Name> (<format>)
...
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 · 93 lines · 58 tokens per session scan A c293e89ea726
interview-coach is a skill published in the GitHub repository tam159/next-role (49 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 967 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-30.
Other skills, from other repositories
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
blog-post
Writes and structures long-form blog posts, creates tutorial outlines, and optimizes content for SEO with cover image generation. Use when the user asks to write a blog post, article, how-to guide, tutorial, technical writeup, thought leadership piece, or long-form content.
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.
principal-agent
当用户选择职业/组织/合作方式、困惑「为什么大公司磨洋工/小公司拼命」「该不该自己干」时调用。 核心理念: 委托人(主人)会把事做好, 代理人会为自己利益优化; 收益与创造价值绑得越紧, 越像委托人; 别让媒体洗脑你需要代理人。 不适用于: 具体薪酬谈判数字、组织架构设计细节。 Triggers: 激励/代理/主人/打工 vs 创业/利益绑定/principal/agent/incentive.
gsd-milestone-summary
Generate a comprehensive project summary from milestone artifacts for team onboarding and review.
gsd-help
Show available GSD commands and usage guide.