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 TaewoooPark/MagLab --skill academic-emailgit clone --depth 1 https://github.com/TaewoooPark/MagLabWrote 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/taewooopark/maglab/academic-email)<a href="https://agentmods.dev/skills/taewooopark/maglab/academic-email"><img src="https://agentmods.dev/badge/skills/taewooopark/maglab/academic-email/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/taewooopark/maglab/academic-email"><img src="https://agentmods.dev/badge/skills/taewooopark/maglab/academic-email.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.00062 | $0.00872 |
| Opus 5.5 | $0.00025 | $0.00349 |
| Sonnet 5.5 | $0.00012 | $0.00174 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
academic-email 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
academic-email — Professional academic email skill
Overview
This skill drafts a ≤200 word professional academic email, aligned with MagLab research integrity principles (§3.3) and the Appendix C bundle comms workflow.
Core principles:
- Body must be ≤200 words.
- Output includes a subject line on the first line and a follow-up action at the end.
- The AI does not invent results, claims, or institutional affiliations.
- All personalisation fields (sender name, greeting, follow-up date) are marked
[FILL]. - Output always begins with
HUMAN REVIEW REQUIRED. - Auto-send is prohibited — the draft is returned to the researcher for review and manual sending.
Agent: maglab.authoring.comms.academic_email.AcademicEmailAgent
CLI command: maglab comms email
Inputs
| Key | Type | Required | Description |
|---|---|---|---|
email_type |
str | Yes | One of: collaboration | question | interview | recommendation | application |
recipient |
str | Yes | Recipient's name or title (e.g. "Professor Smith") |
topic |
str | Yes | Main purpose of the email |
related_papers |
list[str] | No | Relevant papers by the author or recipient |
Email types
| Type | Intent |
|---|---|
collaboration |
Express interest in a research collaboration on a shared topic |
question |
Ask a specific technical or scientific question politely |
interview |
Request a meeting or informational interview |
recommendation |
Request a letter of recommendation with context |
application |
Express interest in a position, program, or grant |
Output
A CommsResult with:
text: Email draft (≤200 words) starting withHUMAN REVIEW REQUIRED.fill_markers: List of[FILL]positions requiring author personalisation.word_count: Approximate word count (logged as a warning if >200).
Email structure
HUMAN REVIEW REQUIRED
Subject: [concise subject line]
[FILL: Dear Professor / Dr. [FILL: name],]
[Email body — ≤200 words, based on email_type instruction]
Follow-up: [FILL: suggested date or action]
Best regards,
[FILL: Sender name, affiliation]
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.
- 2mo ago First seen · 102 lines · 62 tokens per session scan A c6da8051c7e2
academic-email is a skill published in the GitHub repository TaewoooPark/MagLab (11 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 872 once invoked, about $0.0002 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.
academic-email compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| academic-emailTaewoooPark/MagLab | Skill | 11 | 3mo ago | MIT | A | 62 | Claude Code |
| dos-dispatch-loopanthony-chaudhary/dos-kernel | Skill | 21 | 10d ago | MIT | A | 49 | Claude Code |
| dos-goal-fleetanthony-chaudhary/dos-kernel | Skill | 21 | 10d ago | MIT | A | 51 | Claude Code |
| dos-goal-gateanthony-chaudhary/dos-kernel | Skill | 21 | 10d ago | MIT | A | 54 | Claude Code |
| dos-enforce-tuneanthony-chaudhary/dos-kernel | Skill | 21 | 10d ago | MIT | A | 62 | Claude Code |
| dos-next-upanthony-chaudhary/dos-kernel | Skill | 21 | 10d ago | MIT | A | 53 | Claude Code |
| dos-self-improveanthony-chaudhary/dos-kernel | Skill | 21 | 10d ago | MIT | A | 56 | Claude Code |