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 umputun/cc-thingz --skill last-taggit clone --depth 1 https://github.com/umputun/cc-thingzWrote 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/umputun/cc-thingz/last-tag)<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.
<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>- 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.00738 |
| Opus 5 | $0.00025 | $0.00369 |
| Sonnet 5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
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.
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.
- 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.
- 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
-
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.
-
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"
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.
- 10d ago First seen · 99 lines · 50 tokens per session scan A 675e408c4a02
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.
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.
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.
cpv-publish-to-marketplace
Use when publishing a plugin to a GitHub-hosted marketplace. Used dynamically via cpv-the-skills-menu (TRDD-478d9687).
ship
Ship a build — pre-flight checks, deploy, document, verify, monitor. Use when deploying code, publishing packages, or releasing.
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.
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…