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/psd401/psd-claude-plugins/bump-versionnpx skills add psd401/psd-claude-plugins --skill bump-versiongit clone --depth 1 https://github.com/psd401/psd-claude-pluginsWrote 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/psd401/psd-claude-plugins/bump-version)<a href="https://agentmods.dev/skills/psd401/psd-claude-plugins/bump-version"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/bump-version.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.01923 |
| Opus 5 | $0.00015 | $0.00962 |
| Sonnet 5 | $0.00006 | $0.00385 |
| Haiku 4.5 | $0.00003 | $0.00192 |
Grade A, and why
bump-version 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 4d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Version Command
You automate the version bump ritual for the PSD Plugin Marketplace. There are three independent version tracks — never conflate them.
Bump type: $ARGUMENTS
Version Track Reference
| Track | Files | When to bump |
|---|---|---|
| Marketplace | .claude-plugin/marketplace.json → metadata.version; CLAUDE.md → **Version**; root README.md |
Every release |
| psd-coding-system | plugins/psd-coding-system/.claude-plugin/plugin.json; marketplace.json → plugins[name=psd-coding-system].version; plugins/psd-coding-system/README.md |
Only when coding system skills/agents changed |
| psd-productivity | plugins/psd-productivity/.claude-plugin/plugin.json; marketplace.json → plugins[name=psd-productivity].version; plugins/psd-productivity/README.md |
Only when productivity skills/agents changed |
Phase 1: Determine Bump Type
BUMP_TYPE="$ARGUMENTS"
case "$BUMP_TYPE" in
patch|minor|major) echo "Bump type: $BUMP_TYPE" ;;
*)
echo "Invalid or missing bump type"
;;
esac
If the argument is empty or invalid, use AskUserQuestion to ask which bump type they want.
Phase 2: Determine Which Plugins Changed
Use AskUserQuestion to ask:
- Did psd-coding-system skills or agents change in this release?
- Did psd-productivity skills or agents change in this release?
The marketplace version always bumps. Plugin versions only bump for their own changes.
Phase 3: Read Current Versions
# Marketplace version (always bumps)
MARKETPLACE_VERSION=$(jq -r '.metadata.version' .claude-plugin/marketplace.json)
echo "Marketplace current: $MARKETPLACE_VERSION"
# Plugin versions (only if those plugins changed)
CODING_VERSION=$(jq -r '.version' plugins/psd-coding-system/.claude-plugin/plugin.json)
PRODUCTIVITY_VERSION=$(jq -r '.version' plugins/psd-productivity/.claude-plugin/plugin.json)
echo "psd-coding-system current: $CODING_VERSION"
echo "psd-productivity current: $PRODUCTIVITY_VERSION"
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.
- 4d ago First seen · 201 lines · 29 tokens per session scan A 80c4035bca2b
bump-version is a skill published in the GitHub repository psd401/psd-claude-plugins (2 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 1,923 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-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.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.