What is content-curation?

A newsletter-pipeline step that selects and organizes items from a Phase 3 working set into complete newsletter sections. Phase 3 is the stage where gathered material is chosen and shaped for publication.

Use it during Phase 3 to prepare sections such as Lead, Copilot, Enterprise and Security, Platform, and Resources.

It provides a defined structure for turning collected material into newsletter-ready sections and uses earlier discoveries only when the working set is missing information.

How briancl2/CustomerNewsletter configures Claude Code and Codex

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/briancl2/CustomerNewsletter/main/.github/skills/content-curation/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/briancl2/CustomerNewsletter

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/briancl2/customernewsletter/content-curation/github.svg)](https://agentmods.dev/skills/briancl2/customernewsletter/content-curation)

Your own site

<a href="https://agentmods.dev/skills/briancl2/customernewsletter/content-curation"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/content-curation/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/briancl2/customernewsletter/content-curation"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/content-curation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,066 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00085	$0.03066
Opus 5.5	$0.00034	$0.01226
Sonnet 5.5	$0.00017	$0.00613
Haiku 4.5	$0.00009	$0.00307

Measured 2mo ago against content hash 86bddfb06177, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

content-curation 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 2mo 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.

.github/skills/content-curation/SKILL.md · 202 lines

How it starts

The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Content Curation

Transform the Phase 3 working set into polished, newsletter-ready content sections, using Phase 1C discoveries only when the working set flags missing data.

Quick Start

In orchestrated runs, first generate workspace/newsletter_phase3_working_set_YYYY-MM-DD.md with python3 tools/build_phase3_working_set.py START END
If workspace/newsletter_phase3_curated_sections_YYYY-MM-DD.md does not exist yet, create the canonical scaffold with python3 tools/init_phase3_curated_sections.py START END
Always edit the canonical scaffold in place. Do not create the curated sections artifact ad hoc through a generic create-file flow
If the working set exists, use it as the primary Phase 3 input and do not reread raw discoveries, interim IDE files, or long reference docs unless it explicitly flags missing data
Read Phase 1C discoveries from workspace/newsletter_phase1a_discoveries_*.md when no working set exists or the working set flags missing data
Select items using selection criteria with range-aware depth targets
Organize into full newsletter sections: Lead (optional), Copilot (Latest + IDE Parity), Enterprise and Security, Platform, Resources and Best Practices
Apply formatting: bold terms, GA/PREVIEW labels, embedded links, strip metadata
Validate the edited artifact with python3 tools/validate_phase3_curated.py START END workspace/newsletter_phase3_curated_sections_YYYY-MM-DD.md

Inputs

Phase 3 Working Set: workspace/newsletter_phase3_working_set_*.md (primary input in orchestrated mode)
Phase 1C Discoveries: workspace/newsletter_phase1a_discoveries_*.md (fallback only when the working set is absent or flags missing data)

Output

File: workspace/newsletter_phase3_curated_sections_YYYY-MM-DD.md
Target: range-aware depth
- =60-day range: 24+ curated bullets
- =30-day range: 18+ curated bullets
- <30-day range: 12+ curated bullets
Content: Full section-ready material (no final intro/closing text)

Read the full file on GitHub · 202 lines

Files

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.

Changes

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.

2mo ago First seen · 202 lines · 85 tokens per session scan A 86bddfb06177

Subscribe to this mod's changes

content-curation is a skill published in the GitHub repository briancl2/CustomerNewsletter (11 stars, last pushed 5mo ago), licensed MIT. It adds 85 tokens to every session and 3,066 once invoked, about $0.0003 per session on Opus 5.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.

Marketing and SEO Writing and docs agentic-workflows agents copilot llmops mkdocs newsletter

content-curation next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
content-curationbriancl2/CustomerNewsletter	Skill	11	5mo ago	MIT	A	85	Claude Code, Codex
trulens-diagnosistruera/trulens	Skill	3.6k	yesterday	MIT	A	17	Claude Code, Codex
agents-sdk-dotnet-activityhandler-migrationmicrosoft/Agents	Skill	1.1k	yesterday	MIT	A	76	Claude Code
agents-sdk-dotnetmicrosoft/Agents	Skill	1.1k	yesterday	MIT	A	112	Claude Code
agents-sdk-typescript-otelmicrosoft/Agents	Skill	1.1k	yesterday	MIT	A	88	Claude Code
bf-to-agents-sdk-dotnet-migrationmicrosoft/Agents	Skill	1.1k	yesterday	MIT	A	56	Claude Code
github-review-prfeiskyer/claude-code-settings	Skill	1.7k	yesterday	MIT	A	90	Claude Code

CustomerNewsletter: Skill for Claude Code