What is update-tools?

A repository command that checks tool packages installed by a project tool manager against their source repositories and offers to update outdated copies.

Checking all managed tools, checking one tool, previewing updates without changes, or updating the working tree with optional commits.

It shows which installed tools are stale and separates tool updates from normal package updates such as npm, Cargo, or pip dependencies.

How rjwalters/kicad-tools configures Claude Code

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/update-tools.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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/rjwalters/kicad-tools/update-tools.svg)](https://agentmods.dev/commands/rjwalters/kicad-tools/update-tools)

Your own site

<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/update-tools"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/update-tools.svg" alt="Measured on agentmods" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 6,746 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.

Model	Per session	Once invoked
Fable 5.1	$0.00027	$0.06746
Opus 5	$0.00014	$0.03373
Sonnet 5	$0.00005	$0.01349
Haiku 4.5	$0.00003	$0.00675

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

Security

Grade A, and why

update-tools 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/update-tools.md · 489 lines

How it starts

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

/repo:update-tools — Tool Package Updates

Find every tool package installed into this repo by an Anvil/Loom-style installer, compare each against the latest version of its source, and offer to update the stale ones.

Scope is installer-managed tool packages only. Third-party dependency currency — npm/cargo/pip packages and GitHub Actions, i.e. Dependabot setup and Dependabot PR triage — is [[deps]], not this command: there is no local source clone to diff against, so it needs a different comparison model.

Usage

/repo:update-tools               # Report, then offer updates (commit + land on the default branch)
/repo:update-tools --check       # Report only, never writes
/repo:update-tools loom          # Only check/update one tool
/repo:update-tools --no-commit   # Update the working tree but leave it uncommitted for review

An update runs the tool's own installer or updater (executing code from its source repo and rewriting .claude/), so unlike the safe-fix hygiene commands this one is not auto-applied — it reports and confirms before updating. --check is the report-only form.

Once an update is confirmed, it is committed and landed on the default branch (main) by default — it does not push, and it never folds a pre-existing dirty working tree into the update commit. Pass --no-commit (alias --stage-only) to restore the old behavior of leaving the changes uncommitted for manual review. See step 5 and the Safety Rules for details.

Steps

1. Discover installed tools

Tools in this family record their install in a metadata file. Sweep for it rather than listing known paths — a fixed list structurally cannot find a family member added after this doc was last updated, which is exactly how .kct/install-metadata.json went undiscovered before (repo#165):

find . -maxdepth 4 -name "install-metadata.json" \
  -not -path "*/node_modules/*" -not -path "*/.venv/*" 2>/dev/null

-maxdepth 4 reaches every known tool root (.loom/, .anvil/, .kct/ at depth 2, and the two-levels-deeper .claude/skills/*/ at depth 4) and any future tool that follows the same shallow layout, without needing a doc edit when one is added.

Read the full file on GitHub · 489 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.

3d ago First seen · 489 lines · 27 tokens per session scan A dd4d552bd8c8

Subscribe to this mod's changes

update-tools is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 6,746 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.

Git and workflow

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 tokens

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.

OpenHands/extensions · 44 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

repo-audit

Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.

tractorjuice/arc-kit · 29 tokens

handoff

Export a Waybill Bundle by default, or import one when requested.

wardmos/waybill · 13 tokens

kicad-tools: Command for Claude Code