kicad-tools: Command for Claude Code

.claude/commands/repo/release.md

release is a command for Claude Code from rjwalters/kicad-tools. It costs 26 tokens per session (13,211 once invoked), scanned A, original, MIT.

A guided Git release process for checking a project, choosing a semantic version, updating release files, creating a tag, and preparing a GitHub Release. Semantic versioning uses version numbers to show the kind of change included.

In plain words
What is it for?
Use it to run release checks, update a changelog and version files, create a Git tag, and publish a GitHub Release only after confirmation.
Why use it?
It organizes release work into confirmed steps so version changes, notes, tags, and project-specific release rules are not missed.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions CLAUDE.md; positional $N argument.

This is rjwalters/kicad-tools's own configuration. It tells Claude Code how to work on kicad-tools itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kicad-tools configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is elif [ -x ./scripts/version.sh ]; then.

Reuse

Borrowing it

Nothing to install: this file belongs to rjwalters/kicad-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rjwalters/kicad-tools/main/.claude/commands/repo/release.md
Clone the repo
git clone --depth 1 https://github.com/rjwalters/kicad-tools

Made for: Claude Code.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/commands/rjwalters/kicad-tools/release.svg)](https://agentmods.dev/commands/rjwalters/kicad-tools/release)
Your own site
<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/release"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/release.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 13,211 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.13211
Opus 5 $0.00013 $0.06606
Sonnet 5 $0.00005 $0.02642
Haiku 4.5 $0.00003 $0.01321

Measured 3d ago against content hash 287258777817, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

release 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 3d 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.

.claude/commands/repo/release.md · 869 lines

How it starts

The opening of the file, as written. The whole thing — 869 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/repo:release — Cut a Release

Guide a careful, interactive release of this repository. Every phase requires confirmation before proceeding — do not rush, and never push or tag without an explicit yes. The version-bearing files and the bump tool are discovered at release time, never hardcoded, so this works in any repo.

Usage

/repo:release                  # Interactive release from the default branch

Phase 0 — Load project release policy

Before Phase 1, load the repo's release policy if it has one. This is the single supported way for a project to inject its own procedural steps (gates, extra manifest edits, post-release deploys) at named phase boundaries without forking this command — see Extension points — per-project release policy below for the full seam contract and semantics. Projects migrating off Loom's removed /loom:release skill re-home their policy here.

The policy lives in one file at the repo root: .repo/release-policy.md. Each seam is an H2 section headed ## seam: <name>. Read it, then validate the declared seam names and surface any that don't bind, so a typo'd or orphaned seam fails loudly instead of silently doing nothing:

POLICY_FILE=".repo/release-policy.md"
KNOWN_SEAMS="pre-flight pre-changelog-style pre-apply pre-push post-push pre-github-release post-summary"
AUGMENT_ONLY="post-push post-summary"   # no default action → '(replace)' is meaningless
if [ ! -f "$POLICY_FILE" ]; then
  echo "(no $POLICY_FILE — running with the built-in phases only, no behavior change)"
else
  echo "Project release policy: $POLICY_FILE"
  # Enumerate declared seams from '## seam: <name>' headers (dropping an optional
  # '(replace)' suffix) and check each against the known set.
  grep -E '^##[[:space:]]+seam:[[:space:]]*' "$POLICY_FILE" | while IFS= read -r header; do
    name="$(printf '%s' "$header" | sed -E 's/^##[[:space:]]+seam:[[:space:]]*//; s/[[:space:]]*\(replace\)[[:space:]]*$//; s/[[:space:]]+$//')"
    mode="augment"
    printf '%s' "$header" | grep -Eq '\(replace\)[[:space:]]*$' && mode="replace"
    case " $KNOWN_SEAMS " in
      *" $name "*)
        case " $AUGMENT_ONLY " in
          *" $name "*)
            if [ "$mode" = replace ]; then
              echo "  WARNING: seam '$name' is augment-only — '(replace)' is meaningless here and will be ignored"
            else
              echo "  bound: $name (augment)"
            fi ;;
          *) echo "  bound: $name ($mode)" ;;
        esac ;;
      *)
        echo "  WARNING: unknown seam '$name' — it matches no phase boundary and will NOT run. Fix the name (see the seam table) or remove the section." ;;
    esac
  done
fi

Read the full file on GitHub · 869 lines

Changes

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.

  1. 3d ago First seen · 869 lines · 26 tokens per session scan A 287258777817

Subscribe to this mod's changes

release is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 13,211 once invoked, about $0.0001 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-09-03.