ci-flake-quarantine

ci-flake-quarantine is a skill for Claude Code from ivegamsft/basecoat. It costs 62 tokens per session (423 once invoked), scanned A, original, MIT.

A temporary process for isolating a flaky CI test, meaning a test that passes and fails unpredictably without a code change. It records evidence, an owner, and an expiry condition while keeping the failure visible.

In plain words
What is it for?
Use it to confirm flakiness, define a quarantine window, assign follow-up ownership, record removal conditions, and rerun unaffected tests.
Why use it?
It reduces disruption from unreliable tests without permanently hiding failures or disabling them without investigation. The failing test remains tracked for root-cause work.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to confirm flakiness, define a quarantine window, assign follow-up ownership, record removal conditions, and rerun unaffected tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ivegamsft/basecoat/ci-flake-quarantine
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 ivegamsft/basecoat --skill ci-flake-quarantine
Clone the repo
git clone --depth 1 https://github.com/ivegamsft/basecoat

Made for: Claude Code.

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-flake-quarantine

README.md
[![agentmods](https://agentmods.dev/badge/skills/ivegamsft/basecoat/ci-flake-quarantine/github.svg)](https://agentmods.dev/skills/ivegamsft/basecoat/ci-flake-quarantine)
Your own site
<a href="https://agentmods.dev/skills/ivegamsft/basecoat/ci-flake-quarantine"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/ci-flake-quarantine/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.

agentmods 80×15 button for ci-flake-quarantine

Your own site · 80×15
<a href="https://agentmods.dev/skills/ivegamsft/basecoat/ci-flake-quarantine"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/ci-flake-quarantine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 423 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00423
Opus 5 $0.00031 $0.00211
Sonnet 5 $0.00012 $0.00085
Haiku 4.5 $0.00006 $0.00042

Measured 5d ago against content hash ceb83fb3d92b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

ci-flake-quarantine 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 5d 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.

skills/ci-flake-quarantine/SKILL.md · 63 lines

What it actually says

CI Flake Quarantine Skill

Use this skill when a test is flaky enough to temporarily isolate, but not enough to hide the underlying defect. It pairs with self-healing-ci for remediation and with issue-triage for tracking ownership.

Inputs

  • Flaky test name or job identifier
  • Failure history and retry evidence
  • Target quarantine duration or expiry policy
  • Owner or team responsible for follow-up

Workflow

  1. Confirm the failure pattern is non-deterministic.
  2. Check whether automated remediation has already been attempted.
  3. Quarantine only with a clear expiry date and owner.
  4. Record the quarantine scope and the condition that removes it.
  5. Re-run the unaffected test slice and report the reduced blast radius.

Output

## Flake Quarantine Plan

- Test: <name>
- Evidence: <summary>
- Quarantine expires: <date>
- Owner: <team>

### Follow-up
1. Investigate root cause
2. Remove quarantine after green verification

Guardrails

  • Never quarantine a test without repeat evidence.
  • Never make quarantine permanent by default.
  • Keep the failing signal visible through issue tracking.
  • Prefer remediation over quarantine when the root cause is already known.
  • agents/basecoat-60-workflow-self-healing-ci.agent.md
  • agents/basecoat-10-core-issue-triage.agent.md
  • skills/build-failure-triage/SKILL.md
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. 5d ago First seen · 63 lines · 62 tokens per session scan A ceb83fb3d92b

Subscribe to this mod's changes

ci-flake-quarantine is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 423 once invoked, about $0.0003 per session on Opus 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-09-03.

Related

Other skills, from other repositories

migrate-vstest-to-mtp

Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…

dotnet/skills · 191 tokens

ci

Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…

onsi/ginkgo · 132 tokens

playwright-ci

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

zebbern/claude-code-guide · 48 tokens

ci-maintenance-workflow

CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…

UKGovernmentBEIS/inspect_evals · 120 tokens

test-setup

Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.

Donchitos/Claude-Code-Game-Studios · 49 tokens

terraform-skill

Terraform infrastructure as code best practices.

Agent-Threat-Rule/agent-threat-rules · 10 tokens