What is release-audit?

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.

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

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.

release-audit — Skill for Claude Code and Codex by urmzd: A read-only checker for GitHub releases, which are published…

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.

agentmods

npx agentmods add skills/urmzd/dotfiles/release-audit

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, Codex.

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/urmzd/dotfiles/release-audit.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.svg" alt="Measured on agentmods" 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. Scan, not verified.

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	$0.00126	$0.00721
Opus 5	$0.00063	$0.00360
Sonnet 5	$0.00025	$0.00144
Haiku 4.5	$0.00013	$0.00072

Measured 3d ago against content hash d197e5b47466, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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

Determine scope: If a directory of repos is given, discover all git repos one level deep. Otherwise use the current repo.
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
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

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

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.

3d 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 (3 stars, last pushed 21d ago), licensed Apache-2.0. It adds 126 tokens to every session and 721 once invoked, about $0.0006 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-31.

Git and workflow Releases chezmoi dotfiles neovim nvim tmux zsh

coding

Principles for writing and designing code, covering API and abstraction design, naming, comment discipline, and standards of evidence for claims about code behavior. Use whenever the task is to write or modify code, design an API or software architecture, or review code.

ryota2357/dotfiles · 53 tokens

review-code

Standalone code review for any scope — PR number, branch, file paths, or current changes. Synthesizes intent, runs 10 parallel specialized agents, and presents actionable findings with a verdict. For PR scope, optionally posts the review to GitHub with inline comments.

ooloth/dotfiles · 57 tokens

review-prs

Fetch and present a prioritized summary of all PRs awaiting the current user's review across the relevant projects and provide an interactive workflow helping the user phrase and post inline review comments and overall review decisions.

ooloth/dotfiles · 42 tokens

review-converge

Autonomously review and fix the current branch or specified scope in iterative rounds until clean, leaving all changes in the working tree. Escalates only genuine design decisions. Ends with a transparent report of every round, every fix, and anything it couldn't resolve — persisted to .outputs/.

ooloth/dotfiles · 62 tokens

review-pr-comments-converge

Fetch PR review comments, validate each against the actual code, auto-fix obvious issues, and escalate genuine design decisions. Leaves all changes in the working tree. Use when you want to action reviewer feedback autonomously.

ooloth/dotfiles · 50 tokens

write-ticket-description

Voice guide for writing issue/ticket/task/epic descriptions. Use this skill for ALL issue creation — GitHub issues, Jira tasks, Monday tasks, Linear tasks, and epics. Contains section structure, voice rules, and anti-patterns. Never write ticket descriptions without invoking this skill first.

ooloth/dotfiles · 64 tokens