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 negotiate-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/negotiate-offer)<a href="https://agentmods.dev/skills/tmargolis/career-navigator/negotiate-offer"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/negotiate-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/negotiate-offer"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/negotiate-offer.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.01487 |
| Opus 5 | $0.00018 | $0.00744 |
| Sonnet 5 | $0.00007 | $0.00297 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
negotiate-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 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run negotiate-offer to draft send-ready negotiation messaging in the
user's voice using:
- persisted
OfferContextfromevaluate-offerwhen available - otherwise, minimal collection + fresh market benchmark
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:
{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 one offer being negotiated){user_dir}/CareerNavigator/contacts/<company-slug>.json(the recipient of the negotiation message){user_dir}/CareerNavigator/offer-context-{application_id}.json(if present)
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 required files are missing, output:
Negotiation skipped: run
/career-navigator:launchto initializeCareerNavigator/.
2. Identify which offer to negotiate
Preferred path:
- If a user message includes
companyandrole(or job link / deadline), match them to atracker.jsonsummary row wherestatusis"offer".
If there is exactly one "offer" row in the tracker: use it.
If multiple offer applications exist and matching is ambiguous:
- ask for ONE clarification question: "Which company/role offer are we negotiating?"
Set application_id from the row's id, and keep its application label, detail_file,
contacts_file, contact_count, latest_stage, and latest_stage_date.
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 · 141 lines · 36 tokens per session scan A 22ff94bdfb5b
negotiate-offer is a skill published in the GitHub repository tmargolis/career-navigator (13 stars, last pushed 13d ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,487 once invoked, about $0.0002 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…
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…