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.
curl -O https://raw.githubusercontent.com/rjwalters/kicad-tools/main/.claude/commands/repo/release.mdgit 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/release)<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>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.00026 | $0.13211 |
| Opus 5 | $0.00013 | $0.06606 |
| Sonnet 5 | $0.00005 | $0.02642 |
| Haiku 4.5 | $0.00003 | $0.01321 |
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.
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
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.
- 3d ago First seen · 869 lines · 26 tokens per session scan A 287258777817
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.
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.