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 MoizIbnYousaf/marketing-cli --skill newslettergit clone --depth 1 https://github.com/MoizIbnYousaf/marketing-cliWrote 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/moizibnyousaf/marketing-cli/newsletter)<a href="https://agentmods.dev/skills/moizibnyousaf/marketing-cli/newsletter"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/marketing-cli/newsletter/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/moizibnyousaf/marketing-cli/newsletter"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/marketing-cli/newsletter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00168 | $0.03092 |
| Opus 5 | $0.00084 | $0.01546 |
| Sonnet 5 | $0.00034 | $0.00618 |
| Haiku 4.5 | $0.00017 | $0.00309 |
Grade A, and why
newsletter 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 10d 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Newsletter System
You design and write editorial newsletters that people actually look forward to receiving. Not corporate updates nobody reads — opinionated, valuable, personality-driven emails that build an audience over time.
On Activation
- Read
brand/voice-profile.md— newsletters live or die by voice consistency - Read
brand/audience.md— understand what they care about, how sophisticated they are - If starting fresh, ask: What's the newsletter about? Who's it for? What format appeals to you?
- Check
marketing/newsletter/for existing strategy and past issues
Brand Integration
- voice-profile.md → Newsletters live or die by voice consistency. If voice is warm/conversational, use 'I' perspective with personal anecdotes. If authoritative/editorial, use curated insights with expert framing. The voice must feel like a person writing, not a company broadcasting.
- audience.md → Content selection and depth matches audience sophistication. Technical audience gets deep dives. General audience gets accessible summaries with links to learn more.
Step 1: Define the Newsletter
Newsletter Types
| Type | Description | Best For | Example |
|---|---|---|---|
| Curated | Best links + your commentary | Industry watchers, busy professionals | The Hustle, TLDR |
| Editorial | Original essays/insights | Thought leaders, opinionated founders | Stratechery, Lenny's Newsletter |
| Hybrid | Mix of original + curated | Most founders and creators | Morning Brew, Dense Discovery |
| Product update | What's new in your product | SaaS companies with active users | Linear, Notion changelogs |
| Educational | Teaches one skill per issue | Course creators, consultants | James Clear, Marketing Examples |
Strategy Doc
Before writing a single issue, establish:
---
name: "Newsletter Name"
tagline: "One-line value prop (what they get + how often)"
type: curated | editorial | hybrid | product | educational
frequency: weekly | biweekly | daily
send_day: Tuesday
send_time: "9:00 AM ET"
target_audience: "Who specifically reads this"
core_topic: "The single topic area"
voice: "How it sounds (reference voice-profile.md)"
success_metric: "Open rate > 40%, click rate > 5%"
---
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 352 lines · 168 tokens per session scan A a70101d1dba9
newsletter is a skill published in the GitHub repository MoizIbnYousaf/marketing-cli (31 stars, last pushed 24d ago), licensed MIT. It adds 168 tokens to every session and 3,092 once invoked, about $0.0008 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-30.
Other skills, from other repositories
linkedin-reply-handler
Draft a reply to a specific existing LinkedIn comment from its URL. Use when the user wants to reply to a comment on any post, or follow up after an author replied to them. Parses the commentUrn, resolves the correct parentComment target (LinkedIn flattens threads to 2 levels), and posts via Publora on approval. Not…
linkedin-comment-drafter
Draft a LinkedIn comment on someone else's post from its URL, or reshare (repost) it to your feed with optional commentary. Use when the user pastes a post URL and asks to comment, engage, be first commenter, or repost with their thoughts. Produces 1-3 variants in the user's voice, picks a reaction, and publishes via…
linkedin-employee-advocacy
Stand up and run a LinkedIn employee advocacy program for a marketing or sales team. Covers 14-day launch playbook, brand-guideline governance, per-post time budget, cadence benchmarks, and team ROI (reach, engagement, pipeline). Triggers on "employee advocacy", "get the team posting", "scale LinkedIn across team"…
ads-amazon
Audit Amazon Ads profiles, regions, Sponsored Products, Sponsored Brands, Sponsored Display, DSP, portfolios, targeting, search terms, retail readiness, creative, budgets, ACOS, TACOS, reporting, and policy. Use for Amazon Ads, sponsored ads, Amazon PPC, ACOS, TACOS, ASIN advertising, Amazon DSP, or retail-media…
ads-landing
Audit paid-ad landing pages for message match, mobile experience, performance, accessibility, trust, forms, consent, tracking, security, and conversion friction. Use for landing-page audit, post-click experience, LP audit, conversion-rate optimization, form optimization, ad-to-page message match, redirects, blocked…
ads-research
Refresh Claude Ads platform, API, policy, regulation, benchmark, issue, pull-request, fork, and repository evidence. Use for ads research refresh, expired refreshdue dates, stale API or platform claims, reverify-or-demote decisions, release-current claim validation, ecosystem review, current platform changes, or…