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-validation/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-validation)<a href="https://agentmods.dev/skills/briancl2/customernewsletter/newsletter-validation"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/newsletter-validation/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-validation"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/newsletter-validation.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.00057 | $0.01770 |
| Opus 5 | $0.00028 | $0.00885 |
| Sonnet 5 | $0.00011 | $0.00354 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
newsletter-validation 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 12d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Newsletter Validation
Validate newsletter output against quality standards.
Quick Start
- Run automated validation:
bash .github/skills/newsletter-validation/scripts/validate_newsletter.sh <newsletter_file> - Review results: exit 0 = pass, exit 1 = fail with details
- If automated checks pass, perform manual review using the rubric
- Fix any issues and re-validate
Inputs
- Newsletter file: Path to the assembled newsletter markdown (e.g.,
output/YYYY-MM_month_newsletter.md)
Output
- Exit code 0 (pass) or 1 (fail) with detailed report on stdout
Automated Checks
The validate_newsletter.sh script checks:
Required Sections
- Introduction with archive link
- Copilot section with Latest Releases
- Copilot at Scale with changelog links
- Events section with YouTube playlists
- Closing section
Forbidden Patterns
- Raw URLs not in markdown links
- Em dashes
- Double-bracket links
[[ - Copilot Free/Individual/Pro/Pro+ plan mentions
- Wikilink format
- Customer-facing Copilot App release-process leakage (
github/github-app, anonymous fetch/404, private tags, authenticated release notes,[truncated]) - Legal/CCC content outside the active Enterprise/Security/Governance/Legal/Compliance heading path unless the issue is explicitly legal-led
- VS Code body-prose sequences with 3+
1.xxxversion numbers - Under-linked release-inventory bullets for Copilot App and high-volume Copilot CLI, using generic release-count/release-stream triggers rather than one month-specific count
- Specific-labeled inline links that point to a generic landing page instead of the deep/anchored source (WARN; see Link Specificity)
Link Specificity (Inline Deep-Link Policy)
Applies to inline contextual links in prose -- a link whose label names a specific feature, capability, or claim. Such a link must point to the most specific source that documents that exact thing: a section anchor, a dated changelog post, or a deep doc page. It must not point to a generic landing page, a bare version page, or a blog root.
What ships with it
4 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.
- 12d ago First seen · 120 lines · 57 tokens per session scan A b73c55fbb169
newsletter-validation is a skill published in the GitHub repository briancl2/CustomerNewsletter (11 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 1,770 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-running-evaluations
Execute TruLens evaluations and view results.
deepeval
Use when discussing or working with DeepEval (the python AI evaluation framework).
rust-development
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
iterative-refinement
Disciplined, measurable iteration for a substantial refinement or investigation: loop against verifiable pass/fail conditions, fan work out to subagents, and keep the main context lean. Use when improving something measurable over repeated cycles (tuning a metric or detector, refactoring against a regression bar)…
playwright-testing
Generer og kjør Playwright E2E-tester for webapplikasjoner med page objects, auth fixtures og tilgjengelighetstester.
diagnose-hard-problem
Disciplined diagnosis loop for hard problems, diagnosing bugs and regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test.