What is repo-host-optimize?

A host-maintenance audit for a Mac or Linux machine used for large agent and software builds. It finds system settings and background processes that can interfere with build work, then applies safe fixes and asks before consequential ones.

Use it to inspect and prepare a build machine before heavy or concurrent builds, including checking build-directory clutter and system-level interference.

A machine can become slow or unusable when security scanning, backup software, and leftover build files compete with several builds. Checking the host addresses problems that repository cleanup cannot see.

repo-host-optimize — Skill for Claude Code and Codex by rjwalters

Install

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.

Any agent

npx skills add rjwalters/kicad-tools --skill repo-host-optimize

Clone the repo

git clone --depth 1 https://github.com/rjwalters/kicad-tools

Made for: Claude Code, Codex.

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/skills/rjwalters/kicad-tools/repo-host-optimize/github.svg)](https://agentmods.dev/skills/rjwalters/kicad-tools/repo-host-optimize)

Your own site

<a href="https://agentmods.dev/skills/rjwalters/kicad-tools/repo-host-optimize"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/repo-host-optimize/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/rjwalters/kicad-tools/repo-host-optimize"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/repo-host-optimize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,673 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 2 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.00035	$0.05673
Opus 5.5	$0.00014	$0.02269
Sonnet 5.5	$0.00007	$0.01135
Haiku 4.5	$0.00003	$0.00567

Measured 8d ago against content hash 39734499b529, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

repo-host-optimize scanned grade B with 2 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 8d 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 rootlowPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

— build-tree bloat, Loom concurrency vs core count, sudo posture, cache infra,

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Recursive force deletemediumDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

`.loom/worktrees/` whose worktree git no longer lists, `rm -rf` it (these are

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

.agents/skills/repo-host-optimize/SKILL.md · 466 lines

How it starts

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

Codex form of the /repo:host-optimize command. Other commands appear as $repo-<verb> skills. Helper scripts and .claude/ paths below are relative to the repository root and exist when the Claude Code surface is installed alongside this one.

$repo-host-optimize — Prepare a Build Host

Audit the host a machine presents to heavy Loom/agent build workloads, then apply the safe fixes and gate the consequential ones. This is host preparation, not repo hygiene: nothing here is discoverable from inside a repo, and none of it is fixed by [[tidy]] or [[audit]]. It exists because a Mac Studio running six concurrent release-build worktrees melted down — load average 118, VNC unusable, a multi-hour remediation — and every root cause was host configuration: syspolicyd burning 14+ CPU-hours a day re-scanning target/ trees on every Gatekeeper cache miss, a backup agent churning build dirs at 98% CPU, no passwordless sudo, an empty Developer Tools exemption list, and ~10 GB of dead worktree target/ dirs the scanner kept re-walking.

Follows the pack's inventory → categorize by consequence → report → apply shape (the same shape as [[tidy]] and [[branches]]). Audit checks are always report-only and safe. Fixes are split into three consequence tiers: safe / default-on, confirm-first, and documented-but-manual (printed only, never executed).

macOS-first, Linux-aware. The Gatekeeper / SIP / Spotlight / Time Machine material is macOS-only and is gated behind a uname check. The portable subset — build-tree bloat, Loom concurrency vs core count, sudo posture, cache infra, remote access — still runs and reports on Linux.

Usage

$repo-host-optimize            # Audit, apply safe fixes, report; confirm-first items prompt
$repo-host-optimize --ask      # Review every finding and confirm before applying anything
$repo-host-optimize --audit    # Audit and report only — apply nothing (like $repo-audit)

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

8d ago First seen · 466 lines · 35 tokens per session scan B 39734499b529

Subscribe to this mod's changes

repo-host-optimize is a skill published in the GitHub repository rjwalters/kicad-tools (73 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 5,673 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-01.

DevOps and cloud

repo-host-optimize next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
repo-host-optimizerjwalters/kicad-tools	Skill	73	yesterday	MIT	B	35	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	2d ago	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	today	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	315k	5d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code

repo-host-optimize