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 cover-lettergit 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/cover-letter)<a href="https://agentmods.dev/skills/tmargolis/career-navigator/cover-letter"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/cover-letter/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/cover-letter"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/cover-letter.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.00049 | $0.01651 |
| Opus 5 | $0.00024 | $0.00826 |
| Sonnet 5 | $0.00010 | $0.00330 |
| Haiku 4.5 | $0.00005 | $0.00165 |
Grade A, and why
cover-letter 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build a CoverLetterBrief, then invoke writer for final letter prose. Do not write the full letter in this skill—writer owns send-ready copy.
Workflow
1. Collect inputs
Application data uses the split layout defined in references/tracker-schema.md — read it before any read or write.
Job description — required. If not already in context, ask the user to provide it.
Tailored resume — check {user_dir}/CareerNavigator/artifacts-index.json for a resume artifact for this company and role. If one exists, use it as the primary source for experience framing. If none exists:
"I don't see a tailored resume for this role yet. Want me to tailor one first, or build the brief from your ExperienceLibrary directly?"
Profile — read {user_dir}/CareerNavigator/profile.md for differentiators, tone preferences, and any standing instructions.
Contact context — contacts are no longer inside applications[]. In tracker.json, find the summary row for this company and role, take its contacts_file, and load {user_dir}/CareerNavigator/ + that path (contacts/<company-slug>.json); a row with contact_count: 0 or no contacts_file has no contacts on file, so skip the read. Filter the file's contacts[] to entries whose application equals the row's application label ("<company> — <role>"), and dedupe by name before presenting. If a contact is present, note it for the brief (do not draft named flattery unless accurate).
2. Research the company
Before briefing, identify 1–2 specific, verifiable things about the company relevant to fit:
- Recent product launches, initiatives, or strategic direction
- Team/culture signals from the JD
- Notes about this company — in the summary row's
detail_file(applications/<application_id>.json→notes[]), or in profile. Skip the detail read when the row'snotes_countis0.
Do not use generic praise. If no specific signals, say so in the brief—writer will omit flattery.
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 · 122 lines · 49 tokens per session scan A 763c3836678a
cover-letter is a skill published in the GitHub repository tmargolis/career-navigator (13 stars, last pushed 12d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,651 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…
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…