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.
git clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/commands/davistroy/claude-marketplace/bump-version.eval)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/bump-version.eval"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/bump-version.eval/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/commands/davistroy/claude-marketplace/bump-version.eval"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/bump-version.eval.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.00000 | $0.00612 |
| Opus 5 | $0.00000 | $0.00306 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
bump-version.eval 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eval: /bump-version
Purpose
Increments the version number in a plugin's plugin.json and marketplace.json files and adds a CHANGELOG placeholder entry. Good behavior: updates both files atomically with the correct semantic version bump and does not touch other files.
Fixtures
None — this command operates on the actual marketplace repository files. Run these evals in a git branch.
Setup
All scenarios assume the current directory is the marketplace repo root and the working directory is on a feature branch (not main).
Test Scenarios
S1: Patch bump — personal-plugin
Invocation: /bump-version personal-plugin patch
Setup: Note the current version in plugins/personal-plugin/.claude-plugin/plugin.json.
Must:
- Updates
versioninplugins/personal-plugin/.claude-plugin/plugin.jsonwith patch increment (e.g., 2.3.1 → 2.3.2) - Updates matching version entry in
.claude-plugin/marketplace.json - Both files show the same new version
- Adds a CHANGELOG placeholder entry (e.g.,
## [2.3.2] - YYYY-MM-DDor## Unreleased)
Should:
- Reports the old and new version to the user
- Identifies both files that were updated
Must NOT:
- Change any other files (commands, skills, README, etc.)
- Skip updating marketplace.json
S2: Minor bump — bpmn-plugin
Invocation: /bump-version bpmn-plugin minor
Must:
- Minor version increments, patch resets to 0 (e.g., 1.4.2 → 1.5.0)
- Both plugin.json and marketplace.json updated
S3: Major bump
Invocation: /bump-version personal-plugin major
Must:
- Major version increments, minor and patch reset to 0 (e.g., 2.3.1 → 3.0.0)
S4: Error — unknown plugin name
Invocation: /bump-version nonexistent-plugin patch
Must:
- Error message listing valid plugin names
- No files modified
S5: Error — invalid bump type
Invocation: /bump-version personal-plugin hotfix
Must:
- Error message showing valid bump types: major, minor, patch
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 · 90 lines · 0 tokens per session scan A 97e138f5eed9
bump-version.eval is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 612 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.