agentmods.dev

cover-letter

cover-letter is a skill for Claude Code from TaewoooPark/MagLab. It costs 64 tokens per session (817 once invoked), scanned A, original, MIT.

A workflow for drafting journal-submission cover letters of up to 250 words from an author's key results. A cover letter is the short note sent to a journal editor with a manuscript.

In plain words
What is it for?
Use it to prepare a review-required cover letter with fill-in fields for the editor, affiliation, and contact information; it does not send the letter.
Why use it?
It keeps novelty claims tied to the information provided and leaves personal details for the author to complete and review.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

not rated 11repo 3mo ago A scan 64 tokens original MIT

Good fit Use it to prepare a review-required cover letter with fill-in fields for the editor, affiliation, and contact information; it does not send the letter.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/taewooopark/maglab/cover-letter
View source ↗ TaewoooPark/MagLab
Install

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.

Any agent
npx skills add TaewoooPark/MagLab --skill cover-letter
Clone the repo
git clone --depth 1 https://github.com/TaewoooPark/MagLab

Made for: Claude Code.

Wrote 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.

agentmods badge for cover-letter

README.md
[![agentmods](https://agentmods.dev/badge/skills/taewooopark/maglab/cover-letter/github.svg)](https://agentmods.dev/skills/taewooopark/maglab/cover-letter)
Your own site
<a href="https://agentmods.dev/skills/taewooopark/maglab/cover-letter"><img src="https://agentmods.dev/badge/skills/taewooopark/maglab/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.

agentmods 80×15 button for cover-letter

Your own site · 80×15
<a href="https://agentmods.dev/skills/taewooopark/maglab/cover-letter"><img src="https://agentmods.dev/badge/skills/taewooopark/maglab/cover-letter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 817 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.00817
Opus 5.5 $0.00026 $0.00327
Sonnet 5.5 $0.00013 $0.00163
Haiku 4.5 $0.00006 $0.00082

Measured 2mo ago against content hash 75de6c68fb4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

skills/cover-letter/SKILL.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

cover-letter — Journal submission cover letter skill

Overview

This skill drafts a ≤250 word cover letter for journal manuscript submission, aligned with MagLab research integrity principles (§3.3) and the Appendix C bundle comms workflow.

Core principles:

  • Body must be ≤250 words (excluding salutation and sign-off).
  • The AI constructs novelty statements only from the author-provided key_results input.
  • The AI never invents results, citations, or claims beyond the provided inputs.
  • All personalisation fields (editor name, affiliation, email) are marked [FILL].
  • Output always begins with HUMAN REVIEW REQUIRED.
  • The letter is never auto-sent — it is written to a file for human review.

Agent: maglab.authoring.comms.cover_letter.CoverLetterAgent CLI command: maglab comms cover-letter

Inputs

Key Type Required Description
journal str Yes Target journal name (e.g. "Physical Review Letters")
title str Yes Manuscript title
key_results list[str] or str Yes 1–3 key results to highlight in the novelty statement
related_pubs list[str] No Related published papers by the authors

Output

A CommsResult with:

  • text: Cover letter (≤250 words) starting with HUMAN REVIEW REQUIRED.
  • fill_markers: List of [FILL] positions requiring author personalisation.
  • word_count: Approximate word count (logged as a warning if >250).

Letter structure

HUMAN REVIEW REQUIRED

[FILL: Dear Editor-in-Chief / Dr. [FILL: editor name],]

We submit our manuscript "[title]" for consideration in [journal].

[Novelty statement based on key_results — 1–2 sentences]

[Relationship to related_pubs — 1 sentence, if provided]

All authors have read and approved the manuscript.
The manuscript is not under consideration elsewhere.

[FILL: Corresponding author name, affiliation, email]

Workflow

  1. Collect the manuscript title, target journal, and 1–3 key results.
  2. Run maglab comms cover-letter or invoke CoverLetterAgent.draft(inputs).
  3. Review every [FILL] field — fill in editor name and corresponding author details.
  4. Verify the word count is ≤250 words.
  5. Submit the letter alongside the manuscript via the journal portal.

Read the full file on GitHub · 94 lines

Changes

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.

  1. 2mo ago First seen · 94 lines · 64 tokens per session scan A 75de6c68fb4d

Subscribe to this mod's changes

cover-letter is a skill published in the GitHub repository TaewoooPark/MagLab (11 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 817 once invoked, about $0.0003 per session on Opus 5.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.

Writing and docsai-for-scienceclidata-analysisinstrumentsllm-agentsmagnetism
Related

cover-letter compared with skills from other repositories

cover-letter next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
cover-letterTaewoooPark/MagLabSkill113mo agoMITA64Claude Code
dos-dispatch-loopanthony-chaudhary/dos-kernelSkill2110d agoMITA49Claude Code
dos-goal-fleetanthony-chaudhary/dos-kernelSkill2110d agoMITA51Claude Code
dos-goal-gateanthony-chaudhary/dos-kernelSkill2110d agoMITA54Claude Code
dos-enforce-tuneanthony-chaudhary/dos-kernelSkill2110d agoMITA62Claude Code
dos-next-upanthony-chaudhary/dos-kernelSkill2110d agoMITA53Claude Code
dos-self-improveanthony-chaudhary/dos-kernelSkill2110d agoMITA56Claude Code