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 laboramus-ai/laboramus-ai-claude-plugin --skill cover-lettergit clone --depth 1 https://github.com/laboramus-ai/laboramus-ai-claude-pluginWrote 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/laboramus-ai/laboramus-ai-claude-plugin/cover-letter)<a href="https://agentmods.dev/skills/laboramus-ai/laboramus-ai-claude-plugin/cover-letter"><img src="https://agentmods.dev/badge/skills/laboramus-ai/laboramus-ai-claude-plugin/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/laboramus-ai/laboramus-ai-claude-plugin/cover-letter"><img src="https://agentmods.dev/badge/skills/laboramus-ai/laboramus-ai-claude-plugin/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.00051 | $0.00523 |
| Opus 5 | $0.00026 | $0.00262 |
| Sonnet 5 | $0.00010 | $0.00105 |
| Haiku 4.5 | $0.00005 | $0.00052 |
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 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laboramus — Cover Letter
Produce a tailored cover letter via two stages, using two sub-agents. The letter is written in the job posting's language; the brief and your conversation are in the user's language.
Prerequisites
- Locate the current application folder per
../../references/conventions.md§1. job-posting.mdandprofile/candidate-profile.mdmust exist. If the profile is missing, stop and ask the user to build it (build-profile).- Existing
analyses/(employer, role-requirements, fit-comparison) are used if present, but are NOT required — the strategist short-circuits and derives what it needs from the posting + profile.
Step A — Strategy brief (review gate)
Dispatch the strategist sub-agent. It writes strategy-brief.md (candidate facts, top 5–7 arguments, tone, three-part narrative, major gaps, personality only-if-it-helps) and stops.
Then SHOW the brief to the user and pause: "Review and correct anything — facts, emphasis, tone. The letter will be in . Say 'write the letter' when ready." Let the user edit strategy-brief.md or tell you changes. This is the human checkpoint — do not skip it.
Step B — Write
Once the user approves, dispatch the writer sub-agent. It reads the (possibly edited) strategy-brief.md and writes cover-letter.md: plain text, 300–350 words, three-part structure, banned-word list enforced for the posting's language, no repetition, strong opening hook.
After
- Show the letter. Offer revisions (the user can ask for tone tweaks, shortening, different emphasis — re-run the writer).
- Update
status.json:steps.coverLetter,updatedAt— per../../references/status-schema.md. - Offer interview-prep as a natural next step.
Standalone use
If the user jumps straight to "write me a cover letter for this job" with only a posting + profile, run A then B directly — the strategist handles the missing analyses. Offer to run the full employer/role/fit analyses too if they want richer results.
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 · 29 lines · 51 tokens per session scan A 5131f5bd1c8b
cover-letter is a skill published in the GitHub repository laboramus-ai/laboramus-ai-claude-plugin (2 stars, last pushed 13d ago), licensed MIT. It adds 51 tokens to every session and 523 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…