release-audit

release-audit is a skill for Claude Code from urmzd/dotfiles. It costs 126 tokens per session (721 once invoked), scanned A, original, Apache-2.0.

A read-only checker for GitHub releases, which are published versions of a project, along with their git tags and downloadable files. It examines one repository or all repositories in a directory for mismatches and unfinished releases.

In plain words
What is it for?
Use it before or after releasing software to compare tags, GitHub releases, assets, version pointers, and optional sr.yaml configuration without changing anything.
Why use it?
It exposes release problems such as tags without releases, missing binaries or checksums, drafts left unpublished, outdated major-version tags, and old pre-release leftovers. It also checks sr.yaml settings when that file exists.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it before or after releasing software to compare tags, GitHub releases, assets, version pointers, and optional sr.yaml configuration without changing anything.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/urmzd/dotfiles/release-audit
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 urmzd/dotfiles --skill release-audit
Clone the repo
git clone --depth 1 https://github.com/urmzd/dotfiles

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 release-audit

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/urmzd/dotfiles/release-audit"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/release-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 721 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00126 $0.00721
Opus 5.5 $0.00050 $0.00288
Sonnet 5.5 $0.00025 $0.00144
Haiku 4.5 $0.00013 $0.00072

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

Security

Grade A, and why

release-audit 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.

dot_agents/skills/release-audit/SKILL.md · 59 lines

What it actually says

Release Audit

Audit releases, tags, and assets for consistency.

Steps

  1. Determine scope: If a directory of repos is given, discover all git repos one level deep. Otherwise use the current repo.

  2. For each repo, gather:

    • All tags: git tag -l
    • All releases: gh release list --limit 50 --json tagName,name,isDraft,isPrerelease,assets
    • Detect sr.yaml: check whether sr.yaml exists at the repo root. Only if present, read it to understand expected release behavior. If absent, skip all sr-specific checks for this repo (do not report a "missing sr.yaml" issue -- not every repo uses sr).
    • Floating tags: tags like v1, v2 that point to the same commit as a full semver tag
  3. Check for issues:

    • Orphaned tags: tags with no corresponding GitHub release
    • Releases without assets: releases that should have binaries/checksums but don't
    • Draft releases: releases stuck in draft state
    • Floating tag drift: major version tags (e.g., v1) not pointing to the latest patch
    • sr.yaml issues (only when sr.yaml was detected in step 2): misconfigured plugins, version file mismatches between sr.yaml and the actual version files
    • Pre-release remnants: old pre-release versions that were never promoted
  4. Report: For each repo, show:

    ## repo-name
    - Latest release: v1.2.3 (2024-01-15)
    - Total releases: 12 | Tags: 15
    - Issues:
      - ⚠ 3 orphaned tags: v0.1.0, v0.2.0, v0.3.0
      - ⚠ Floating tag v1 behind latest (points to v1.1.0, latest is v1.2.3)
      - ✓ All releases have assets
    
  5. Summary: One-line-per-repo table at the end with issue counts.

Rules

  • Don't delete or modify tags/releases. This is read-only audit.
  • If gh isn't authenticated, fall back to git-only checks (tags, sr.yaml).
  • For multi-repo scans, run checks in parallel where possible.
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. 1mo ago First seen · 59 lines · 126 tokens per session scan A d197e5b47466

Subscribe to this mod's changes

release-audit is a skill published in the GitHub repository urmzd/dotfiles (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 126 tokens to every session and 721 once invoked, about $0.0005 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.