Borrowing it
Nothing to install: this file belongs to farrelfatah/nextjobkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/farrelfatah/nextjobkit/main/.agents/skills/write-cover-letter/SKILL.mdgit clone --depth 1 https://github.com/farrelfatah/nextjobkitWrote 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/farrelfatah/nextjobkit/write-cover-letter)<a href="https://agentmods.dev/skills/farrelfatah/nextjobkit/write-cover-letter"><img src="https://agentmods.dev/badge/skills/farrelfatah/nextjobkit/write-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/farrelfatah/nextjobkit/write-cover-letter"><img src="https://agentmods.dev/badge/skills/farrelfatah/nextjobkit/write-cover-letter.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00052 | $0.00511 |
| Opus 5 | $0.00026 | $0.00255 |
| Sonnet 5 | $0.00010 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
write-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 12d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Cover Letter
Add useful context that the resume cannot carry; do not narrate the resume back to the reader.
Inputs
Read:
profile/candidate.md.- The configured evidence file.
- The complete job listing and analysis.
- The stable tailored resume for the same opportunity.
If the tailored resume is still changing materially, finish it first.
Drafting Workflow
- Identify why this role, product, problem space, or company is specifically relevant.
- Select two or three evidence-backed connections.
- Explain how the candidate works or makes decisions where that adds signal.
- Address a material career transition or adjacent-experience gap only when it helps the reader interpret the candidacy.
- Close directly and professionally.
Default to 200–350 words. Use 100–180 words for a form note or explicitly short message.
When the listing is the only company source, connect to the role's problem space instead of inventing company or product affinity.
Quality Rules
- Open with a role-specific reason, not enthusiasm boilerplate.
- Use the company's language only when the candidate can support it.
- Do not repeat the resume bullet by bullet.
- Do not invent personal affinity, product usage, customer status, or company knowledge.
- Do not add salary, work authorization, relocation, or notice-period claims unless the prompt requires them and the user confirmed them.
- Do not treat location as proof of work authorization. An unresolved eligibility gate may coexist with a draft, but must block any claim that the package is submission-ready.
- Keep the tone natural enough to read aloud.
- Avoid empty claims such as “perfect fit,” “dream company,” or “passionate professional.”
File Contract
Write the editable source under cover-letters/:
[candidate-slug]-[company]-[role-type]-cover-letter-[yyyymmdd].md
Link it from the application prep file and tracker when those artifacts exist. Do not record it as submitted before confirmation.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 57 lines · 52 tokens per session scan A 2eb2e343cacc
write-cover-letter is a skill published in the GitHub repository farrelfatah/nextjobkit (5 stars, last pushed 21d ago), licensed MIT. It adds 52 tokens to every session and 511 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-31.
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…