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 skills add benskamps/career-compass-mcp --skill debriefgit clone --depth 1 https://github.com/benskamps/career-compass-mcpWrote 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/benskamps/career-compass-mcp/debrief)<a href="https://agentmods.dev/skills/benskamps/career-compass-mcp/debrief"><img src="https://agentmods.dev/badge/skills/benskamps/career-compass-mcp/debrief/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/benskamps/career-compass-mcp/debrief"><img src="https://agentmods.dev/badge/skills/benskamps/career-compass-mcp/debrief.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.00036 | $0.00564 |
| Opus 5.5 | $0.00014 | $0.00226 |
| Sonnet 5.5 | $0.00007 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
debrief 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 2d 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.
What it actually says
The user wants to debrief an interview. Their notes are below.
- If there are no notes, ask once: "How did it go? Rough notes are fine: who you met, what they asked, what felt strong or shaky." Then stop.
- What happened: two or three lines on what the round covered and what it says about their fit and the company's process.
- What landed and what to sharpen: from their notes only. Be honest; if it went badly, say so plainly, because a hard debrief is the most useful kind.
- Thank-you notes: one short note per interviewer they named, each built only from what
their notes say was discussed with that person. Where the notes give nothing, leave a
slot like
[confirm: what you talked about with Priya]. Never invent a name, topic or moment. You draft; they send. - Next step: follow up tomorrow, plus two or three things to do before the next round.
With the Career Compass tools, then offer one batch and write it only after one yes:
capture_insight(typeinterview_insight, the company and role orapplicationId, an honestsentiment, recurring strengths or gaps assignals,origin: "user_said"). Anything that is your read rather than theirs goes in asorigin: "inferred", and say so.pipeline_update: the round (interviewType,interviewDate,interviewers,roundOutcomein their words), any status change, andfollowUpDueset to tomorrow.- Stories: offer to save a story they told that isn't in
stories, and to addusedWith(company, round, interviewer, date) to the saved ones they used.save_career_sectionreplaces the whole section, so send every story.
If another round is likely, run interview_arc for what comes next.
Without the tools (claude.ai chat), do all of the above from what they tell you, and give the follow-up date as a reminder line instead of saving anything. If they have a Career Compass card, end with it updated (the round, the follow-up date, stories told to whom); if not, offer one.
$ARGUMENTS
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.
- 2d ago Changed · +2 lines 0306005bcbbf
- 4d ago First seen · 39 lines · 36 tokens per session scan A a6615085cf41
debrief is a skill published in the GitHub repository benskamps/career-compass-mcp (6 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 564 once invoked, about $0.0001 per session on Opus 5.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-10-07.
Other skills, from other repositories
kochab
Kochab, a personalized resume-based job-search assistant that runs a recurring scan and everything downstream of it. Use when the user wants to start or run a job search, shares a resume, or says "set up my job scan," "find roles that fit my resume," or "what should I apply to." Also use to tailor a resume, draft a…
interviewing
Use when the user gets an interview invitation, moves into an interview process, wants to track interview stages, capture post-interview notes, draft follow-up messages, or update an application to interviewing.
get-started
Use when the user is new to Job Hunt Skills and wants to see what it does or set up their workspace — including "I'm new to Job Hunt Skills", "help me get started", "set me up", "first time using this", "here's my resume, tailor it for this job", "can you look at my resume", pasting a resume and a job posting…
yc-job-tracker
Track and filter YC startup job listings for AI/ML engineering roles. Builds a daily-refreshed local database of relevant jobs with scoring and alerts for new postings.
Job Description Analyzer
Analyze job postings, calculate match scores, identify gaps, and create application strategy.
opportunity-brief
Research a company and a specific role, then produce an honest brief on whether it is worth pursuing. Use this whenever the user mentions a recruiter reaching out, a job posting they found, a company someone told them about, or a role they are weighing. Triggers on "a recruiter contacted me," "should I apply to,"…