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 jcottam/agent-resources --skill release-notesgit clone --depth 1 https://github.com/jcottam/agent-resourcesWrote 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/jcottam/agent-resources/release-notes)<a href="https://agentmods.dev/skills/jcottam/agent-resources/release-notes"><img src="https://agentmods.dev/badge/skills/jcottam/agent-resources/release-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/jcottam/agent-resources/release-notes"><img src="https://agentmods.dev/badge/skills/jcottam/agent-resources/release-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.00087 | $0.01677 |
| Opus 5.5 | $0.00035 | $0.00671 |
| Sonnet 5.5 | $0.00017 | $0.00335 |
| Haiku 4.5 | $0.00009 | $0.00168 |
Grade A, and why
release-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 26d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes
Turn a logical grouping of commits into clear summaries for teammates, stakeholders, or changelogs — not developer jargon.
Workflow
1. Choose the boundary (required)
Ask which grouping of commits to summarize before gathering history or writing notes. Do not assume. Do not default to "recent commits."
If the user already named a boundary in this request, use it. Otherwise ask once and wait:
Which commits should these notes cover?
- This branch — commits on the current branch that are not on the default
base (usually
main) - A PR — commits in a pull request (number, URL, or this branch's open PR)
- Recent commits — only when the user chooses this; they must name a count, date, or tag
Do not gather git history or draft notes until the boundary is known.
Follow-ups after they pick:
| They chose | If still missing, ask |
|---|---|
| A PR | Which PR (number, URL), unless the current branch already has one |
| Recent commits | How far back (last N commits, since a date, or since a tag) |
| This branch | Nothing — detect the base and proceed |
Author, path, or extra filters are optional refinements after the boundary is set, not a substitute for it.
2. Gather that range
Run read-only git commands. Do not commit, push, or edit files unless the user explicitly asks.
Detect the default base with git symbolic-ref refs/remotes/origin/HEAD (fall
back to origin/main or origin/master).
| Boundary | Range |
|---|---|
| This branch | <base>..HEAD on the current branch. If HEAD is already the default branch, say so and ask for another boundary — there is no unique branch range. |
| A PR | Commits on the PR head that are not on its base. Prefer gh pr view [<n>|URL] --json title,baseRefName,headRefName,commits when GitHub CLI is available; otherwise git log <pr-base>..<pr-head>. |
| Recent commits | Exactly the window they named: git log --oneline -<n>, --since=<date>, or <tag>..HEAD. Do not invent a count. |
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.
- 26d ago First seen · 191 lines · 87 tokens per session scan A 2726866c3d0c
release-notes is a skill published in the GitHub repository jcottam/agent-resources (29 stars, last pushed 8d ago), licensed MIT. It adds 87 tokens to every session and 1,677 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-09-21.
Other skills, from other repositories
capgo-release-management
Runs Capgo OTA release operations with the CLI, including bundle upload (channels, delta, rollout, encryption, version bumps), bundle compatibility and releaseType checks, channel add/set/promote/currentBundle/delete, progressive rollouts and rollback, bundle cleanup, preview QR codes, and key create/save encryption…
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
apply-semantic-versioning
Apply semantic versioning (SemVer 2.0.0) to determine the correct version bump based on change analysis. Covers major/minor/patch classification, pre-release identifiers, build metadata, and breaking change detection. Use when preparing a new release to determine the correct version number, after merging changes…
create-github-release
Create a GitHub release with proper tagging, release notes, and optional build artifacts. Covers semantic versioning, changelog generation, and GitHub CLI usage. Use when marking a stable version of software for distribution, publishing a new library or application version, creating release notes for stakeholders, or…
publish-vscode-extension
Publish a VS Code extension to the VS Code Marketplace and/or Open VSX Registry. Use when the user wants to publish, ship, or release a VS Code extension; audit or improve manifest, listing, or release setup; build or upload a .vsix; set up vsce or ovsx; create a marketplace publisher or Open VSX namespace; configure…
npm-publish
Prepare an npm package for publishing. Handles version bump, CHANGELOG update, typings check, test run, README refresh, package.json audit, and npm pack verification. Use when the user asks to prepare a release, bump version, publish a package, or do release prep.