A read-only preview of the next software release based on Git history since the latest version tag. It groups commits into features, fixes, other changes, and uncategorized messages.

It is for checking the next release version, reviewing categorized changes, and spotting commit messages that do not follow the project's format.

It shows the expected version increase and release notes before anything is tagged or published.

status — Skill for Claude Code by ondrasek/cc-plugins

Install

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.

Any agent

npx skills add ondrasek/cc-plugins --skill status

Clone the repo

git clone --depth 1 https://github.com/ondrasek/cc-plugins

Made for: Claude Code.

Or install auto-release, the plugin that ships this one along with the rest of its 2 skills, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ondrasek/cc-plugins/status/github.svg)](https://agentmods.dev/skills/ondrasek/cc-plugins/status)

Your own site

<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/status"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/status/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/status"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 847 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00055	$0.00847
Opus 5.5	$0.00022	$0.00339
Sonnet 5.5	$0.00011	$0.00169
Haiku 4.5	$0.00006	$0.00085

Measured 1mo ago against content hash 66c54f51c023, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

status 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.

plugins/auto-release/skills/status/SKILL.md · 125 lines

How it starts

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

Status

Read-only analysis of what the next release will look like.

Critical Rules

Never create tags or releases — this skill is read-only
Always show non-conventional commits — they won't be categorized properly
Use --no-merges to skip merge commits in analysis

Prerequisites Check

git rev-parse --is-inside-work-tree

Workflow

1. Find Latest Tag

LATEST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
echo "Latest tag: ${LATEST_TAG:-none}"

2. List Commits Since Tag

if [ -n "$LATEST_TAG" ]; then
  git log "${LATEST_TAG}..HEAD" --format="%h %s" --no-merges
else
  git log --format="%h %s" --no-merges
fi

3. Categorize and Analyze

Group commits by type:

Breaking Changes (any type with ! or BREAKING CHANGE footer)
Features (feat)
Fixes (fix)
Other (all other conventional types)
Non-conventional (commits that don't match the pattern)

4. Calculate Version Bump

Breaking changes → MAJOR (X+1.0.0)
Features → MINOR (x.Y+1.0)
Everything else → PATCH (x.y.Z+1)

Highest wins: MAJOR > MINOR > PATCH

5. Present Report

Release Status
==============

Latest tag: v1.2.3 (released 2024-01-15)
Commits since tag: 8

Next version: v1.3.0 (MINOR bump — new features detected)

Breaking Changes:
  (none)

Features:
  - abc1234 feat(auth): add OAuth2 login flow
  - def5678 feat(api): add bulk delete endpoint

Fixes:
  - 111aaaa fix: correct null pointer in user lookup
  - 222bbbb fix(ui): resolve dark mode toggle

Other:
  - 333cccc docs: update API reference
  - 444dddd chore(deps): update dependency versions
  - 555eeee refactor(auth): simplify token validation

Non-conventional commits (will not be categorized):
  - 666ffff Update README
  - 777gggg WIP save progress

Preview release notes:
  ## Features
  - feat(auth): add OAuth2 login flow
  - feat(api): add bulk delete endpoint

  ## Fixes
  - fix: correct null pointer in user lookup
  - fix(ui): resolve dark mode toggle

  ## Other Changes
  - docs: update API reference
  - chore(deps): update dependency versions
  - refactor(auth): simplify token validation

Read the full file on GitHub · 125 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.

1mo ago First seen · 125 lines · 55 tokens per session scan A 66c54f51c023

Subscribe to this mod's changes

status is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 847 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-31.

Git and workflow Releases

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.

paperclipai/paperclip · 42 tokens

release

Fully automate a release with version-bump and childhood.

thedotmack/claude-mem · 13 tokens

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.

phuryn/pm-skills · 57 tokens

status