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 agentmods add skills/ibrain-bvba/gutt-claude-code-plugin/plugin-releasenpx skills add iBrain-BVBA/gutt-claude-code-plugin --skill plugin-releasegit clone --depth 1 https://github.com/iBrain-BVBA/gutt-claude-code-pluginWhat 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 | $0.00083 | $0.02363 |
| Opus 5 | $0.00042 | $0.01182 |
| Sonnet 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 2d 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.
- 2d 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 (4 stars, last pushed 12d ago), licensed MIT. It adds 83 tokens to every session and 2,363 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-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.