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 jain777/jobclaw-skills --skill map-career-pathgit clone --depth 1 https://github.com/jain777/jobclaw-skillsWrote 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/jain777/jobclaw-skills/map-career-path)<a href="https://agentmods.dev/skills/jain777/jobclaw-skills/map-career-path"><img src="https://agentmods.dev/badge/skills/jain777/jobclaw-skills/map-career-path/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/jain777/jobclaw-skills/map-career-path"><img src="https://agentmods.dev/badge/skills/jain777/jobclaw-skills/map-career-path.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.00063 | $0.01042 |
| Opus 5 | $0.00032 | $0.00521 |
| Sonnet 5 | $0.00013 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
map-career-path 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 12d 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.
map-career-path
Show the user how others made the move, and where they'd need to grow. Hard rules: ../_shared/RULES.md.
Inputs
- current_role (required).
- target_role (required).
- Profile —
profile/master-profile.md(for the gap analysis). - Optional region —
--region US | IN(else use profile'starget.regions).
Method
-
Resolve the search backend.
- If
GOOGLE_API_KEY+CSE_IDenv vars are present →
python3 scripts/career_paths.py --current "<X>" --target "<Y>" --region <code>(CSE-driven; better recall + structured snippets). - Else →
WebSearchwith the same 4 query templates the script uses.
Either path returns up to 10 transition examples.
- If
-
Query templates (the script + the WebSearch fallback use identical queries):
"<current>" "<target>" site:linkedin.com/infrom "<current>" to "<target>" site:linkedin.com"<target>" "previously <current>" site:linkedin.comcareer transition "<current>" "<target>"(broader, no site restriction)
-
Filter for relevance. Keep entries where the snippet/title shows both the current and target role (or near-synonyms — "Product Manager" matches "Sr. PM"). Dedup by canonical URL. Drop entries with no transition signal.
-
Synthesize patterns. Across the kept profiles, surface 3–5 common patterns (e.g., "most PM → Director moves went through a 1–2 yr 'Group PM' stint"; "AI Engineer transitions usually start with shipping one production LLM project at the current role"). Patterns must be observable in the snippets — don't generalize beyond evidence.
-
Personalize the roadmap against the user's profile:
- You already have: items the profile evidences.
- Build next: specific, measurable skills/experiences (e.g., "ship one LLM-eval doc in the current role"; not "get more AI experience").
- Soft signals (optional): writing, speaking, OSS, certifications — only real, named ones.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 99 lines · 63 tokens per session scan A 646a52aa01f3
map-career-path is a skill published in the GitHub repository jain777/jobclaw-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,042 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…