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/launchnpx 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.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.00116 | $0.10533 |
| Opus 5 | $0.00058 | $0.05267 |
| Sonnet 5 | $0.00023 | $0.02107 |
| Haiku 4.5 | $0.00012 | $0.01053 |
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 4d 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 — 621 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.
- 4d ago First seen · 621 lines · 116 tokens per session scan A 81c365054ffc
launch is a skill published in the GitHub repository tmargolis/career-navigator (14 stars, last pushed 5d ago), licensed Apache-2.0. It adds 116 tokens to every session and 10,533 once invoked, about $0.0006 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
simulator-reactions
Simulator.Company reactions specialist — comments, events, approvals, ratings and other feedback attached under an actor. Use when the user wants to comment on an actor, reply in a thread, read/like/pin the discussion, mark comments read, or get reaction stats. Activate when the user says "comment on this actor"…
glab-issue
Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…