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 swan-gtm/gtm-skills --skill weekly-roundup-emailgit clone --depth 1 https://github.com/swan-gtm/gtm-skillsWrote 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/swan-gtm/gtm-skills/weekly-roundup-email)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/weekly-roundup-email"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/weekly-roundup-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/swan-gtm/gtm-skills/weekly-roundup-email"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/weekly-roundup-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.00164 | $0.01199 |
| Opus 5 | $0.00082 | $0.00600 |
| Sonnet 5 | $0.00033 | $0.00240 |
| Haiku 4.5 | $0.00016 | $0.00120 |
Grade A, and why
weekly-roundup-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 9d 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.
This is a copy
86% identical to tooluniverse-product-safety-surveillance — 270 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write A Weekly Roundup Email
Write a curated weekly roundup email that packages the best links, insights, or resources from your week into a scannable, valuable email — with your unique take on each item.
Why This Works
Roundup emails are one of the highest-value, lowest-effort email formats. They work because: (1) curation is a skill — your subscribers are busy and trust you to filter the noise, (2) they're scannable — readers can consume them in 2 minutes or save items for later, (3) they build a habit — subscribers learn to expect and look forward to your weekly digest, and (4) they position you as someone who's always learning and sharing. The key that separates great roundup emails from boring link dumps: your commentary. Every item needs YOUR angle, not just a description.
How to Use This Skill
When triggered, ask the user for:
To write your roundup email, I need:
- What are you rounding up? — Paste links, resources, lessons, tools, tweets, content, or ideas you want to include (minimum 3, ideally 5-7 items)
- Roundup format — What style do you want?
- Link roundup — Best articles/content you consumed this week
- Lesson roundup — Top things you learned or observed this week
- Tool roundup — Apps, tools, or resources you discovered
- Content roundup — Your own content from the week, repackaged
- Hybrid — Mix of the above
- Your audience — Who reads your newsletter?
- Your newsletter voice — Casual, professional, witty, motivational?
- Any recurring section? — Do you have a signature section? (Quote of the week, tool of the week, ask of the week, etc.)
Process
Step 1: Organize the Items
Group and sequence the roundup items for maximum flow:
- Lead with the most interesting/valuable item
- Alternate between formats (link, lesson, tool) to keep it dynamic
- End with something actionable or forward-looking
Step 2: Write the Intro (2-3 sentences)
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.
- 9d ago First seen · 113 lines · 164 tokens per session scan A 5b29ee5c9c57
weekly-roundup-email is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 164 tokens to every session and 1,199 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to tooluniverse-product-safety-surveillance, differing in 270 lines, and is treated as a copy.
Other skills, from other repositories
teaser-block-writer
Writes "read next," "related articles," or "previously on" teaser blocks for web pages, newsletters, or app interfaces — short, click-worthy summaries that drive readers from one piece of content to another.
email-marketing
Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics.
Mailchimp Automation
Automate Mailchimp email marketing campaigns, audience management, automations, and analytics.
fastmail-imap-newsletter-digest
Read emails from Fastmail via IMAP and process them (e.g., newsletter digest). Handles HTML→text extraction for newsletters where plain text fallbacks are useless. Summarization via self-contained Python script calling Qwen 3.5 (NanoGPT) and delivery via AgentMail.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…