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 brandi-berg/annie --skill cover-lettergit clone --depth 1 https://github.com/brandi-berg/annieWrote 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/brandi-berg/annie/cover-letter)<a href="https://agentmods.dev/skills/brandi-berg/annie/cover-letter"><img src="https://agentmods.dev/badge/skills/brandi-berg/annie/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/brandi-berg/annie/cover-letter"><img src="https://agentmods.dev/badge/skills/brandi-berg/annie/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.00092 | $0.01190 |
| Opus 5 | $0.00046 | $0.00595 |
| Sonnet 5 | $0.00018 | $0.00238 |
| Haiku 4.5 | $0.00009 | $0.00119 |
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cover-letter — Cover Letter Builder
Read context/intake.md (plugin root) first and run the shared intake: confirm inputs, enforce input discipline, load all mandatory context layers. Stop immediately if context/section-b-voice.md is missing.
Required inputs: Job Description, Company Mission and/or Values, Contributing Skills Statement.
Workflow — do not skip, collapse, or reorder steps. Each step produces its own labeled section.
Step 1: Input acknowledgment
Checklist of received vs. missing inputs. Ask for anything missing before continuing.
Step 2: Role read
From the JD, extract: company name, exact job title, core requirements, preferred/bonus skills. Map Brandi's verifiable experience to the preferred/bonus skills first (anchoring rule), then confirm core coverage. Cite only evidence present in the context files, per Section A candidate truth rules.
Step 3: Draft the {{Company-why-statement}} — APPROVAL GATE
A polished, compelling statement of why Brandi is drawn to this organization, built from her Contributing Skills Statement and the company's mission/values. Constraints:
- 1 to 2 sentences. It is inserted as a standalone sentence in the letter's opening paragraph, immediately after "...I bring over 15 years of experience building and scaling high-performance recruiting functions at AI-native and developer-focused startups." and immediately before "I am excited to bring my expertise in full-cycle recruiting, AI-enabled talent operations, and strategic leadership to accelerate your growth." It must read naturally between those two sentences.
- Specific to this company. The test: if it could be sent to any other company unchanged, rewrite it.
- Section B voice, Section A formatting guardrails. No em dashes. Run the Section B pre-delivery check.
Present the draft and wait for Brandi's explicit approval. Iterate until approved. Do not continue to Step 4 without approval.
Step 4: Draft Section 3 "Where I add value to {{Company Name}}" — APPROVAL GATE
The template's Section 3 sits between the markers [This Section To Be Edited] and [End Edit Section] and contains one framing paragraph plus three bullets. Treat these as tailorable defaults:
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 · 63 lines · 92 tokens per session scan A f5e44aa9d0fb
cover-letter is a skill published in the GitHub repository brandi-berg/annie (21 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,190 once invoked, about $0.0005 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.