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 urmzd/dotfiles --skill release-auditgit clone --depth 1 https://github.com/urmzd/dotfilesWrote 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/urmzd/dotfiles/release-audit)<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.
<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>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.00126 | $0.00721 |
| Opus 5.5 | $0.00050 | $0.00288 |
| Sonnet 5.5 | $0.00025 | $0.00144 |
| Haiku 4.5 | $0.00013 | $0.00072 |
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.
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.yamlexists 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,v2that point to the same commit as a full semver tag
- All tags:
-
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
ghisn't authenticated, fall back to git-only checks (tags, sr.yaml). - For multi-repo scans, run checks in parallel where possible.
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 · 59 lines · 126 tokens per session scan A d197e5b47466
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.
Other skills, from other repositories
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.
smart-commit
Analyze staged changes and split them into multiple logical commits following Conventional Commits.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.
pr-review
Intelligent PR code review with dynamic agent allocation based on change types. Analyzes PR changes and generates targeted review tasks.
analyze-pr
Analyze a GitHub/GitLab Pull Request by fetching its diff, reading its web description, and generating a comprehensive document. Use when the user provides a PR link and wants to understand what changes the PR introduces, or asks to review/analyze/summarize a pull request.
gen-commit-msg
Generate intelligent commit messages based on staged changes following Conventional Commits format.