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 ivan-magda/claude-superpowers --skill releasing-plugin-versionsgit clone --depth 1 https://github.com/ivan-magda/claude-superpowersWrote 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/ivan-magda/claude-superpowers/releasing-plugin-versions)<a href="https://agentmods.dev/skills/ivan-magda/claude-superpowers/releasing-plugin-versions"><img src="https://agentmods.dev/badge/skills/ivan-magda/claude-superpowers/releasing-plugin-versions/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/ivan-magda/claude-superpowers/releasing-plugin-versions"><img src="https://agentmods.dev/badge/skills/ivan-magda/claude-superpowers/releasing-plugin-versions.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.00030 | $0.00559 |
| Opus 5 | $0.00015 | $0.00280 |
| Sonnet 5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
releasing-plugin-versions 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 9d 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
Releasing Plugin Versions
Critical Distinction
metadata.version ≠ plugin version. These are DIFFERENT things:
| Field | What It Tracks | When to Update |
|---|---|---|
plugins[].version |
Individual plugin version | Every plugin release |
metadata.version |
Marketplace catalog structure | Adding/removing plugins ONLY |
Common mistake: Thinking metadata.version should "stay in sync" with plugin versions. It should NOT.
Plugin Version Locations (Update ALL 4)
When releasing a plugin (e.g., swift 1.2.0 → 1.3.0):
plugins/swift/.claude-plugin/plugin.json→"version": "1.3.0".claude-plugin/marketplace.json→plugins[].version: "1.3.0"plugins/swift/README.md→ Version section:1.3.0README.md(root) → Available Plugins table:1.3.0
Release Commands
# 1. Stage changes
git add -A
# 2. Commit
git commit -m "Release swift v1.3.0
- Description of changes"
# 3. Tag (format: v1.3.0, NOT swift-v1.3.0)
git tag v1.3.0
# 4. Push
git push && git push origin v1.3.0
# 5. GitHub release
gh release create v1.3.0 --title "v1.3.0" --notes "## Changes
- Change 1
- Change 2
**Full Changelog**: https://github.com/OWNER/REPO/compare/v1.2.0...v1.3.0"
Tag Format
Use v1.3.0, NOT swift-v1.3.0. Check existing tags:
git tag --sort=-v:refname | head -5
When NOT to Update metadata.version
- Releasing a new plugin version ❌
- Fixing plugin bugs ❌
- Adding features to existing plugins ❌
- Updating plugin documentation ❌
When TO Update metadata.version
- Adding a NEW plugin to the catalog ✓
- Removing a plugin from the catalog ✓
- Changing marketplace owner/name ✓
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.
- 9d ago First seen · 74 lines · 30 tokens per session scan A 631ecb6b3a59
releasing-plugin-versions is a skill published in the GitHub repository ivan-magda/claude-superpowers (6 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 559 once invoked, about $0.0002 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
memstack-development-changelog-generator
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
changelog-generator
Generate CHANGELOG.md from git history grouped by Conventional Commit types. Triggers on "generate changelog", "write changelog", "release notes".
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…
aiwg-pr
AIWG-specific pull request delivery workflow for AIWG product/workspace changes; not the generic repository PR process.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
ijfw-ship
Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…