Borrowing it
Nothing to install: this file belongs to briancl2/CustomerNewsletter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/briancl2/CustomerNewsletter/main/.github/skills/newsletter-assembly/SKILL.mdgit clone --depth 1 https://github.com/briancl2/CustomerNewsletterWrote 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/briancl2/customernewsletter/newsletter-assembly)<a href="https://agentmods.dev/skills/briancl2/customernewsletter/newsletter-assembly"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/newsletter-assembly/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/briancl2/customernewsletter/newsletter-assembly"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/newsletter-assembly.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.00069 | $0.01279 |
| Opus 5 | $0.00034 | $0.00639 |
| Sonnet 5 | $0.00014 | $0.00256 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
newsletter-assembly 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 11d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Newsletter Assembly
Assemble Phase 3 curated sections and Phase 2 events into a complete newsletter.
Quick Start
- Read Phase 3 curated sections from
workspace/newsletter_phase3_curated_sections_*.md - Read Phase 2 events from
workspace/newsletter_phase2_events_*.md - Create introduction with 2-3 key highlights
- Assemble sections in mandatory order
- Add standard closing, changelog links, YouTube playlists
- Enforce heading structure and density targets for long windows
- Write output to
output/YYYY-MM_month_newsletter.md
Inputs
- Phase 3 Curated Sections:
workspace/newsletter_phase3_curated_sections_*.md(required) - Phase 2 Events:
workspace/newsletter_phase2_events_*.md(required)
Output
- File:
output/YYYY-MM_month_newsletter.md - Complete newsletter ready for distribution
Core Workflow
Step 1: Create Introduction
Use the standard template with 2-3 dynamic highlights:
This is a personally curated newsletter for my customers, focused on the most
relevant updates and resources from GitHub this month. Highlights for this month
include [2-3 key highlights]. If you have any feedback or want to dive deeper
into any topic, please let me know. Feel free to share this newsletter with
others on your team as well. You can find an archive of past newsletters
[here](https://github.com/briancl2/CustomerNewsletter).
Select highlights from the most impactful GA features or major enterprise announcements in the curated sections.
Step 2: Assemble in Mandatory Order
See section-ordering.md for the required section sequence.
- Introduction (with highlights)
- Monthly Announcement / Lead Section (if present in Phase 3)
- Copilot (mandatory heading shape:
# Copilotwith## Latest Releases, plus Copilot at Scale with changelogs) - Enterprise and Security Updates (H1 for Feb benchmark-style runs)
- Resources and Best Practices (H1 when sources exist)
- Webinars, Events, and Recordings (H1, with H2 subheadings from Phase 2)
- Closing
What ships with it
5 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.
- 11d ago First seen · 136 lines · 69 tokens per session scan A cc951a383ea4
newsletter-assembly is a skill published in the GitHub repository briancl2/CustomerNewsletter (11 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 1,279 once invoked, about $0.0003 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
trulens-diagnosis
Diagnose low evaluation scores and generate actionable improvement recommendations.
agents-sdk-dotnet-activityhandler-migration
Use when migrating a Microsoft 365 Agents SDK agent that uses ActivityHandler or TeamsActivityHandler to AgentApplication. This is ONLY for DotNet projects that uses Microsoft.Agents. packages. Triggered by Agents SDK bots that subclass ActivityHandler or TeamsActivityHandler that need to be modernized to…
agents-sdk-dotnet
Use when any code imports Microsoft.Agents.Hosting.AspNetCore, Microsoft.Agents.Builder, or related Agents SDK packages, or when the user is building, configuring, or asking questions about a Microsoft 365 Agents SDK agent in C# / .NET. Trigger on questions about appsettings.json, connection configuration…
agents-sdk-provision
Use when provisioning Azure resources for a Microsoft Agents SDK application — including creating an Azure Bot Service resource, setting up Entra app registrations, configuring identity credentials (UserManagedIdentity, FederatedCredentials, or ClientSecret), adding a Teams channel, running Bicep deployments for SSO…
agents-sdk-typescript-otel
Use when adding, configuring, validating, or troubleshooting OpenTelemetry observability for a Microsoft 365 Agents SDK application in JavaScript or TypeScript. Trigger when the user mentions OpenTelemetry, OTel, telemetry, traces, metrics, logs, OTLP, Aspire Dashboard, Application Insights, Azure Monitor, distributed…
agents-sdk-dotnet-otel
Use when adding, configuring, validating, or troubleshooting OpenTelemetry observability for a Microsoft 365 Agents SDK application in C# / .NET. Trigger when the user mentions OpenTelemetry, OTel, telemetry, traces, metrics, logs, OTLP, Aspire Dashboard, Application Insights, Azure Monitor, distributed tracing…