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/tmargolis/career-navigator/reportnpx skills add tmargolis/career-navigator --skill reportgit clone --depth 1 https://github.com/tmargolis/career-navigatorWrote 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/tmargolis/career-navigator/report)<a href="https://agentmods.dev/skills/tmargolis/career-navigator/report"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/report.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 | $0.00076 | $0.02048 |
| Opus 5 | $0.00038 | $0.01024 |
| Sonnet 5 | $0.00015 | $0.00410 |
| Haiku 4.5 | $0.00008 | $0.00205 |
Grade A, and why
report 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 5d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invoke the analyst agent to run all three operations and deliver the integrated insight report.
Workflow
1. Confirm data exists
Application data uses the split layout defined in references/tracker-schema.md — read it before any read or write.
Read {user_dir}/CareerNavigator/tracker.json, {user_dir}/CareerNavigator/ExperienceLibrary.json, {user_dir}/CareerNavigator/profile.md, and {user_dir}/CareerNavigator/artifacts-index.json. If the ExperienceLibrary is empty:
"Your ExperienceLibrary is empty. Run
/career-navigator:add-sourceto add a resume first."
If the tracker has no applications, note this inline — pattern analysis will be limited but the other two operations can still run.
tracker.json now holds summary rows only. Operations 2 and 3 (transferable strengths, AI displacement) run off those rows plus the ExperienceLibrary and need nothing else. Operations 1 and 4 (outcome patterns, market benchmark) reason over stage transitions and note text, which live in the per-application detail files — so before the handoff, collect {user_dir}/CareerNavigator/ + detail_file for every summary row with stage_count greater than 0 or outcome != "pending", and skip the rest. Do not load contacts files; no analyst operation uses them.
1.5 Ensure ATS scores exist (resume artifacts)
Read {user_dir}/CareerNavigator/artifacts-index.json.
If any artifact with type: "resume" is missing ats_score (or has ats_score: null):
- Invoke
resume-scorefor that resume artifact (reference itsfilenameso the skill can look it up and run the ATS check pass). - If keyword coverage can’t be computed due to missing JD context, still proceed with formatting/narrative ATS checks and write whatever
ats_scorethe ATS pass can compute. - Re-check
{user_dir}/CareerNavigator/artifacts-index.jsonafter the ATS pass(es). If scores are still missing, note the remaining ATS gaps in the report highlights.
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.
- 5d ago First seen · 148 lines · 76 tokens per session scan A 8d5720161f9e
report is a skill published in the GitHub repository tmargolis/career-navigator (13 stars, last pushed 6d ago), licensed Apache-2.0. It adds 76 tokens to every session and 2,048 once invoked, about $0.0004 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
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…