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.
npx skills add cenconq25/claude-code-app-studio --skill patch-notesgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/patch-notes)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/patch-notes"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/patch-notes/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.
<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/patch-notes"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/patch-notes.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.01364 |
| Opus 5 | $0.00023 | $0.00682 |
| Sonnet 5 | $0.00009 | $0.00273 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
patch-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 5d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patch Notes
A focused twin of /changelog. Produces only the user-facing,
store-ready patch notes for a release. Haiku tier — this is formatting
and rewording, not synthesis.
Phase 1: Locate Inputs
Parse --version=<v>. Default: most recent unreleased tag.
Read in parallel:
production/releases/changelog-internal-[version].md(preferred source).- If no internal changelog exists, read git log for the version window and any associated story / bug records.
.claude/docs/technical-preferences.mdfor target locales.
Phase 2: Pick the Tone
Parse --tone. If not given, propose options via AskUserQuestion:
warm— friendly, first-person plural ("We've added...").neutral— direct, third-person ("[App] now supports Apple Pay").formal— precise, legal-friendly ("Version [N] introduces support for Apple Pay").
Default: warm.
Apply the tone to every line consistently. Mixing tones is a smell.
Phase 3: Distill the Internal Changelog
For each entry in the internal source:
- Drop Internal / Refactor / Reverted entries unless user-visible.
- Drop test-only changes.
- Keep Features, Improvements, Fixes, Security in user-friendly form.
Apply rewriting rules:
- Replace developer terms with user terms: "reducer" -> drop; "background fetch" -> "while the app is closed"; "Hermes upgrade" -> "faster startup".
- Lead with user benefit: "Cold start improvements" -> "App opens faster".
- Avoid passive voice unless required by tone.
- Avoid "we fixed a bug where..." — be specific. "Sign-in no longer fails when switching from Wi-Fi to cellular."
- Keep entries punchy — one line per change unless context truly helps.
Phase 4: Compose Long Form
# What's New in [App] [version]
## New
- [bullet]
## Improvements
- [bullet]
## Fixes
- [bullet]
## Notes
[1-3 lines of plain language about anything users should know — new
permission, etc. Optional.]
Thanks for using [App]. Got feedback? [contact].
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.
- 5d ago First seen · 207 lines · 45 tokens per session scan A c9c04ac6f351
patch-notes is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 1,364 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…