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 commands/stellarshenson/claude-code-plugins/increment-plugin-versiongit clone --depth 1 https://github.com/stellarshenson/claude-code-pluginsWhat 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.00000 | $0.00494 |
| Opus 5 | $0.00000 | $0.00247 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
increment-plugin-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 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.
What it actually says
Increment Plugin Versions
Bump the patch version of every plugin in this marketplace. Does NOT touch pyproject.toml - the PyPI version is managed by make publish, and a release syncs the plugins to it. Use this only for a plugin-only bump outside a release; /release does its own sync.
What to update
22 version strings across 15 files, all set to the same number:
plugins/*/.claude-plugin/plugin.json- one"version"per pluginplugins/*/kimi.plugin.json- one"version"per plugin, the Kimi manifests.claude-plugin/marketplace.json-metadata.versionplus the"version"in each plugin entry
Do not hand-count. Derive the set from the tree, so a plugin added later is picked up on its own:
PREV=<current version>; NEW=<PREV with PATCH incremented>
grep -rl "\"$PREV\"" --include=*.json . | grep -v node_modules | xargs sed -i "s/\"$PREV\"/\"$NEW\"/g"
grep -rn "\"$NEW\"" --include=*.json . | grep -v node_modules | wc -l # expect 22
grep -rn "\"$PREV\"" --include=*.json . | grep -v node_modules | wc -l # expect 0
Never bump kimi-marketplace.json's top-level "version": "2" - that is the Kimi marketplace SCHEMA version, not a plugin version. Matching on $PREV rather than on every "version" key is what keeps the sweep off it.
Steps
- Read the current version from
.claude-plugin/marketplace.jsonmetadata.version - Parse as semver and increment PATCH
- Run the sweep above; confirm the two counts, 22 new and 0 stale
- Report:
Plugin versions bumped: X.Y.Z -> X.Y.(Z+1)
Rules
- All plugin versions stay in sync - one number across every file
- Only bump PATCH unless the user explicitly asks for MINOR or MAJOR
- Do NOT touch
pyproject.toml-make publishowns the library version - Do NOT commit - update the files and report
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 · 37 lines · 0 tokens per session scan A 5cfec9a7c5bd
increment-plugin-version is a command published in the GitHub repository stellarshenson/claude-code-plugins (3 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 494 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.