What is repo-optimize-ci?

A GitHub Actions checker that examines automated build and test workflows for unnecessary work. GitHub Actions is GitHub's service for running these workflows.

It uses past run data to rank possible savings and reports recommended changes; it does not apply them unless requested.

It finds wasted runner time caused by irrelevant changes, ineffective caches, duplicate or superseded runs, and expensive default-branch jobs.

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

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

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

agentmods

npx agentmods add skills/rjwalters/kicad-tools/repo-optimize-ci

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

Your own site

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

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

When invoked 5,611 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.00051	$0.05611
Opus 5.5	$0.00020	$0.02244
Sonnet 5.5	$0.00010	$0.01122
Haiku 4.5	$0.00005	$0.00561

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

Security

Grade A, and why

repo-optimize-ci 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 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.

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.

.agents/skills/repo-optimize-ci/SKILL.md · 436 lines

How it starts

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

Codex form of the /repo:optimize-ci 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-optimize-ci — Stop CI Doing Work That Cannot Matter

Find the four ways CI routinely wastes runner minutes, prove how much each one costs from real run history, and propose the fix:

No change-relevance filtering — full suites on documentation-only PRs, heavy jobs on changes that cannot affect them. And the opposite hazard: an existing paths: filter that omits a real input (a lockfile, the workflow file itself, a local action), which lets a breaking change merge green.
Weak or missing caching — no toolchain cache at all, or a cache keyed so it never hits (github.sha in the key) or never invalidates (no lockfile hash in the key).
Superseded runs — no concurrency: / cancel-in-progress, so every push to a PR leaves the previous run burning minutes; or duplicate push + pull_request triggers running the same commit twice.
Default-branch cost — push-only workflows (deploys, main-only suites) with no ref-scoped group or an unconditional cancel-in-progress: true, and heavy suites that re-run on every merge although the PR already ran them.

Modeled on [[deps]]: a report-first audit of repo configuration that proposes changes and gates writes. The default mode and --check never write. --apply writes proposed workflow edits on a branch and opens a PR, under the same authorization convention as [[deps]] and [[release]]: apply existing authorization when it covers the concrete edits, otherwise show the diff and confirm first. Never push to the default branch.

The deterministic half — workflow parsing, trigger/paths/cache/concurrency extraction, required-check lookup, run-timing aggregation — is scripts/repo/repo-optimize-ci.py in the source checkout, installed to .claude/skills/repo/scripts/repo-optimize-ci.py. Every GitHub call it makes is a GET. This file is the judgment half: verifying what the helper inferred, choosing the right fix shape, and writing it.

Read the full file on GitHub · 436 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 · 436 lines · 51 tokens per session scan A 9f175bfaccc0

Subscribe to this mod's changes

repo-optimize-ci is a skill published in the GitHub repository rjwalters/kicad-tools (73 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 5,611 once invoked, about $0.0002 per session on Opus 5.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-11-01.

Analytics and metrics CI and CD DevOps and cloud

repo-optimize-ci next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
repo-optimize-cirjwalters/kicad-tools	Skill	73	yesterday	MIT	A	51	Claude Code, Codex
chinese-git-workflowjnMetaCode/superpowers-zh	Skill	8.5k	14d ago	MIT	A	69	Claude Code
atmos-profilescloudposse/atmos	Skill	1.4k	today	Apache-2.0	A	35	Claude Code
webhook-managementhoangsonww/Claude-Code-Agent-Monitor	Skill	1.2k	yesterday	MIT	A	56	Claude Code, Codex
deployment-engineerrmyndharis/antigravity-skills	Skill	2.0k	2d ago	MIT	A	73	Claude Code, Codex
monorepo-managementwshobson/agents	Skill	42k	yesterday	MIT	C	54	Claude Code
postman-newman-automationLambdaTest/agent-skills	Skill	391	4d ago	MIT	A	156	Claude Code, Codex