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 JayRHa/AgentSkills --skill cover-letter-writergit clone --depth 1 https://github.com/JayRHa/AgentSkillsWrote 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/jayrha/agentskills/cover-letter-writer)<a href="https://agentmods.dev/skills/jayrha/agentskills/cover-letter-writer"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/cover-letter-writer.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.1 | $0.00089 | $0.00988 |
| Opus 5 | $0.00044 | $0.00494 |
| Sonnet 5 | $0.00018 | $0.00198 |
| Haiku 4.5 | $0.00009 | $0.00099 |
Grade A, and why
cover-letter-writer 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 8d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cover Letter Writer
Overview
This skill writes a short, specific, genuinely persuasive cover letter that complements (never repeats) the resume. A good cover letter answers three questions fast: Why this company? Why this role? Why you? — backed by one or two concrete proof points.
Keywords: cover letter, motivation letter, letter of interest, application letter, Anschreiben, job application, career change, why this company.
When to use vs. not
Use this whenever a role asks for (or allows) a cover letter, or when the candidate needs to explain something a resume can't (a pivot, a gap, an unusual fit). Don't pad — if there's nothing role-specific to say, a tight 3-paragraph letter beats a generic page. Never fabricate enthusiasm with invented facts about the company; use real, verifiable specifics.
Inputs to gather first
- The job description and company name.
- The candidate's 2–3 strongest relevant achievements (ideally quantified).
- One genuine reason they want this company/role (product, mission, team, problem).
- Anything to address head-on: career change, gap, relocation, over/under-qualification.
- Tone target: formal (finance/law/gov) vs. warm-professional (startup/creative).
Workflow
- Research the hook. Find one specific, true thing about the company (a product, value, recent launch, problem they solve) the candidate authentically connects to. This becomes the opener. Generic "I am writing to apply for…" openers are dead on arrival.
- Map proof to needs. Read the JD's top 3 requirements. Pick the candidate's achievements that directly answer them.
- Write the opening (2–3 sentences). Name the role, lead with the hook or a punchy proof point. Make the reader want the next paragraph.
- Write the body (1–2 short paragraphs). Each makes one claim about fit and backs it with a concrete, quantified example. Show impact, not a duty list. This is "the resume's greatest hits, with narrative."
- Address the elephant (if any). One confident sentence on the gap/pivot/relocation — framed forward, never apologetic.
- Close (2 sentences). Restate enthusiasm, state availability, and a light call to action ("I'd welcome the chance to discuss…"). Thank them.
- Trim to ~250–350 words / under one page. Cut every sentence that could appear in any other letter.
- Match format. Email body vs. attached letter; for DACH, follow the formal Anschreiben layout (sender/recipient blocks, date, subject line).
What ships with it
2 files 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.
- 8d ago First seen · 60 lines · 89 tokens per session scan A b50e89c366b8
cover-letter-writer is a skill published in the GitHub repository JayRHa/AgentSkills (5 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 988 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-31.
Other skills, from other repositories
cost-optimizer
Trigger when the user asks to audit Claude Code costs, reduce token spend, says "my Claude bill is too high", "optimize my CLAUDE.md", "why is this project burning tokens", or "/cost-optimizer". Scans a project for the common Claude Code cost leaks and returns a prioritized fix list.
excalidraw-architecture
Trigger when the user asks for an architecture diagram, says "draw the system", "update the architecture diagram", "give me an excalidraw of this codebase", or "/excalidraw-architecture". Generates or updates an Excalidraw JSON file at docs/architecture.excalidraw by reading the codebase's key entry points.
model-cost-compare
Trigger when the user asks which model to use, wants to compare model costs, says "what's cheapest for this task", "should I use Opus or Sonnet", "can a smaller model handle this", or "/model-cost-compare". Estimates token cost across Opus 4.6, Sonnet 4.6, GLM-5.1, Minimax M2.7, and local Gemma 4, then recommends the…
openclaw-debugger
Trigger when an OpenClaw agent is broken, silent, crashing, stuck, not responding, returning empty output, or the user says "my agent is down", "agent not working", "/openclaw-debugger". Walks through the standard OpenClaw 2026.4 diagnosis checklist and prints a report.
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.
meeting-notes
Paste raw meeting notes and get a clean summary with key decisions and action items.