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/curator-notes/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/curator-notes)<a href="https://agentmods.dev/skills/briancl2/customernewsletter/curator-notes"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/curator-notes.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.00096 | $0.01797 |
| Opus 5 | $0.00048 | $0.00898 |
| Sonnet 5 | $0.00019 | $0.00359 |
| Haiku 4.5 | $0.00010 | $0.00180 |
Grade A, and why
curator-notes 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 8d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curator Notes Processing
Process the human curator's monthly notes file into pipeline-ready content and editorial signals.
Quick Start
- Check for
workspace/curator_notes_YYYY-MM.md(or known variants) - If no file exists, skip this phase entirely -- pipeline continues normally
- Parse and classify every item using the link type taxonomy
- Filter: internal links become editorial signals; public links get visited
- Output processed items + editorial signals
- Items feed into Phase 3 curation alongside Phase 1C discoveries
Inputs
- Curator notes file (optional):
workspace/curator_notes_YYYY-MM.md- May also appear as:
workspace/<month>.md,workspace/<Month>.md,workspace/Jan.md, etc. - Check for any
.mdfile inworkspace/that looks like a brain dump of links
- May also appear as:
- Phase 1C Discoveries: For cross-reference (avoid duplicates)
Output
workspace/curator_notes_processed_YYYY-MM.md-- Items in universal extraction format, ready for Phase 3workspace/curator_notes_editorial_signals_YYYY-MM.md-- Priority hints, theme suggestions, internal context
Core Workflow
Step 0: Locate the Notes File
Check these paths in order:
workspace/curator_notes_YYYY-MM.md(canonical)workspace/<Month>.md(e.g.,workspace/Jan.md,workspace/February.md)- Any
.mdfile inworkspace/containing 3+ URLs that isn't a pipeline output
If no file found: SKIP. Output nothing. Pipeline continues.
Step 1: Parse and Classify
For each line/item in the notes file, classify into one of these types:
| Type | Detection Pattern | Action |
|---|---|---|
| GitHub Changelog | github.blog/changelog/ |
PROCESS: visit URL, extract item |
| GitHub Blog | github.blog/news-insights/ or github.blog/ai-and-ml/ |
PROCESS: visit URL, extract item |
| VS Code Release Notes | code.visualstudio.com/updates/ |
PROCESS: visit URL, extract features |
| Microsoft DevBlog | devblogs.microsoft.com/ |
PROCESS: visit if GitHub-specific |
| Community resource | github.com/<user>/, personal sites, awesome-lists |
PROCESS: visit URL, extract description |
| VS Code extension | marketplace.visualstudio.com/ |
PROCESS: visit URL, extract description |
| YouTube video | youtube.com/watch, youtu.be/ |
PROCESS: visit, extract title and context |
| Event registration | registration.goldcast.io/, github.com/resources/events/ |
PROCESS: extract event details |
| Named feature hint | Text line without URL referencing a product name | SIGNAL: flag as editorial priority |
| Internal link | github.slack.com/, docs.google.com/, github.com/github/ (private repos), thehub.github.com/ |
SIGNAL: translate topic to public reference |
| Industry content | hbr.org/, substack.com/, medium.com/, martinfowler.com/, analyst reports |
SIGNAL: framing context only |
| Competitor content | blog.cloudflare.com/, sonarsource.com/, etc. |
SIGNAL: competitive context only |
| Text note (vague) | Bare text, no URL, no product name | SIGNAL: note for context |
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.
- 8d ago First seen · 160 lines · 96 tokens per session scan A d1c6d5a81759
curator-notes is a skill published in the GitHub repository briancl2/CustomerNewsletter (11 stars, last pushed 3mo ago), licensed MIT. It adds 96 tokens to every session and 1,797 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…
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…