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 sd0xdev/sd0x-harness --skill bump-versiongit clone --depth 1 https://github.com/sd0xdev/sd0x-harnessWrote 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/sd0xdev/sd0x-harness/bump-version)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/bump-version"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/bump-version/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/sd0xdev/sd0x-harness/bump-version"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/bump-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00061 | $0.01011 |
| Opus 5.5 | $0.00024 | $0.00404 |
| Sonnet 5.5 | $0.00012 | $0.00202 |
| Haiku 4.5 | $0.00006 | $0.00101 |
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 12d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Version
Update package.json, .claude-plugin/plugin.json, and .sd0x/install-state.json versions in sync.
Workflow
- Choose the target (below) — the plugin, or the agentctl mod
- Read current versions from all files
- Determine new version (from argument or auto-increment)
- Update all files to the same version
- Report result
Step 0: Choose the Target
| Invocation | Target | Steps |
|---|---|---|
/bump-version agentctl [patch|minor|major|<version>] |
the agentctl mod only | Step 3b only — the plugin's three files are not read or changed, so no plugin release is triggered |
| anything else | the plugin | Steps 1–4; Step 3b is not run |
Never bump both in one invocation: the plugin and the mod release separately, and a stray change to
package.json triggers the plugin's release workflow. When the plugin is bumped and
node .github/scripts/agentctl-version.js check reports that the mod changed too, say so and suggest
/bump-version agentctl as a separate run.
Step 1: Read Current Versions
grep '"version"' package.json .claude-plugin/plugin.json
Also check manifest:
grep '"plugin_version"' .sd0x/install-state.json 2>/dev/null || echo "(no manifest)"
If versions are already out of sync, warn user before proceeding.
Step 2: Determine New Version
| Input | Action |
|---|---|
Explicit version (e.g., 1.9.0) |
Use as-is |
major |
Bump major: 1.8.1 → 2.0.0 |
minor |
Bump minor: 1.8.1 → 1.9.0 |
patch (default) |
Bump patch: 1.8.1 → 1.8.2 |
| No argument | Default to patch |
Step 3: Update All Files
Use Edit tool to update version fields:
package.json—"version"field.claude-plugin/plugin.json—"version"field.sd0x/install-state.json—"plugin_version"field (if file exists)
All must be set to the exact same version string.
The manifest update prevents the SessionStart drift sentinel from firing false warnings after every version bump in the plugin source repo.
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.
- 12d ago Changed · +26 lines ce0e46dce414
- 1mo ago First seen · 69 lines · 61 tokens per session scan A 4619af4ef0ca
bump-version is a skill published in the GitHub repository sd0xdev/sd0x-harness (194 stars, last pushed 11d ago), licensed MIT. It adds 61 tokens to every session and 1,011 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
update
Safe cc10x upgrade through the Claude Code plugin CLI. Lists every installed scope, refreshes the marketplace, updates each scope, and optionally carries local patches over to the new install. Use this skill when: updating cc10x, upgrading, pulling latest cc10x, syncing plugin, refreshing cache, or checking for new…
comet-archive
A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.
comet-release
A release-preparation workflow for Comet that uses the real version, branch history, and user-visible changes to prepare a changelog and release checks. A changelog is a dated record of what changed for people using the software.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
resolving-merge-conflicts
Use when a git merge or rebase reports conflicts and the operation is in progress.
release-support
A release and upgrade support tool for 1C configurations, which are the structured applications built on the 1C platform. It covers checks around delivered updates, extensions, data migrations, and compatibility.