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 agentmods add skills/chucklever/cel-kdev/cover-letternpx skills add chucklever/cel-kdev --skill cover-lettergit clone --depth 1 https://github.com/chucklever/cel-kdevWrote 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/chucklever/cel-kdev/cover-letter)<a href="https://agentmods.dev/skills/chucklever/cel-kdev/cover-letter"><img src="https://agentmods.dev/badge/skills/chucklever/cel-kdev/cover-letter.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 | $0.00250 | $0.04820 |
| Opus 5 | $0.00125 | $0.02410 |
| Sonnet 5 | $0.00050 | $0.00964 |
| Haiku 4.5 | $0.00025 | $0.00482 |
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 4d 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cover-letter
How to write the content of a document that introduces a set of changes to the people who will review them, in Chuck's voice. The Linux kernel patch series cover letter is the main case, and the rules below are written against it. A GitHub pull request description and a merge commit message do the same job and take the same rules; "Other surfaces" at the end covers where they differ. Where the cover file lives and how a kernel series is sent (b4/series-send) belong to the series-send and cel-kdev:b4 skills; a reroll's changelog belongs to the cel-prose:version-changelog skill, and a single patch's commit message to the cel-prose:commit-message skill. Load those for the workflow, this for the prose.
What a cover letter is for
The cover directs reviewer attention. It carries what the diffs and the commit messages do not advertise: design choices that span several patches, subtle invariants, ordering constraints, and contracts a later patch relies on. A reviewer reads the cover to learn how to read the series.
So the test for every sentence is whether it earns its place against that purpose. If a reviewer will find its content in the patch it belongs to -- the subject line in the shortlog, the commit message, the diff -- it is redundant here; cut it. The defect the series answers is the exception. State it here even though the fixing patch states it too. The cover is not a summary of the patches; it records the cross-cutting design that no single patch carries.
The cover never enters git history: a part-zero cover is not applied at all, and for a lone patch the same text sits below the "---" that git strips at apply time. It lives only in the review thread. So the cover coordinates the series but never substitutes for a patch's own commit message -- anything a single patch needs to justify itself belongs in that patch, not only in the cover.
Before drafting: sourcing the rationale
The cover carries what the patches do not, so the patches cannot be the only input. Reading the series tells you what it does. It rarely tells you why it exists, and that is the half a reviewer is being asked to accept. Go get it first:
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.
- 4d ago First seen · 397 lines · 250 tokens per session scan A d0e854abbe04
cover-letter is a skill published in the GitHub repository chucklever/cel-kdev (2 stars, last pushed 3d ago), licensed MIT. It adds 250 tokens to every session and 4,820 once invoked, about $0.0013 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
baoyu-youtube-transcript
Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast re-formatting. Use when user asks to "get YouTube transcript", "download subtitles", "get captions", "YouTube字幕", "YouTube封面"…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
pdf-verification-cli
Verify PDF page count and content using command-line tools when Python libraries unavailable.