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 follow-upgit 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/follow-up)<a href="https://agentmods.dev/skills/tmargolis/career-navigator/follow-up"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/follow-up/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/follow-up"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/follow-up.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.00076 | $0.03429 |
| Opus 5 | $0.00038 | $0.01715 |
| Sonnet 5 | $0.00015 | $0.00686 |
| Haiku 4.5 | $0.00008 | $0.00343 |
Grade A, and why
follow-up 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 10d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Surface follow-up priorities for all active applications using company-specific response window data.
Data files
Application data uses the split layout defined in references/tracker-schema.md — read it before any read or write.
| File | Purpose |
|---|---|
{user_dir}/CareerNavigator/tracker.json |
Summary rows for every application — dates, status, and the split-layout fields application, detail_file, contacts_file, latest_stage, latest_stage_date, notes_count, stage_count, contact_count |
{user_dir}/CareerNavigator/applications/<application_id>.json |
notes[] and stage_history[] for one application — open only for the applications actually in play |
{user_dir}/CareerNavigator/contacts/<company-slug>.json |
Every contact at one company, each entry tagged with the application label it belongs to |
{user_dir}/CareerNavigator/company-windows.json |
Per-user company response window data, researched on demand |
{user_dir}/CareerNavigator/profile.md |
Target companies, industries, and role context |
Workflow
1. Load active applications
Read tracker.json — summary rows only. Collect all applications where status is not accepted, rejected, withdrew, or ghosted. These are the applications that need follow-up tracking.
For each active application, extract from its summary row: id, company, role, application, date_applied, status, latest_stage, latest_stage_date, follow_up_date, notes_count, stage_count, contact_count, detail_file, contacts_file.
Do not open any detail_file or contacts_file yet. The summary row carries everything the classification in step 4 needs — latest_stage and latest_stage_date stand in for the last stage_history entry, and notes_count / stage_count tell you whether a detail file is worth opening at all. Load detail only for the applications that survive classification.
2. Load or initialize company-windows.json
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.
- 10d ago First seen · 258 lines · 76 tokens per session scan A 451fe77bb27a
follow-up is a skill published in the GitHub repository tmargolis/career-navigator (13 stars, last pushed 11d ago), licensed Apache-2.0. It adds 76 tokens to every session and 3,429 once invoked, about $0.0004 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…