agentmods.dev

CustomerNewsletter: Skill for Claude Code

.github/skills/url-manifest/SKILL.md

url-manifest is a skill for Claude Code, Codex from briancl2/CustomerNewsletter. It costs 73 tokens per session (1,368 once invoked), scanned A, original, MIT.

A newsletter-pipeline step that creates and checks a list of candidate web addresses from SOURCES.yaml for a specified date range. SOURCES.yaml is a file containing the newsletter’s known source addresses and feeds.

In plain words
What is it for?
Use it at the start of Phase 1A to generate a dated URL manifest from sources such as feeds and canonical pages.
Why use it?
It gives later pipeline stages a validated set of pages to investigate and checks that the date range does not leave gaps between newsletters.

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 →

not rated 11repo 3mo ago A scan 73 tokens original MIT
View source ↗ briancl2/CustomerNewsletter briancl2.github.io
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/url-manifest/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 url-manifest

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/briancl2/customernewsletter/url-manifest"><img src="https://agentmods.dev/badge/skills/briancl2/customernewsletter/url-manifest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,368 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.00073 $0.01368
Opus 5 $0.00036 $0.00684
Sonnet 5 $0.00015 $0.00274
Haiku 4.5 $0.00007 $0.00137

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

Security

Grade A, and why

url-manifest 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/url-manifest/SKILL.md · 118 lines

How it starts

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

URL Manifest Generator

Generate and validate candidate URLs from known sources for a given DATE_RANGE.

Quick Start

  1. Receive DATE_RANGE (YYYY-MM-DD to YYYY-MM-DD)
  2. Read kb/SOURCES.yaml for canonical URLs and feed endpoints
  3. Generate candidate URLs per source using known patterns
  4. Spot-check 1-2 URLs per source to confirm patterns work
  5. Write manifest to workspace/newsletter_phase1a_url_manifest_YYYY-MM-DD_to_YYYY-MM-DD.md

Inputs

  • DATE_RANGE: Start date and end date in YYYY-MM-DD format
  • Reference Year: Extracted from DATE_RANGE
  • kb/SOURCES.yaml: Canonical URL source with 47 machine-readable entries

Output

  • File: workspace/newsletter_phase1a_url_manifest_YYYY-MM-DD_to_YYYY-MM-DD.md
  • Token budget: 10,000-20,000 tokens total

Core Workflow

Step 0: Date Range Overlap Check

Before generating URLs, verify DATE_RANGE has no gap with the previous newsletter. Check archive/ for the most recent newsletter to find its coverage end date. If a gap exists (e.g., previous newsletter covered through Dec 3, but current DATE_RANGE starts Jan 1), extend the START date backward to close the gap. Never leave uncovered days between newsletters.

Step 1: Generate Candidates (~2 min)

For each source, generate candidate URLs using known patterns and DATE_RANGE months. See url-patterns.md for per-source URL architecture.

Key Innovation: Read kb/SOURCES.yaml for canonical URLs rather than guessing URL patterns. The YAML provides:

  • canonical_urls for each source
  • update_feeds with type (RSS, Atom, API, none) and endpoints
  • latest_known.version and latest_known.release_date for version-based URLs

CRITICAL: VS Code Version Enumeration (L64 + L66)

Do NOT rely on SOURCES.yaml latest_known.version alone for VS Code. That field only contains the newest version. VS Code now ships weekly, so a 30+ day DATE_RANGE includes 4-5+ versions. You MUST:

  1. Fetch https://code.visualstudio.com/updates (the index page)
  2. Parse every version listed with its actual release date
  3. Include ALL versions whose release date falls within DATE_RANGE
  4. Remember: named months may still lag by 1-2 months ("December 2025" = released Jan 8, 2026)

Read the full file on GitHub · 118 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 · 118 lines · 73 tokens per session scan A 248a7ebef142

Subscribe to this mod's changes

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

Researchagentic-workflowsagentscopilotllmopsmkdocsnewsletter
Related

Other skills, from other repositories

trulens-diagnosis

Diagnose low evaluation scores and generate actionable improvement recommendations.

truera/trulens · 17 tokens

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…

microsoft/Agents · 76 tokens

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…

microsoft/Agents · 112 tokens

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…

microsoft/Agents · 131 tokens

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…

microsoft/Agents · 88 tokens

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…

microsoft/Agents · 86 tokens