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 salary-researchgit 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/salary-research)<a href="https://agentmods.dev/skills/tmargolis/career-navigator/salary-research"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/salary-research/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/salary-research"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/salary-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.01726 |
| Opus 5 | $0.00034 | $0.00863 |
| Sonnet 5 | $0.00013 | $0.00345 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
salary-research 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 11d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull live salary data for a role and location via the Apify MCP server and return a structured compensation summary.
Preflight check
Before doing anything else, confirm Apify MCP tools are available in this session (e.g. Call Actor, Get Actor run, Get dataset items). They appear when the user adds the Apify Desktop connector in Claude Customize → Connectors, pastes their token in the connector UI (not in chat), and sets Enabled tools to:
call-actor,get-actor-run,get-dataset-items,cheapget/best-job-search
If those tools are not available:
"Salary benchmarking needs the Apify Desktop connector. In Claude Desktop: Customize → Connectors → Desktop → Apify → Configure — add your Apify token, set Enabled tools to
call-actor,get-actor-run,get-dataset-items,cheapget/best-job-search, save, enable the connector, then open a new chat and try again. Or run/career-navigator:launchStep 4 for the full walkthrough."
Stop here — do not proceed without the MCP connection.
Workflow
1. Collect inputs
Extract the following from the conversation. Do not ask for anything already stated:
| Input | Source | Required |
|---|---|---|
keyword |
Job title from conversation or ## Target Roles in profile.md |
Required |
location |
Location from conversation or ## Location in profile.md |
Required |
remoteOnly |
Mentioned by user ("remote only", "fully remote") | Optional |
minSalary |
Mentioned by user ("above $120k", "minimum $150k") | Optional |
If keyword or location cannot be determined from context or profile, ask for them together in a single prompt:
"What role and location should I pull salary data for? (e.g., 'Senior Product Manager in Chicago')"
2. Call the Apify actor
Use the Apify MCP call-actor tool with the following parameters:
- Actor ID:
cheapget/best-job-search - Input:
{
"keyword": "<role title>",
"location": "<city, state or country>",
"maxResults": 25,
"remoteOnly": <true if specified, omit otherwise>,
"minSalary": <integer if specified, omit otherwise>
}
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.
- 11d ago First seen · 153 lines · 67 tokens per session scan A bf96f0d4cbfd
salary-research is a skill published in the GitHub repository tmargolis/career-navigator (13 stars, last pushed 12d ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,726 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-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…
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…