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/deprecation-consolidation/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/deprecation-consolidation)<a href="https://agentmods.dev/skills/briancl2/customernewsletter/deprecation-consolidation"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/deprecation-consolidation/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/deprecation-consolidation"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/deprecation-consolidation.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.00107 | $0.00769 |
| Opus 5 | $0.00053 | $0.00385 |
| Sonnet 5 | $0.00021 | $0.00154 |
| Haiku 4.5 | $0.00011 | $0.00077 |
Grade A, and why
deprecation-consolidation 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deprecation Consolidation
Ensure deprecations and migration notices are not duplicated across the newsletter and are presented once in the right place.
Quick Start
- Read the assembled newsletter file at
output/YYYY-MM_month_newsletter.md. - Find all deprecation/migration/sunset content anywhere in the document.
- Move it into a single bundled bullet under Enterprise and Security Updates.
- Delete any standalone
# Migration Noticessection. - Re-run validation:
bash .github/skills/newsletter-validation/scripts/validate_newsletter.sh output/YYYY-MM_month_newsletter.md.
Core Rules (Hard Requirements)
Rule 1: Single bundled update
All of these belong in one bullet (one paragraph) under Enterprise and Security Updates:
- Deprecations (models/features/SDKs)
- Sunsets / API shutdowns
- Token revocations
- Minimum version enforcement
- Syntax changes that can break workflows (e.g., comment commands)
Use a title like:
**Deprecations and Migration Notices** -- ...
Rule 2: No bottom-of-newsletter migration section
Do not end the newsletter with a standalone section like:
# Migration Notices
If it exists, it must be removed and its content merged into the Enterprise & Security bullet.
Rule 3: Remove duplicate mentions elsewhere
If deprecation content appears in other bullets (common places: model availability bullets, metrics bullets), do one of:
- Remove the deprecation sentence/link entirely, OR
- Replace it with a short pointer: "See Deprecations and Migration Notices in Enterprise and Security Updates."
Prefer removal over pointers unless the section would otherwise become misleading.
Editing Workflow
- Inventory: Identify every deprecation/migration statement and every link that implies deprecation (e.g.,
upcoming-deprecation,closing-down-notice,revoked,minimum-version-enforcement). - Choose canonical placement: Under Enterprise and Security Updates, immediately after the most related bullet (often metrics/governance).
- Bundle: Write one bullet that lists the items as bolded phrases in a single sentence/paragraph.
- Linking: Include the authoritative links (usually changelog entries) as pipe-separated links at the end.
- Delete old section: Remove
# Migration Noticesheading and its bullet(s). - Re-scan for dupes: Ensure the same deprecation link doesn’t appear in multiple sections.
What ships with it
1 file 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 · 75 lines · 107 tokens per session scan A 9e10344cc31b
deprecation-consolidation is a skill published in the GitHub repository briancl2/CustomerNewsletter (11 stars, last pushed 3mo ago), licensed MIT. It adds 107 tokens to every session and 769 once invoked, about $0.0005 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…
bf-to-agents-sdk-dotnet-migration
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.
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…