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/sd0xdev/sd0x-harness/bump-versionnpx 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.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.00061 | $0.00546 |
| Opus 5 | $0.00030 | $0.00273 |
| Sonnet 5 | $0.00012 | $0.00109 |
| Haiku 4.5 | $0.00006 | $0.00055 |
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.
What it actually says
Bump Version
Update package.json, .claude-plugin/plugin.json, and .sd0x/install-state.json versions in sync.
Workflow
- Read current versions from all files
- Determine new version (from argument or auto-increment)
- Update all files to the same version
- Report result
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.
Step 4: Report
## Version Bump
| File | Field | Before | After |
|------|-------|--------|-------|
| package.json | version | x.y.z | a.b.c |
| .claude-plugin/plugin.json | version | x.y.z | a.b.c |
| .sd0x/install-state.json | plugin_version | x.y.z | a.b.c |
Prohibited
- Never set different versions across the files
- Never modify other fields in the JSON files
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 · 69 lines · 61 tokens per session scan A 4619af4ef0ca
bump-version is a skill published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 546 once invoked, about $0.0003 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-30.
Other skills, from other repositories
cc10x-router
THE ONLY ENTRY POINT FOR CC10X. Activate this skill for build, debug, review, and plan requests. Use when the user asks to implement, fix, review, plan, test, refactor, or continue code work. Trigger keywords: build, implement, create, write, add, review, audit, debug, fix, error, bug, broken, plan, design, architect…
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
diff-driven-docs
Use when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation. Also use when the user says "update docs", "sync docs", "document this", or asks whether documentation is up to date.
exploration
Two-mode exploration skill: (1) design dialogue — turn rough ideas into validated designs through collaborative interview before planning; (2) spike — throwaway code answering ONE design question, deleted or absorbed, never shipped. Router invokes mode via dispatch context.
memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.
plan-review-gate
Use after saving a non-trivial plan or decision RFC when a fail-closed feasibility, completeness, and alignment review must block execution.