Starcat: Skill for Claude Code

.claude/skills/update-changelog/SKILL.md

update-changelog is a skill for Claude Code from starcat-app/Starcat. It costs 96 tokens per session (3,354 once invoked), scanned A, original, MIT.

A project-specific procedure for creating Starcat release notes from the main project's Git commits in English and Chinese.

In plain words
What is it for?
It helps update Starcat's English and Chinese changelogs after the user provides a semantic version number such as 1.2.0.
Why use it?
It removes the manual work of reviewing commits, grouping changes, and keeping both changelog files synchronized.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is starcat-app/Starcat's own configuration. It tells Claude Code how to work on Starcat itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Starcat configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is STARCAT_NOTARIZE=1 STARCAT_RELEASE_SKIP_TAG=1 ./scripts/release-direct.sh <version>.

Reuse

Borrowing it

Nothing to install: this file belongs to starcat-app/Starcat. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/starcat-app/Starcat/main/.claude/skills/update-changelog/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/starcat-app/Starcat

Made for: Claude Code.

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 update-changelog

README.md
[![agentmods](https://agentmods.dev/badge/skills/starcat-app/starcat/update-changelog/github.svg)](https://agentmods.dev/skills/starcat-app/starcat/update-changelog)
Your own site
<a href="https://agentmods.dev/skills/starcat-app/starcat/update-changelog"><img src="https://agentmods.dev/badge/skills/starcat-app/starcat/update-changelog/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 update-changelog

Your own site · 80×15
<a href="https://agentmods.dev/skills/starcat-app/starcat/update-changelog"><img src="https://agentmods.dev/badge/skills/starcat-app/starcat/update-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,354 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00096 $0.03354
Opus 5 $0.00048 $0.01677
Sonnet 5 $0.00019 $0.00671
Haiku 4.5 $0.00010 $0.00335

Measured 10d ago against content hash 2491cfb656ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

update-changelog scanned grade A with 1 finding 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 10d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Requires: `git`, `python3`, `rsync`, `ssh`, `curl`
.claude/skills/update-changelog/SKILL.md · 345 lines

How it starts

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

Update Starcat Changelog

Read ALL git commits from the main Starcat project since the last version tag, then update CHANGELOG.md (English) and CHANGELOG-ZH.md (Chinese) in supports/starcat-pro/.

File Locations

File Path
Changelog (EN) supports/starcat-pro/CHANGELOG.md
Changelog (ZH) supports/starcat-pro/CHANGELOG-ZH.md
Git repo (source) Starcat root (the Xcode project)

Step 0: Ask for Version Number (MANDATORY — Do This FIRST)

This is a blocking step. Before reading any git log or touching any file, you MUST know the target version number. If the user did not provide one in their invocation, immediately ask:

"Which version number should I use for this changelog entry? (e.g., 1.2.0, 1.1.1)"

Do NOT proceed to Step 1 until the user answers. Do NOT guess or assume a version number.

If the user's invocation already includes a version number (e.g., "update changelog for 1.2.0"), validate that it matches X.Y.Z format. If it doesn't, ask the user to provide a valid format.

The version number must be in X.Y.Z format (semantic versioning) because release-direct.sh requires this format.


Step 1: Determine Commit Range

# Latest tag
git tag --sort=-creatordate | head -1

# All commits since that tag (NO filtering, NO skip)
git log <latest-tag>..HEAD --oneline --no-merges

# Count
git log <latest-tag>..HEAD --oneline --no-merges | wc -l

If no tag exists, start from the first commit.

If there are 0 commits since the latest tag, stop and tell the user: "No new commits since . There's nothing to add to the changelog."


Step 2: Read EVERY Commit Message (Do NOT Skip Any)

# Full messages for ALL non-merge commits — every single one
git log <latest-tag>..HEAD --format="---COMMIT---%n%h%n%s%n%b" --no-merges

Critical rule: Read EVERY commit first. Then in Step 3a, filter out non-user-facing changes. Don't skip commits at read time — some commits with non-standard prefixes may still describe user-visible changes. The filtering happens AFTER reading, based on content.

Read the full file on GitHub · 345 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. 10d ago First seen · 345 lines · 96 tokens per session scan A 2491cfb656ce

Subscribe to this mod's changes

update-changelog is a skill published in the GitHub repository starcat-app/Starcat (159 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 3,354 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.