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/remote.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/remote)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/remote"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/remote.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.00024 | $0.10647 |
| Opus 5 | $0.00012 | $0.05324 |
| Sonnet 5 | $0.00005 | $0.02129 |
| Haiku 4.5 | $0.00002 | $0.01065 |
Grade F, and why
remote scanned grade F with 4 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
passwordless-sudo drop-in is installed. Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
REPO_REMOTE_SSH_KEY=~/.ssh/id_ed25519 # key used for the SSH session (fine to share) Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
path, offer to install it (`curl -fsSL https://claude.ai/install.sh | bash`). Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
path, offer to install it (`curl -fsSL https://claude.ai/install.sh | bash`). How it starts
The opening of the file, as written. The whole thing — 756 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/repo:remote — Remote Dev Session
Stand up (or reuse) a cloud VM with this repository cloned and synced, then
open a live SSH session in a new terminal window — landing in the repo, ready
to run claude and continue the work on the remote host.
Configuration is read from two layers (see below): shared cloud credentials
from ~/.config/repo/remote.env (reused across every repo), with the
target repo's .env layered on top for per-repo machine settings — and
free to override any shared value. The provisioning credentials are used
locally to drive the cloud CLI; they are never copied to the VM.
Usage
/repo:remote # Read .env, bring up / reuse the host, open SSH
/repo:remote --configure # Guided setup: shared creds (~/.config/repo/remote.env) + repo .env (machine)
/repo:remote gcp # Override REPO_REMOTE_PROVIDER for this run
/repo:remote aws
/repo:remote --status # List instances created by this command
/repo:remote --down # Stop instances created by this command
/repo:remote --down --delete # Terminate/delete them
First time in a repo? Run /repo:remote --configure to build the .env below,
then /repo:remote to launch.
The provisioning contract below is implemented once, as an executable
script — scripts/repo/repo-remote.sh, installed to
.claude/skills/repo/scripts/repo-remote.sh. The interactive flow here is a
thin wrapper: it runs the wizard/cost-confirmation UX, and once you say yes it
calls that script rather than re-issuing aws/gcloud calls from prose. The
same script is the headless entry point a non-interactive caller (e.g.
loom's fleet add-worker) invokes directly:
repo-remote up [aws|gcp] # DRY RUN: print the resolved plan + estimated cost as JSON, create NOTHING
repo-remote up --yes [--json] # provision (or reuse) with no prompts; requires pre-supplied cost-relevant config
repo-remote up --yes --force # additionally override the fleet-marker guard (see below)
repo-remote status [--json] # list instances tagged repo-remote=<name>
repo-remote down [--yes] [--delete] # dry-run listing without --yes; stop (or --delete to terminate) with --yes
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 · 756 lines · 24 tokens per session scan F 4654feee6c99
remote is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 10,647 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it F with 4 findings (asks for root, reaches for credential files, downloads and executes remote code). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.