Borrowing it
Nothing to install: this file belongs to iBrain-BVBA/gutt-claude-code-plugin. 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/iBrain-BVBA/gutt-claude-code-plugin/main/.claude/skills/plugin-release/SKILL.mdgit clone --depth 1 https://github.com/iBrain-BVBA/gutt-claude-code-pluginWrote 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/ibrain-bvba/gutt-claude-code-plugin/plugin-release)<a href="https://agentmods.dev/skills/ibrain-bvba/gutt-claude-code-plugin/plugin-release"><img src="https://agentmods.dev/badge/skills/ibrain-bvba/gutt-claude-code-plugin/plugin-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/ibrain-bvba/gutt-claude-code-plugin/plugin-release"><img src="https://agentmods.dev/badge/skills/ibrain-bvba/gutt-claude-code-plugin/plugin-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.00083 | $0.02363 |
| Opus 5.5 | $0.00033 | $0.00945 |
| Sonnet 5.5 | $0.00017 | $0.00473 |
| Haiku 4.5 | $0.00008 | $0.00236 |
Grade A, and why
plugin-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 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Release
Announce: "Starting plugin release process..."
When to Use
After merging feature/fix PRs to main, when it's time to cut a new release. This skill handles version bumping, tagging, and release creation.
Pre-Release Checklist
Before starting, verify:
- All PRs merged — no open PRs targeting main that should be included
- Tests pass — run
node tests/cursor-host.test.cjsand any other test suites - No broken hooks — quick smoke test:
node tests/test-all-hooks.cjsshould pass - Changelog reviewed — know what's in this release (check merged PRs since last tag)
# Find what changed since last release
git log v<last_version>..HEAD --oneline
Step 1: Determine Version Number
Use semantic versioning (semver):
| Change Type | Bump | Example |
|---|---|---|
| Bug fix, typo, small tweak | PATCH | 1.2.6 → 1.2.7 |
| New feature, new skill, new hook | MINOR | 1.2.6 → 1.3.0 |
| Breaking change, restructure | MAJOR | 1.2.6 → 2.0.0 |
Ask the user if the version isn't obvious from the changes. When in doubt, MINOR for features, PATCH for fixes.
Step 2: Bump Version
Each plugin's .claude-plugin/plugin.json "version" is the single source of truth for that plugin — marketplace.json deliberately carries no version fields (GP-852), and the update mechanism reads plugin.json's version as its cache key. The root package.json version tracks the root plugin, gutt-core (whose name is gutt-pro, same as package.json).
Files to update:
package.json— top-level"version"(root/repo version)gutt-core/.claude-plugin/plugin.json— top-level"version"; must equalpackage.json- Any other plugin you changed (e.g.
gutt-mentor/.claude-plugin/plugin.json) — bump its own"version"; it is versioned independently and does not trackpackage.json
Do NOT add a "version" to .claude-plugin/marketplace.json or any of its entries — plugin.json is the source of truth, and npm run check:version (Step 2b) fails if a stray version appears there.
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 · 229 lines · 83 tokens per session scan A bfcf552fa210
plugin-release is a skill published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 2,363 once invoked, about $0.0003 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.