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 launchgit 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/launch)<a href="https://agentmods.dev/skills/tmargolis/career-navigator/launch"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/launch/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/launch"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/launch.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 Agent Snooping · line 501 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00116 | $0.10335 |
| Opus 5.5 | $0.00046 | $0.04134 |
| Sonnet 5.5 | $0.00023 | $0.02067 |
| Haiku 4.5 | $0.00012 | $0.01034 |
Grade A, and why
launch 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 27d 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 — 614 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this after installing the plugin — it is how you launch Career Navigator: registering your job search folder, reading your existing documents, building your profile and ExperienceLibrary, and configuring integrations (the same setup flow as before, framed as starting your search).
The working directory (or relevant sub-directory) should be configured as the user's job search directory to be referred to as {user_dir}. All data this plugin produces— profile, ExperienceLibrary, tracker, generated artifacts — lives in subdirectories of the {user_dir} folder alongside the user's raw documents.
Integrations (Indeed, Apify, LinkedIn, Gmail, Microsoft 365, Google Calendar): Follow CONNECTORS.md: only prompt for services that are not already connected in this session (host tools missing or user reports a problem). If tools are already present, a brief acknowledgment is enough—do not ask setup, OAuth, or browser-access questions for those services.
Workflow
Connector pattern (apply to steps 3–7)
| Step | What to do |
|---|---|
| 1 — Discover | Check tools in this chat for that integration. If connected (tools present), acknowledge briefly and skip further steps for it. |
| 2 — Configure | Only if not connected: ask if they want to set up; guide CONNECTORS.md; they complete Connectors + OAuth/token. Never automate OAuth with Chrome/computer use. |
| 3 — Browser access | Only if not connected via MCP or the flow is browser-only (e.g. LinkedIn analytics). Do not ask for Indeed / Apify / inbox / calendar when MCP tools already work. |
Apply 1 → 2 → (3 only when needed) per integration—omit steps 2–3 when step 1 already succeeded.
1. Confirm job search directory
If the user provided a directory path: use it. inform the user of the path to {user_dir}
If no path was provided: ask:
"What folder should Career Navigator use for your job search? This is where your resumes and cover letters live, and where I'll save everything I generate. Start a new chat and click the "+" icon in the text box to add that folder to our chat"
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.
- 27d ago Changed · -15 lines 7867ddcf533c
- 29d ago Changed · +8 lines cc44620eceeb
- 1mo ago First seen · 621 lines · 116 tokens per session scan A 81c365054ffc
launch is a skill published in the GitHub repository tmargolis/career-navigator (16 stars, last pushed 27d ago), licensed Apache-2.0. It adds 116 tokens to every session and 10,335 once invoked, about $0.0005 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…