delta-briefing

delta-briefing is a skill for Claude Code from mohitagw15856/pm-claude-skills. It costs 70 tokens per session (998 once invoked), scanned A, original, MIT.

A format for recurring reports that compares the current situation with the previous edition and leads with new, changed, resolved, or still-watched items. It also saves a compact record for the next comparison.

In plain words
What is it for?
Use it for competitive updates, product metrics, account health reports, scheduled monitors, and other recurring briefings.
Why use it?
Weekly and monthly reports often repeat old information, making important changes hard to find.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pm-autopilot plugin — 7 skills shipped together

Good fit Use it for competitive updates, product metrics, account health reports, scheduled monitors, and other recurring briefings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mohitagw15856/pm-claude-skills/delta-briefing
About the project

PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.

mohitagw15856/pm-claude-skills · 1,449 stars · on GitHub · mohitagw15856.github.io

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add mohitagw15856/pm-claude-skills --skill delta-briefing
Clone the repo
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills

Made for: Claude Code.

Or install pm-autopilot, the plugin that ships this one along with the rest of its 7 skills.

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 delta-briefing

README.md
[![agentmods](https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/delta-briefing/github.svg)](https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/delta-briefing)
Your own site
<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/delta-briefing"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/delta-briefing/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 delta-briefing

Your own site · 80×15
<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/delta-briefing"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/delta-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 998 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.00070 $0.00998
Opus 5.5 $0.00028 $0.00399
Sonnet 5.5 $0.00014 $0.00200
Haiku 4.5 $0.00007 $0.00100

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

Security

Grade A, and why

delta-briefing 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 2d 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.

plugins/pm-autopilot/skills/delta-briefing/SKILL.md · 87 lines

How it starts

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

Delta Briefing Skill

The failure mode of every recurring report is that edition 6 reads like edition 5. This skill structures a recurring brief around the delta: read the last edition's state, diff the world against it, lead with what changed, and save state for the next run.

What This Skill Produces

  • A changes-first brief: new / changed / resolved / unchanged-but-watched
  • A state record (compact, machine-readable) that the next edition diffs against
  • An explicit "nothing changed" edition format — short, honest, and still useful

Required Inputs

Ask for (if not already provided):

  • The brief's subject and audience (competitive landscape, product metrics, account health…)
  • The previous edition or state record — if none exists, this run is the baseline: say so in the output and produce the first state record
  • Current sources for this cycle
  • Where state lives between runs (a file next to the brief, a Brain folder — see BRAIN.md if using this library's memory)

Delta Method

  1. Load last state. Parse the previous state record (or previous edition if that's all there is). List the items it tracked and their status.
  2. Re-observe. Gather this cycle's facts from the sources — independently of the old state, so removals are caught too.
  3. Diff into four buckets:
    • New — present now, absent last time
    • Changed — tracked before, materially different now (state what moved, old → new)
    • Resolved / gone — tracked before, no longer present or no longer a concern
    • Watching — unchanged but still worth tracking (compressed to one line each)
  4. Judge materiality. A delta makes the brief only if the audience would act differently knowing it. Trivia goes to the state record, not the brief.
  5. Write state for next time. Every tracked item, its current status, the date, and the sources read.

Output Format

[Brief name] — [date] (edition [n], previous: [date])

TL;DR: [1-2 sentences: the most consequential delta, or "no material changes"]

Read the full file on GitHub · 87 lines

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. 2d ago First seen · 87 lines · 70 tokens per session scan A 764424e9f261

Subscribe to this mod's changes

delta-briefing is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 998 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-10-12.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens