Borrowing it
Nothing to install: this file belongs to PIsberg/vibetags. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PIsberg/vibetags/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/PIsberg/vibetagsWrote 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/pisberg/vibetags/release)<a href="https://agentmods.dev/skills/pisberg/vibetags/release"><img src="https://agentmods.dev/badge/skills/pisberg/vibetags/release.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
- medium Agent Snooping · line 88 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00071 | $0.03197 |
| Opus 5 | $0.00036 | $0.01598 |
| Sonnet 5 | $0.00014 | $0.00639 |
| Haiku 4.5 | $0.00007 | $0.00320 |
Grade A, and why
release 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 7d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release VibeTags
Drives the release process documented in docs/RELEASING.md. That document is the
source of truth; this skill is the executable path through it. If the two ever
disagree, docs/RELEASING.md wins — and say so rather than silently improvising.
Step 1 — Establish the current version and ask for the next one
The single source of truth for "what version are we on" is the <revision>
property in vibetags-parent/pom.xml:
sed -n 's:.*<revision>\(.*\)</revision>.*:\1:p' vibetags-parent/pom.xml | head -n1
git tag --sort=-v:refname | head -5
Then ask the user which version to release with AskUserQuestion. Compute the
candidates from whatever the current version turns out to be — do not hardcode them:
- If the current version is a release candidate (
X.Y.Z-RCn), offer promoting it to final (X.Y.Z) and cutting the next candidate (X.Y.Z-RC<n+1>). - If the current version is final, offer the patch, minor, and major bumps, and a first
release candidate for the next minor if that fits what is in
[Unreleased].
Always include the semantic-versioning meaning in each option's description. The user can also type any version via "Other". Never guess and proceed — the version is always the user's call.
Sanity-check the answer before continuing: it must be a release version (no
-SNAPSHOT — Maven Central rejects those), and git tag -l "v<version>" must come
back empty.
Step 2 — Preflight
Refuse to continue and tell the user what is wrong if any of these fail:
git status --porcelain # must be clean
git rev-parse --abbrev-ref HEAD # note the branch
gh auth status # gh must be authenticated
Then:
git checkout main && git pull
git checkout -b release/v<version>
Step 3 — Bump the version
tools/set-version.sh does the whole bump in one pass (it reads the current
version fresh from the parent, so it is idempotent):
tools/set-version.sh <version>
That rewrites <revision> in vibetags-parent/pom.xml — which every managed pom
inherits its version from, so vibetags-annotations/pom.xml, vibetags/pom.xml,
vibetags-bom/pom.xml and load-tests/pom.xml need no edit at all — plus the
places that cannot inherit it: both build.gradle files, the copy-pasteable
snippets in the <description> blocks, and the standalone example/demo poms.
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.
- 7d ago First seen · 280 lines · 71 tokens per session scan A 1205025061f7
release is a skill published in the GitHub repository PIsberg/vibetags (15 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 3,197 once invoked, about $0.0004 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
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
research-archival
Scrape AI research URLs, archive with frontmatter, create GitHub Issues with identity verification.
monorepo-navigator
Navigate, manage, and optimize monorepos. Covers Turborepo, Nx, pnpm workspaces, and Lerna. Enables cross-package impact analysis, selective builds/tests on affected packages only, remote caching, dependency graph visualization, and structured migrations from multi-repo to monorepo. Includes Claude Code configuration…