Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add palashjain95/jobhunter/plugin install jobhunterWrote 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/palashjain95/jobhunter/mock-interview)<a href="https://agentmods.dev/skills/palashjain95/jobhunter/mock-interview"><img src="https://agentmods.dev/badge/skills/palashjain95/jobhunter/mock-interview/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.
<a href="https://agentmods.dev/skills/palashjain95/jobhunter/mock-interview"><img src="https://agentmods.dev/badge/skills/palashjain95/jobhunter/mock-interview.svg" alt="Reviewed on agentmods" width="80" 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.00782 |
| Opus 5 | $0.00030 | $0.00391 |
| Sonnet 5 | $0.00012 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
mock-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 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mock-interview
Usage
/mock-interview <company name + role>
/mock-interview <company name + role> behavioral
Inputs
- Which company and role (to tailor questions)
- Interview type: behavioral / technical / case / mixed
- knowledge/profile.md — candidate context
- knowledge/stories/ — to evaluate if stories are used well
- knowledge/frameworks/writing-framework.md — to evaluate structure
- If available: output/[company]/interview-prep.md — prepared questions
- ${CLAUDE_PLUGIN_ROOT}/.claude/resources/ — detect the company or career path and load the matching framework. Search companies/ (e.g. amazon.md), then paths/ (e.g. consulting.md for case + PEI, pe.md for deal discussion), then general.md as fallback.
How to Run
Setup
Tell the user: "I'll ask you questions one at a time. Answer as if you're in the real interview. After each answer, I'll give brief feedback. At the end, I'll give a full assessment."
During the Interview
- Ask 5-7 questions, one at a time
- Mix behavioral + role-specific + curveball
- Start easy, escalate difficulty
- Include at least one question the candidate is likely weak on
- Ask follow-ups like a real interviewer would
After Each Answer
Give brief feedback (2-3 sentences):
- What worked
- What to adjust
- Rating: Strong / Good / Needs Work
Output Format (Final Assessment)
## Mock Interview Assessment: [Company] — [Role]
**Overall:** Ready / Almost Ready / Needs More Practice
### Strongest Answer
[Which question and why it worked]
### Weakest Answer
[Which question, why it fell short, suggested rewrite]
### Patterns
[Recurring strengths or issues across answers]
### Story Usage
[Did they use prepared stories effectively? Missed opportunities?]
### Framework Adherence
[Did answers follow their writing/communication framework?]
### Top 3 Fixes Before the Real Interview
1. [specific, actionable fix]
2. [specific, actionable fix]
3. [specific, actionable fix]
If Something Goes Wrong
- User gives very short answers: Prompt like a real interviewer — "Can you tell me more about...?" Push for specifics.
- User goes over 2 minutes on an answer: Flag it — "That ran long. In a real interview, aim for 90 seconds."
- No company framework found: Use general behavioral format. Note it.
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.
- 9d ago First seen · 99 lines · 59 tokens per session scan A 8f3343d0b858
mock-interview is a skill published in the GitHub repository palashjain95/jobhunter (2 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 782 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
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
examples
Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
intro
Walk through the Elixir/Phoenix plugin commands, workflow, and features in 6 interactive sections. Use when a new user wants to learn what the plugin offers or needs a refresher on available commands.
learning-and-development
Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.
top-one-percent
Teach any topic deeply from first principles and build evidence-based paths toward exceptional capability. Use when a user asks to understand, explain, learn, or deep-dive into a topic; asks why or how something works, why it matters, how alternatives compare, or what different perspectives reveal; requests current…