Optimize Runner Usage
- 2 repo stars
- Updated July 24, 2026
- cboone/agent-harness-plugins
Cut CI cost and runtime by adding paths-ignore, concurrency groups, and timeout-minutes to existing GitHub Actions workflows.
About
Optimize-runner-usage edits existing GitHub Actions workflows to reduce wasted CI minutes. It adds paths-ignore filters, concurrency groups that cancel superseded runs, and timeout-minutes caps so jobs don't hang or run on irrelevant changes. The result is faster, cheaper pipeline operation without changing what the workflows test.
- Adds paths-ignore filters
- Concurrency groups to cancel stale runs
- timeout-minutes guards
- Reduces GitHub Actions cost
Optimize Runner Usage by the numbers
- Data as of Jul 25, 2026 (Skillselion catalog sync)
/plugin marketplace add cboone/agent-harness-plugins/plugin install optimize-runner-usage@agent-harness-pluginsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | July 24, 2026 |
| Repository | cboone/agent-harness-plugins ↗ |
What it does
Cut CI cost and runtime by adding paths-ignore, concurrency groups, and timeout-minutes to existing GitHub Actions workflows.
README.md
Optimize Runner Usage
Add paths-ignore, concurrency groups, and timeout-minutes to existing GitHub Actions workflows.
Type: Command
Trigger: /optimize-runner-usage
Installation
See the marketplace install instructions.
What It Does
Scans all workflow files in .github/workflows/, classifies each one by its trigger pattern (CI, Release, Secret scanning, etc.), and adds missing optimizations:
- paths-ignore: Skip CI runs for documentation-only changes (root-level
*.md,docs/**, LICENSE, agent config files) - Concurrency groups: Cancel in-progress runs when new commits are pushed to the same branch
- timeout-minutes: Prevent runaway jobs from consuming unlimited minutes
Each optimization is applied only where appropriate. For example, paths-ignore is added to CI workflows but not to release or secret scanning workflows. Release workflows use cancel-in-progress: false to avoid aborting deployments.
Usage
/optimize-runner-usage
Examples
- "optimize runner usage": scans workflows and applies all three optimizations
- "add concurrency groups to my workflows": same behavior (all three are checked)
- "reduce CI costs": same behavior
See Also
- Set-Up CI: create CI workflows from scratch (includes these optimizations by default)
- Set-Up Secret Scanning: add secret scanning workflows
- All plugins
Related skills
Azure DeploySafely execute production deployments of already-prepared applications to Microsoft Azure.485k1.3kAzure ValidateRun deep pre-deployment checks on Azure configuration, infrastructure definitions, RBAC roles, and managed identities before pushing to production.485k1.3k
Github Actions DocsGet precise, docs-grounded answers about GitHub Actions workflows, syntax, security, and migration instead of relying on stale knowledge.275k72
Setup Pre CommitAutomatically run Prettier, type checking, and tests on every commit via Husky and lint-staged.170k199k
Deploy To VercelSafely turn any local project into a live Vercel preview with one instruction.99.3k29.7kVercel Cli With TokensDeploy projects to Vercel from agents and scripts using token authentication instead of interactive browser login.74.6k29.7k