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 weekgit 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/week)<a href="https://agentmods.dev/skills/benskamps/career-compass-mcp/week"><img src="https://agentmods.dev/badge/skills/benskamps/career-compass-mcp/week/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/week"><img src="https://agentmods.dev/badge/skills/benskamps/career-compass-mcp/week.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.00034 | $0.00511 |
| Opus 5.5 | $0.00014 | $0.00204 |
| Sonnet 5.5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
week 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 a weekly review of their job search. Anything to center it on is below.
With the Career Compass tools, call pipeline_view with action: "stats" and with
action: "list", and read the journal (career://journal) and profile if the host can
read resources. Then, in this order:
- Movement: what advanced, stalled or closed this week, and where applications are getting stuck.
- Pace: applications this week against
profile.weeklyPace, in one line ("4 sent against your pace of 5"). If no pace is set, skip it. - Patterns: strengths that keep landing and gaps that keep surfacing in recent journal entries.
- A month on: one line, only when the data shows it, e.g. "A month ago your journal kept flagging no metrics; your last three fit checks didn't." Skip it otherwise.
- The honest read: one thing working to do more of, one not working to change.
- Next week's focus: the single highest-leverage bet.
Cite the application (company, role) or journal entry (date and summary) behind every claim. If you can't point to one, cut the claim.
Then offer one capture_insight (type note or fit_signal) recording the week's
takeaway, with origin: "inferred" for your read or "user_said" if it's their words.
Write it only after they say yes. If the search ended in an accepted offer, the week is
instead a win capture (capture_insight type win).
Without the tools (claude.ai chat), use their Career Compass card (pasted, or found by searching past chats when you can, as the career-compass skill describes). If there is none, ask: "Paste your Career Compass card, or this week's applications: company, role, date, stage, last contact, and any notes." Then do the same review, citing their lines, and end with the updated card.
$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 · +3 lines 1082be7c74b1
- 4d ago First seen · 37 lines · 34 tokens per session scan A 18720bb21899
week is a skill published in the GitHub repository benskamps/career-compass-mcp (6 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 511 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,"…