Borrowing it
Nothing to install: this file belongs to code-payments/code-android-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/code-payments/code-android-app/code/cash/.claude/skills/release-notes/SKILL.mdgit clone --depth 1 https://github.com/code-payments/code-android-appWrote 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/code-payments/code-android-app/release-notes)<a href="https://agentmods.dev/skills/code-payments/code-android-app/release-notes"><img src="https://agentmods.dev/badge/skills/code-payments/code-android-app/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/code-payments/code-android-app/release-notes"><img src="https://agentmods.dev/badge/skills/code-payments/code-android-app/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.01049 |
| Opus 5.5 | $0.00020 | $0.00420 |
| Sonnet 5.5 | $0.00010 | $0.00210 |
| Haiku 4.5 | $0.00005 | $0.00105 |
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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
Generate polished GitHub release notes for the code-android-app repository.
Pre-flight context
- Latest tag: !
git describe --tags --match 'fcash/*' --abbrev=0 HEAD 2>/dev/null || echo "no tags found" - All recent tags: !
git tag --sort=-creatordate | head -10
Input
Parse the two refs from $ARGUMENTS. Each ref can be a tag, a commit SHA, a commit number (Nth commit in repo history), or HEAD:
/release-notes fcash/2026.4.10 fcash/2026.4.11/release-notes fcash/2026.4.9 HEAD/release-notes a3f2417 HEAD/release-notes 3599 HEAD(from the 3599th commit to HEAD)
If only one ref is provided, use it as <from> and default <to> to HEAD.
If no refs are provided, use the pre-flight latest tag as <from> and HEAD as <to>.
Steps
1. Run the changelog script
bash scripts/changelog.sh <from_tag> <to_tag>
Display the raw output for the user to see.
2. Rewrite into release notes
Use the Agent tool with model: "haiku". Pass the raw changelog output with this prompt:
Given these git commits (conventional commit format), write user-facing release notes.
Rules:
- Group under: Features, Bug Fixes, Improvements, Dependencies (omit empty sections)
- Write for end users — no jargon, file names, or internals
- One short sentence per item
- Group related commits into a single bullet when they address the same area
- Use scope as context but write in plain language; keep scope in bold prefix when it adds clarity
- Include every bug fix; drop only pure refactors, CI pipeline changes, and release/manifest bookkeeping
- Feature bullets start with a lowercase verb (e.g., "add", "support", "enable")
- Bug fix bullets start with "Fixed" (capitalized)
- Dependencies section: list each dependency bump as
Name X.Y.Z → A.B.C(use the human-readable library name, not the Maven coordinate). Include targetSdkVersion and Gradle wrapper bumps in this section too.- Use 2-space indent before each bullet (
-)- Do NOT include commit hashes
- If no user-facing changes, output: Bug fixes and performance improvements.
- Output ONLY the section markdown, no title or fences
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.
- 1mo ago Changed 90dcfe82c5df
- 2mo ago First seen · 102 lines · 50 tokens per session scan A 89a8cdc0f89d
release-notes is a skill published in the GitHub repository code-payments/code-android-app (23 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,049 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.