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 surfmind-space/awesome-surfmind --skill cover-letter-buildergit clone --depth 1 https://github.com/surfmind-space/awesome-surfmindWrote 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/surfmind-space/awesome-surfmind/cover-letter-builder)<a href="https://agentmods.dev/skills/surfmind-space/awesome-surfmind/cover-letter-builder"><img src="https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/cover-letter-builder/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/surfmind-space/awesome-surfmind/cover-letter-builder"><img src="https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/cover-letter-builder.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.00058 | $0.00957 |
| Opus 5 | $0.00029 | $0.00478 |
| Sonnet 5 | $0.00012 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
cover-letter-builder 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cover Letter Builder
Create a tailored cover letter from the selected text, visible page, or pasted job description, and draft it in chat for review. Before drafting, confirm a real job description is present — a role title, a company name, and responsibilities or requirements. If it is missing, ask the user to paste the posting or open it. Use only achievements and facts the user has supplied; never invent numbers, employers, or qualifications, and keep the letter specific to this company and role rather than generic filler. Adapted from santifer/career-ops cover mode.
- Parse the job description: exact role title, company, location, top competencies, mission language, start-date signals, language requirements, domain, and tone.
- Research the company when current context would materially improve the letter — summarize what it appears to be building, prioritizing, or struggling with — and ask the user to confirm or correct the synthesis before using it.
- Extract 8-10 phrases to mirror: ATS-critical terms (titles, tools, methods, domain terms) and human trust signals (verbs, product nouns, team framing, outcome language from the posting).
- Identify gaps only when visible from the user's background — domain mismatch, language requirement, start date, title mismatch, relocation, authorization — and ask how they want to handle any real one before writing.
- If not already clear, ask the four drafting inputs: why this role or company, what problem they would help solve, how they would approach it, and the desired tone (formal, direct, conversational, or mirror the posting). If no achievements are available, ask for 3-5 proof points first.
- Draft the letter: candidate header (when provided), role and company line, optional greeting, a two-sentence opening, one profile paragraph, four to five achievement bullets when there are enough proof points, a short "problems I will solve" paragraph, and a close that acknowledges any confirmed gap.
Write in active voice and keep every major claim backed by a number, system, product, customer, team, or stated requirement. Mirror the job's vocabulary but not its structure — use each keyword once, placed in the opening, profile paragraph, achievements, and problems paragraph, and keep the personal "why this role" angle and the close in the user's own words. Avoid filler like "excited to apply", "passionate about", "perfect fit", "proven track record", "leverage", "synergy", and "cutting-edge". List any keyword you cannot include honestly after the draft. Return Research and angle, Keywords to mirror, Questions before drafting (when needed), then the Draft cover letter once you have enough to write.
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 · 50 lines · 58 tokens per session scan A 7c8a4c951554
cover-letter-builder is a skill published in the GitHub repository surfmind-space/awesome-surfmind (5 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 957 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
uiux-master
UI/UX expert for design systems, accessibility, and avoiding generic AI-generated design patterns.
cs-master
Expert computer scientist for algorithms, complexity analysis, and distributed systems.
data-science
ML engineering expert for feature engineering, model debugging, and production pipelines.
network-devops
Network performance expert for latency optimization, packet analysis, and infrastructure tuning.
quant-finance
Quantitative finance expert for trading strategies, risk management, and portfolio optimization.
rust-master
Rust expert for async systems, unsafe code, and zero-cost abstractions.