last-tag

last-tag is a skill for Claude Code from umputun/cc-thingz. It costs 50 tokens per session (738 once invoked), scanned A, original, MIT.

A release-change view that lists commits made after the repository’s most recent Git tag, which is a label marking a version or release.

In plain words
What is it for?
Use it to review unreleased work, prepare release notes, or answer what changed since the last release.
Why use it?
It avoids manually finding the latest release marker and sorting through Git history to see what is not yet released.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the release-tools plugin — 2 skills shipped together

Good fit Use it to review unreleased work, prepare release notes, or answer what changed since the last release.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/umputun/cc-thingz/last-tag
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 umputun/cc-thingz --skill last-tag
Clone the repo
git clone --depth 1 https://github.com/umputun/cc-thingz

Made for: Claude Code.

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

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 last-tag

README.md
[![agentmods](https://agentmods.dev/badge/skills/umputun/cc-thingz/last-tag/github.svg)](https://agentmods.dev/skills/umputun/cc-thingz/last-tag)
Your own site
<a href="https://agentmods.dev/skills/umputun/cc-thingz/last-tag"><img src="https://agentmods.dev/badge/skills/umputun/cc-thingz/last-tag/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 last-tag

Your own site · 80×15
<a href="https://agentmods.dev/skills/umputun/cc-thingz/last-tag"><img src="https://agentmods.dev/badge/skills/umputun/cc-thingz/last-tag.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 738 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. 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.00050 $0.00738
Opus 5 $0.00025 $0.00369
Sonnet 5 $0.00010 $0.00148
Haiku 4.5 $0.00005 $0.00074

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

Security

Grade A, and why

last-tag 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 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.

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/release-tools/skills/last-tag/SKILL.md · 99 lines

How it starts

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

Last Tag - Commits Since Last Release

Show commits since the last tag in a formatted table with optional details.

Activation Triggers

  • "last tag", "last-tag", "since last tag"
  • "what changed since last release"
  • "commits since last tag"
  • "what's new", "unreleased changes"

Workflow

Important: Avoid $() command substitution in Bash tool - use sequential steps.

  1. Fetch tags from remote and get the last tag:
git fetch origin --tags

Then get the last tag:

git describe --tags --abbrev=0

Store this value (e.g., v1.2.3) for use in subsequent commands.

  1. Get commits since that tag with format date|author|hash|subject (substitute TAG with actual value):
git log TAG..HEAD --format="%ad|%an|%h|%s" --date=short
  1. Check if all commits have the same author - extract unique authors from step 2 output. If only one unique author name appears in all rows, it's a single author.

  2. Format output:

If single author (count = 1):

Last tag: v1.2.3
Author: John Doe

| Date       | Commit  | Description                    |
|------------|---------|--------------------------------|
| 2025-12-20 | abc1234 | fix: resolve null pointer      |
| 2025-12-19 | def5678 | feat: add user authentication  |

If multiple authors (count > 1):

Last tag: v1.2.3

| Date       | Author   | Commit  | Description                    |
|------------|----------|---------|--------------------------------|
| 2025-12-20 | John Doe | abc1234 | fix: resolve null pointer      |
| 2025-12-19 | Jane Doe | def5678 | feat: add user authentication  |

If no tag exists:

No tags found in repository

If no commits since tag:

Last tag: v1.2.3
No commits since this tag

Interactive Details

After displaying the table, use AskUserQuestion:

question: "Show commit details?"
header: "Details"
options:
  - label: "All commits"
    description: "Show full details for each commit"
  - label: "None"
    description: "Skip details"
  - label: "Specific commit"
    description: "Enter commit hash to inspect"

Read the full file on GitHub · 99 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 · 99 lines · 50 tokens per session scan A 675e408c4a02

Subscribe to this mod's changes

last-tag is a skill published in the GitHub repository umputun/cc-thingz (470 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 738 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories

flow-next-land

Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.

gmickel/flow-next · 42 tokens

plugin-publish

A release guide for publishing Zhin.js plugins to npm, the JavaScript package registry, and to the Zhin plugin marketplace. It covers package metadata, versioning, release checks, and submission requirements.

zhinjs/zhin · 58 tokens

cpv-publish-to-marketplace

Use when publishing a plugin to a GitHub-hosted marketplace. Used dynamically via cpv-the-skills-menu (TRDD-478d9687).

Emasoft/claude-plugins-validation · 39 tokens

ship

Ship a build — pre-flight checks, deploy, document, verify, monitor. Use when deploying code, publishing packages, or releasing.

martineserios/thebrana · 29 tokens

changelog-assembly

This skill should be used when the user mentions "changelog", "release notes", "keep a changelog", "conventional commits", "commit message", "what changed", or "release summary". Provides a standardized methodology to turn raw, possibly non-conventional git history into human-readable changelogs and release notes.

sigistry/marketplace · 70 tokens

release-please-monorepo

Set up automated semantic versioning, changelogs, and per-package publishing in a pnpm/Turbo monorepo using googleapis/release-please-action v4. Use when the user asks to "add release please", "automate releases/versioning", "publish packages on push to main", "set up release-please in a monorepo", or wants…

pau-vega/Devkit-AI · 127 tokens