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 jtprogru/bear-skills --skill git-release-taggit clone --depth 1 https://github.com/jtprogru/bear-skillsWrote 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/jtprogru/bear-skills/git-release-tag)<a href="https://agentmods.dev/skills/jtprogru/bear-skills/git-release-tag"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/git-release-tag/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/jtprogru/bear-skills/git-release-tag"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/git-release-tag.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.00159 | $0.01184 |
| Opus 5.5 | $0.00064 | $0.00474 |
| Sonnet 5.5 | $0.00032 | $0.00237 |
| Haiku 4.5 | $0.00016 | $0.00118 |
Grade A, and why
git-release-tag 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-release-tag — Релизный semver-тег с changelog
Цель: одной операцией провести релиз — определить версию, собрать changelog, поставить тег, при желании запушить.
Перед началом прочитай ~/.claude/rules/git-conventions.md — разделы про Semver и теги.
Шаг 1. Определи контекст репозитория
- монорепо с несколькими SDK или одиночный пакет?
- одиночный →
v<X>.<Y>.<Z>, работаешь дальше по этому скиллу - монорепо → теги вида
<sdk>/v<X>.<Y>.<Z>(например,sdk-go/v0.3.1)
- одиночный →
- если монорепо и пакет для релиза ещё не выбран — это работа
git-monorepo-release: он определит состав релиза и вызовет этот скилл на каждый тег. Если тебя вызвали уже с конкретным пакетом — продолжай, тег будет<sdk>/v<X>.<Y>.<Z>
Найди последний тег:
git tag --list 'v*' --sort=-v:refname | head -5 # одиночный
git tag --list 'sdk-go/v*' --sort=-v:refname | head -5 # пер-SDK
Если тегов нет — стартуй с v0.1.0 (или <sdk>/v0.1.0).
Шаг 2. Собери коммиты с прошлого тега
git log <last-tag>..HEAD --oneline
git log <last-tag>..HEAD --pretty=format:'%h %s%n%b%n'
В монорепо отфильтруй коммиты, затрагивающие нужный SDK:
git log <last-tag>..HEAD -- sdk-go/
Шаг 3. Определи bump
Проанализируй коммиты:
| есть в коммитах | bump |
|---|---|
feat!: или BREAKING CHANGE: в теле |
major |
feat: без breaking |
minor |
только fix:, perf:, refactor:, docs:, chore: |
patch |
| ничего значимого (только chore без изменений в коде) | спросить пользователя |
Если коммиты не по конвенции — покажи их пользователю и спроси, какой bump.
Шаг 4. Сформируй changelog
Группируй коммиты по type. Формат:
## v0.4.0 — 2026-05-23
### Breaking changes
- <commit subject> (`<sha>`)
### Features
- feat(scope): <subject> (`<sha>`)
### Fixes
- fix(scope): <subject> (`<sha>`)
### Other
- refactor / docs / chore — кратко
<полная дельта: git log link>
Шаг 5. Покажи и подтверди
Покажи:
- предлагаемую версию (
v0.4.0) - changelog
- команды, которые будут выполнены
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 127 lines · 159 tokens per session scan A 7066bcec1ef1
git-release-tag is a skill published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 8d ago), licensed MIT. It adds 159 tokens to every session and 1,184 once invoked, about $0.0006 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
otto-drive-pr
PR mergeability, CI, and live preview.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.
ship
Finish a branch: infer which review passes the change warrants, run them, open the PR, babysit CI to green, triage bot comments, and refresh the body from a clean context.