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 agentmods add skills/friedbotstudio/baseline/whatsnewnpx skills add friedbotstudio/baseline --skill whatsnewgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/whatsnew)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/whatsnew"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/whatsnew.svg" alt="Measured on agentmods" 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 | $0.00126 | $0.00793 |
| Opus 5 | $0.00063 | $0.00396 |
| Sonnet 5 | $0.00025 | $0.00159 |
| Haiku 4.5 | $0.00013 | $0.00079 |
Grade A, and why
whatsnew 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 today.
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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
whatsnew — on-demand generator
Emits a structured "what's new" fragment for a set of changes. The fragment is a gitignored handoff buffer; a per-project routing workflow turns it into whatever surface the project wants. The generator makes no assumption about the destination, and it never touches CHANGELOG.md — semantic-release owns that file at release time.
This skill is not a mandatory workflow phase. It is invoked on demand (and, when a project wires whatsnew.route_workflow, handed off to that routing workflow). Version is never stored in the fragment: the routing target reads the shipped version at publish time.
Steps
- Build the entries (main context). Decide the keepachangelog entries for the change — one object per user-visible change, not per file. Write a JSON array to an entries file (for example under
.claude/state/whatsnew/), each object shaped{ "category": "<Added|Changed|Deprecated|Removed|Fixed|Security>", "title": "<short headline>", "body": "<one or two sentences>", "highlight": <bool, optional> }. - Run the generator. Invoke the entrypoint with
--slug <slug> --entries-file <path>(optionally--project-root <root>). It validates the entries, writes the fragment to.claude/state/whatsnew/<slug>.json, and resolves the optional routing target. - Routing (optional). If
project.json → whatsnew.route_workflownames a workflow, that workflow is the documented consumer of the fragment; it reads the fragment and writes its own committed output. If the knob is absent ornull, the generator still succeeds and the fragment simply sits at the conventional path unconsumed.
Companion files
whatsnew.mjs— the generator entrypoint. Reads the entries file, writes the fragment, reports the routing target.fragment-writer.mjs— validates entries and serializes the fragment{ slug, generated_at, entries[{category, title, body, highlight?}] }. No version field.route-resolver.mjs— resolvesproject.json → whatsnew.route_workflow(string track id, ornullby read-time default).classifier.mjs— defines the canonical keepachangelog category set thatfragment-writer.mjsvalidates entries against.
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.
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.
- today First seen · 33 lines · 126 tokens per session scan A 103c67707d80
whatsnew is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed yesterday), licensed Apache-2.0. It adds 126 tokens to every session and 793 once invoked, about $0.0006 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
release
The single permitted path to a version tag, for any target declared in the project's .codearbiter/release-targets.md. Routed to when the user invokes /release on a non-default branch with a green suite. Takes the declared target as its one argument, derives the SemVer bump from Conventional-Commits history since that…
ca-pr
Open a pull request the only sanctioned way — clear every BLOCK-level review finding, then stage the PR. Never a direct write to the default branch.
ca-release
Cut a release the only sanctioned way — SemVer bump from the commit log, a CHANGELOG section, an annotated tag. Takes the declared target's name as its only argument, or --dry-run to preview one with no write. The only path to a version tag.
probe
Report this absolute source path, then read the nested routine.
dev-standards
Enforces development workflows, quality gates, coding standards, and release processes for the deterministic-agent-control-protocol project. Use when implementing features, fixing bugs, refactoring architecture, adding integrations, updating policies, writing tests, updating documentation, or preparing releases.
brainstorming
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an approved, concrete spec with testable acceptance criteria. Five gated phases — frame, shape, refine, write, review-and-approve. No implementation and no handoff to…