ci-sweeper

ci-sweeper is a skill for Claude Code, Codex from OutlineDriven/odin-claude-plugin. It costs 54 tokens per session (999 once invoked), scanned A, a copy of ci-sweeper, Apache-2.0.

A bounded workflow for investigating repeated failures in continuous integration, the automated checks that run against code changes. It reproduces or classifies each failure and may prepare one small, separately verified repair.

In plain words
What is it for?
Use it to sweep a failing CI run or check over a defined number of attempts, identify actionable causes, and verify a minimal proposed fix.
Why use it?
Repeatedly retrying CI failures can waste time or hide flaky checks. This tracks root causes, limits repair attempts, and stops when the problem is unclear or does not converge.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the odin-code-advanced plugin — 30 skills shipped together

Good fit Use it to sweep a failing CI run or check over a…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/outlinedriven/odin-claude-plugin/ci-sweeper
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 OutlineDriven/odin-claude-plugin --skill ci-sweeper
Clone the repo
git clone --depth 1 https://github.com/OutlineDriven/odin-claude-plugin

Made for: Claude Code, Codex.

Or install odin-code-advanced, the plugin that ships this one along with the rest of its 30 skills.

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.

agentmods badge for ci-sweeper

README.md
[![agentmods](https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/ci-sweeper.svg)](https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/ci-sweeper)
Your own site
<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/ci-sweeper"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/ci-sweeper.svg" alt="Measured on agentmods" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 999 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00999
Opus 5 $0.00027 $0.00500
Sonnet 5 $0.00011 $0.00200
Haiku 4.5 $0.00005 $0.00100

Measured 2d ago against content hash 5310bf48165d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

ci-sweeper 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 2d 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.

Origin

This is a copy

100% identical to ci-sweeper — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/odin-code-advanced/skills/ci-sweeper/SKILL.md · 48 lines

How it starts

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

CI sweeper

Contract

Field Bound contract
Trigger A recurring or requested sweep monitors CI failures over a bounded attempt window.
Authority Reversible local writes only: observe CI checks, propose or implement one minimal isolated repair in a worktree, and run the verifier. Never push, merge, publish, deploy, or mutate credentials.
Side effect One minimal isolated repair in a worktree plus one independent verifier run; hands off on flake, ambiguity, budget exhaustion, or circuit-breaker trip.
Done Root cause reproduced or classified non-actionable; any patch is minimal, independently verified, and returned as a proposal; retries stop at the configured cap without symptom patching.

Inputs

  • CI run identifier or failing check name to sweep.
  • Repository checkout path and the base commit the CI run used.
  • Verifier command: the test or check command that independently confirms the repair.
  • Attempt cap: maximum repair retries for this sweep.
  • Optional: flake-detection window and circuit-breaker threshold (repeated non-convergence or repeated flakes that stop the sweep).

Procedure

  1. On each tick, fetch the current set of failing CI checks for the target run and record the attempt number against the configured cap. Done when: the failing checks are fetched and the attempt number is recorded.
  2. If the attempt cap is reached, stop and hand off; do not start a new repair. Done when: the sweep stops at the cap with a handoff, or the cap is not yet reached.
  3. Pick one failing check and reproduce the failure locally in an isolated worktree created from the base commit the CI run used. Done when: the failure is reproduced locally or confirmed non-reproducible.
  4. Classify the failure: reproduce the root cause, or classify it non-actionable (flake, environment, upstream). If the failure is a flake or the cause is ambiguous, hand off and do not patch. Done when: the failure is classified as root cause or non-actionable, or handed off.
  5. If a root cause is reproducible, implement one minimal isolated repair in the worktree: the smallest change that fixes the reproduced cause and nothing else. Done when: the minimal repair is implemented in the worktree.
  6. Run the verifier in the worktree independently of the repair; confirm the failing check passes and no other check regresses. Done when: the verifier confirms the fix and no regression, or the verifier failure is recorded.
  7. If the verifier fails or regresses, do not widen the patch; increment the attempt counter and either retry within budget or hand off. Done when: the attempt counter is incremented and the retry-or-handoff decision is made.
  8. Return the verified patch as a proposal (diff or branch) with the reproduced root cause and verifier evidence. Do not push, merge, or publish. Done when: the verified patch is returned as a proposal with evidence.
  9. If the circuit breaker trips (repeated non-convergence, repeated flakes, or budget exhaustion), stop the sweep and hand off with the accumulated evidence. Done when: the sweep stops with a handoff and accumulated evidence.

Read the full file on GitHub · 48 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 2d ago First seen · 48 lines · 54 tokens per session scan A 5310bf48165d

Subscribe to this mod's changes

ci-sweeper is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 999 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ci-sweeper, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens