CustomerNewsletter: Skill for Claude Code

.github/skills/content-consolidation/SKILL.md

content-consolidation is a skill for Claude Code, Codex from briancl2/CustomerNewsletter. It costs 77 tokens per session (1,456 once invoked), scanned A, original, MIT.

A document-processing step for a newsletter pipeline that combines five interim files into one list of relevant discoveries.

In plain words
What is it for?
Use it after Phase 1B to merge files from GitHub, VS Code, Visual Studio, JetBrains, and Xcode, group discoveries into five categories, and write the consolidated result to a Markdown file.
Why use it?
It removes repeated entries and filters out items that are not useful for enterprise readers, so the newsletter work starts with a cleaner list.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is briancl2/CustomerNewsletter's own configuration. It tells Claude Code and Codex how to work on CustomerNewsletter itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything CustomerNewsletter configures →

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-consolidation/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.

agentmods badge for content-consolidation

README.md
[![agentmods](https://agentmods.dev/badge/skills/briancl2/customernewsletter/content-consolidation/github.svg)](https://agentmods.dev/skills/briancl2/customernewsletter/content-consolidation)
Your own site
<a href="https://agentmods.dev/skills/briancl2/customernewsletter/content-consolidation"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/content-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.

agentmods 80×15 button for content-consolidation

Your own site · 80×15
<a href="https://agentmods.dev/skills/briancl2/customernewsletter/content-consolidation"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/content-consolidation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,456 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.01456
Opus 5 $0.00039 $0.00728
Sonnet 5 $0.00015 $0.00291
Haiku 4.5 $0.00008 $0.00146

Measured 11d ago against content hash 7829ed348472, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

content-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 11d 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-consolidation/SKILL.md · 123 lines

How it starts

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

Content Consolidation

Merge, deduplicate, and filter 5 Phase 1B interim files into a single discoveries document.

Quick Start

  1. Read all 5 interim files from Phase 1B
  2. Aggregate items into a working list with source tracking
  3. Deduplicate: same feature from multiple sources becomes one item
  4. Categorize into 5 taxonomy categories
  5. Filter for enterprise relevance (score 5+)
  6. Write output to workspace/newsletter_phase1a_discoveries_YYYY-MM-DD_to_YYYY-MM-DD.md

Inputs

All 5 Phase 1B interim files (required):

  • workspace/newsletter_phase1b_interim_github_*.md
  • workspace/newsletter_phase1b_interim_vscode_*.md
  • workspace/newsletter_phase1b_interim_visualstudio_*.md
  • workspace/newsletter_phase1b_interim_jetbrains_*.md
  • workspace/newsletter_phase1b_interim_xcode_*.md

Output

  • File: workspace/newsletter_phase1a_discoveries_YYYY-MM-DD_to_YYYY-MM-DD.md
  • Target: 20-40 items with balanced category distribution

Legacy naming note: The output filename uses phase1a_discoveries despite being produced by Phase 1C. This is a historical convention preserved for compatibility with benchmark data, archived intermediates, and downstream prompt references. All downstream consumers (content-curation, prompts, agent) reference this exact name pattern.

Core Workflow

Key finding (see reference/source-intelligence/meta-analysis.md): Cross-cycle analysis shows the pipeline does NOT cut items. 100% discovery survival in Aug+Jun+May 2025. The real editorial value is in ADDITIONS (Azure, devblogs, resources), BUNDLING (models, parity, governance), and EXPANSION (flagships). This phase should ENRICH and CONSOLIDATE, not just filter.

Step 1: Aggregate

Read all 5 interim files. For each item, record: source file, date, title, URLs, status (GA/PREVIEW), relevance score, IDE support.

Step 1.5: Enrich (Gap-Filling)

Check for known under-discovery gaps (L29, L30, L31). These sources are consistently missing from Phase 1B output but always appear in published newsletters:

Read the full file on GitHub · 123 lines

Files

What ships with it

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

  1. 11d ago First seen · 123 lines · 77 tokens per session scan A 7829ed348472

Subscribe to this mod's changes

content-consolidation is a skill published in the GitHub repository briancl2/CustomerNewsletter (11 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 1,456 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.

Related

Other skills, from other repositories

pptx-to-md

Convert a PPTX slide deck into per-slide markdown that preserves both the verbatim text and the meaning of embedded screenshots, diagrams and charts in their original layout positions. Use this skill (over pptx or liteparse) whenever the deliverable is markdown of a deck's content including interpreted visuals.

sammcj/agentic-coding · 64 tokens

glean-cli

Provides knowledge on using the glean CLI tool to access company knowledge and documents through Glean. Use when the user asks you to use Glean to search, read or otherwise access knowledge from their company's Confluence, Slack, Google Drive Files (Slides, Documents, Sheets) etc.

sammcj/agentic-coding · 63 tokens

liteparse

Provides fast document to markdown extraction. Use this skill when the user asks to parse, perform multi-format document conversion or spatially extract text from an unstructured file (PDF, DOCX, PPTX, XLSX, images, etc.) locally.

sammcj/agentic-coding · 53 tokens

python-pptx-generator

Generate complete Python scripts that build polished PowerPoint decks with python-pptx and real slide content.

beel-collab/presets.dev · 20 tokens

code-documentation-doc-generate

You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.

beel-collab/presets.dev · 38 tokens

foundry-hosted-agent-validation

Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.

microsoft/agent-framework · 82 tokens