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 berkcangumusisik/claude-code-practices --skill tag-releasegit clone --depth 1 https://github.com/berkcangumusisik/claude-code-practicesWrote 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/berkcangumusisik/claude-code-practices/tag-release)<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/tag-release"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/tag-release/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/berkcangumusisik/claude-code-practices/tag-release"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/tag-release.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.00020 | $0.00266 |
| Opus 5 | $0.00010 | $0.00133 |
| Sonnet 5 | $0.00004 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
tag-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 6d 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
Create a Release Tag
Bump type: $1 (major | minor | patch)
- Get current version:
cat package.json | grep '"version"' | head -1
git tag --sort=-v:refname | head -5
-
Calculate new version based on semver and bump type
$1. -
Show what will happen:
- Old version → New version
- Files that will be modified
- Tag that will be created
-
If
$ARGUMENTScontains--dry-run, stop here. -
Ask for confirmation, then:
- Update version in
package.json(orpyproject.toml,Cargo.toml, etc.) - Commit:
chore: bump version to X.Y.Z - Tag:
git tag -a vX.Y.Z -m "Release vX.Y.Z"
- Update version in
-
Ask whether to push tag to remote.
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.
- 6d ago First seen · 35 lines · 20 tokens per session scan A 94c1f2061974
tag-release is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (10 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 266 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
close
Update version tracking when finishing work on a skill bundle. Use when you're done editing a skill project and need to bump version headers, recompute manifest hashes, update the changelog, flag stale files, or prepare a commit message. Triggers on: "close the session", "update versions", "save the bundle", "I'm done…
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.