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/rjwalters/kicad-tools/bumpgit clone --depth 1 https://github.com/rjwalters/kicad-toolsWrote 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/rjwalters/kicad-tools/bump)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/bump"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/bump.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.1 | $0.00000 | $0.05309 |
| Opus 5 | $0.00000 | $0.02655 |
| Sonnet 5 | $0.00000 | $0.01062 |
| Haiku 4.5 | $0.00000 | $0.00531 |
Grade A, and why
bump 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 6d 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 — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Bump + Tag (generic)
You are bumping the version of this repository — a generic project, not necessarily Loom itself.
When to use this skill
- The operator wants to release a new version of their project.
- This is a lightweight, no-CHANGELOG quick-bump. For a full versioned release with CHANGELOG gates, semver decision, and GitHub Release, use
/repo:releasefrom rjwalters/repo. - Works for any project shape: an npm package, a Cargo crate, a Python package, a single-script shell project, an npm+cargo monorepo, etc.
If the operator wants the full release methodology (pre-flight/CI gate, CHANGELOG completeness + version-drift gates, tag, GitHub Release), they should install repo and use /repo:release — it detects and honors scripts/version.sh as its first-priority version tool. /loom:bump is the quick-bump for when that full flow is overkill.
Do not rush. Each phase requires explicit confirmation before proceeding to the next.
Phase 1: Detect version sources
Walk the current repository root once and record which version-bearing files exist. Look for these sources in order and remember every match — multiple shapes can coexist (e.g. an npm+cargo monorepo).
Detection order
-
scripts/version.sh(top-level): if this file already exists from a prior/loom:bumprun, short-circuit the detection. Skip directly to Phase 5 ("Invoke the generated script"). The script is the source of truth on subsequent runs — the operator may have edited it. -
package.json(top-level): an npm project. Read.versionviajq -r .version. Skip this source if.name == "loom-workspace"— that's the Loom installer's own workspace-scaffolding stub (defaults/package.json, copied into any consumer repo that lacked a rootpackage.json), not a real project version source. It carries noversionfield in current installs; if an older stub with a leftoverversionfield is still present, treat it the same way — skip it and keep walking the remaining detection sources instead of reporting a false 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.
- 6d ago First seen · 428 lines · 0 tokens per session scan A f88db52e91d1
bump is a command published in the GitHub repository rjwalters/kicad-tools (55 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,309 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-30.
Other commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
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.