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 tmargolis/career-navigator --skill evaluate-offergit 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/evaluate-offer)<a href="https://agentmods.dev/skills/tmargolis/career-navigator/evaluate-offer"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/evaluate-offer/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/tmargolis/career-navigator/evaluate-offer"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/evaluate-offer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 69 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00051 | $0.02226 |
| Opus 5.5 | $0.00020 | $0.00890 |
| Sonnet 5.5 | $0.00010 | $0.00445 |
| Haiku 4.5 | $0.00005 | $0.00223 |
Grade A, and why
evaluate-offer 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 1mo 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run evaluate-offer to produce an honest OfferEvaluationReport and persist an
OfferContext JSON file to:
{user_dir}/CareerNavigator/offer-context-{application_id}.json
so negotiate-offer and compare-offers can consume it later.
Workflow
Directory sharing (host integration)
If the host UI asks you for a directory to share with an agent during this
skill's run, share only your {user_dir} job-search folder (the one
containing CareerNavigator/).
This skill reads/writes:
{user_dir}/CareerNavigator/profile.md{user_dir}/CareerNavigator/ExperienceLibrary.json{user_dir}/CareerNavigator/tracker.json(summary rows){user_dir}/CareerNavigator/applications/<application_id>.json(the offer application'snotes[]+stage_history[]){user_dir}/CareerNavigator/contacts/<company-slug>.json(that company's contacts, when recruiter context matters){user_dir}/CareerNavigator/offer-context-{application_id}.json
Do not share the whole workspace or unrelated folders.
1. Confirm required 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/profile.md{user_dir}/CareerNavigator/ExperienceLibrary.json{user_dir}/CareerNavigator/tracker.json
If missing required files, output:
Offer evaluation skipped: run
/career-navigator:launchto initializeCareerNavigator/.
2. Identify the offer-stage application
From the tracker.json summary rows, find applications where:
statusis"offer"
Cases:
- If exactly one such application exists: use its
idasapplication_id. - If multiple exist: ask for the company and role (or the job link / deadline) and pick the matching application.
- If none exist: ask the user to log the offer first via
/career-navigator:track-application.
Keep from the matched row: application (the "<company> — <role>" label), detail_file,
contacts_file, latest_stage, latest_stage_date, notes_count, stage_count. Then
read {user_dir}/CareerNavigator/ + detail_file for this one application — its
stage_history[] and notes[] are the interview record the evaluation reasons over, and
they no longer exist inside tracker.json. Do not load detail files for any other
application.
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.
- 1mo ago First seen · 205 lines · 51 tokens per session scan A 2e0872c11a3d
evaluate-offer is a skill published in the GitHub repository tmargolis/career-navigator (16 stars, last pushed 27d ago), licensed Apache-2.0. It adds 51 tokens to every session and 2,226 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…