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/scope-contract/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/scope-contract)<a href="https://agentmods.dev/skills/briancl2/customernewsletter/scope-contract"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/scope-contract.svg" alt="Measured on agentmods" 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.00077 | $0.01635 |
| Opus 5 | $0.00039 | $0.00817 |
| Sonnet 5 | $0.00015 | $0.00327 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
scope-contract 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 6d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Contract
Generate a testable scope manifest before the pipeline runs, then validate the newsletter output against it after assembly.
Quick Start
Pre-Pipeline (Phase 0)
- Run
python3 tools/generate_scope_contract.py <START_DATE> <END_DATE>(the helper reads the date range from these arguments) - If it succeeds, use the generated manifest as the Phase 0 artifact
- Only fall back to manual source inspection if the helper cannot resolve the range
- Verify the output at
workspace/newsletter_scope_contract_YYYY-MM-DD.json
Post-Pipeline (after Phase 4.5)
- Read scope manifest
- Read final newsletter
- Run validation checks
- Write test results to
workspace/newsletter_scope_results_YYYY-MM-DD.md
Scope Manifest Format
{
"date_range": {
"start": "YYYY-MM-DD",
"end": "YYYY-MM-DD",
"previous_newsletter_end": "YYYY-MM-DD",
"gap_days": 0
},
"expected_versions": {
"vscode": ["v1.108", "v1.109"],
"visual_studio": ["18.2.x"],
"jetbrains": ["1.5.60", "1.5.61", "1.5.62", "1.5.63", "1.5.64"],
"xcode": ["0.46.0", "0.47.0"],
"copilot_cli": ["v0.0.400+"]
},
"expected_sources": [
"github.blog/changelog/YYYY/MM/",
"github.blog/news-insights/company-news/",
"code.visualstudio.com/updates/v1_NNN",
"plugins.jetbrains.com/api/plugins/17718/updates",
"github.com/github/CopilotForXcode/releases",
"devblogs.microsoft.com/visualstudio/",
"resources.github.com/events/"
],
"expected_categories": [
"Security & Compliance",
"AI & Automation",
"Platform & DevEx",
"Enterprise Administration",
"Code Quality",
"IDE Updates"
],
"expected_event_date_range": {
"earliest": "YYYY-MM-DD",
"latest": "YYYY-MM-DD"
}
}
Pre-Pipeline Workflow
Step 1: Determine Date Range Boundaries
- Read the requested DATE_RANGE (start, end)
- First try
python3 tools/generate_scope_contract.py <START_DATE> <END_DATE> - If the helper reuses an exact archived contract, keep that historical boundary metadata
- If the helper cannot resolve the range, inspect
archive/manually for the previous newsletter end date and any gap - Record in manifest
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.
- 6d ago First seen · 175 lines · 77 tokens per session scan A dd3e0d6d4134
scope-contract is a skill published in the GitHub repository briancl2/CustomerNewsletter (11 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 1,635 once invoked, about $0.0004 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-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…
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…