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 good-sender/mcp --skill get-startedgit clone --depth 1 https://github.com/good-sender/mcpWrote 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/good-sender/mcp/get-started)<a href="https://agentmods.dev/skills/good-sender/mcp/get-started"><img src="https://agentmods.dev/badge/skills/good-sender/mcp/get-started/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/good-sender/mcp/get-started"><img src="https://agentmods.dev/badge/skills/good-sender/mcp/get-started.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.00045 | $0.00371 |
| Opus 5.5 | $0.00018 | $0.00148 |
| Sonnet 5.5 | $0.00009 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
get-started 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.
What it actually says
Get started with GoodSender
Use this skill right after the user connects GoodSender, or when they ask what they can do with it.
- Call
get_blogto read the workspace's blog settings. If the blog has no title or description, offer to set them withupdate_blog(ask before running it: it changes the public site). - Call
list_sender_identitiesandcheck_sender_domain_stats. Tell the user whether they have a verified sender domain and a sender identity. Without one, they can publish to the blog but cannot send email or newsletters; point them to the GoodSender dashboard to verify a domain. - Call
list_postsand summarize how many posts are published and how many are drafts. - Suggest one next step that fits what you found, for example:
- "Draft a post from these notes and show me a preview before publishing."
- "Email my latest post to newsletter subscribers."
- "Send the 'Weekly update' template to my beta-users group."
Ground rules:
- Never publish, send, delete or change the live site without the user's explicit go-ahead. Show a preview first (
create_post_preview,render_template_preview). - GoodSender only emails recipients who opted in. Adding a recipient sends them a consent request; mail to them waits until they consent. Do not offer to work around consent.
- Transactional templates (
send_consentless_email) are for messages the recipient asked for, such as account notices and receipts, sent from the workspace's own verified domain.
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 · 23 lines · 45 tokens per session scan A a22dd37d112a
get-started is a skill published in the GitHub repository good-sender/mcp (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 45 tokens to every session and 371 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-11-03.
get-started compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| get-startedgood-sender/mcp | Skill | 1 | 4d ago | Apache-2.0 | A | 45 | Claude Code, Codex |
| affiliate-blog-builderAffitor/affiliate-skills | Skill | 767 | 18d ago | MIT | A | 110 | Claude Code, Codex |
| blog-postNickCrew/Claude-Cortex | Skill | 66 | 4mo ago | MIT | A | 70 | Claude Code, Codex |
| karpathy-article-writingIrtezaAsadRizvi/article-writing-skills | Skill | 25 | 6mo ago | MIT | A | 92 | Claude Code, Codex |
| affiliate-blog-buildergabrielmoreira/agent-skills-mirror | Skill | 20 | yesterday | MIT | A | 110 | Codex |
| affiliate-blog-builderGingg7260/affiliate-skills | Skill | 5 | 24d ago | MIT | A | 110 | Codex |
| dcf-modelNousResearch/hermes-agent | Skill | 261k | yesterday | MIT | A | 14 | Claude Code, Codex |