fix-failing-pipelines

fix-failing-pipelines is a skill for Claude Code from a5c-ai/babysitter. It costs 60 tokens per session (970 once invoked), scanned A, original, MIT.

A workflow checker and repair routine for GitHub Actions, the service that runs automated build and test jobs. It examines the latest completed runs on the babysitter repository’s staging branch and starts a repair process for failures.

In plain words
What is it for?
Use it to inspect staging-branch workflows, identify the ones whose latest completed run failed, and launch fixes for each failure.
Why use it?
It avoids manually searching through many workflow runs to find which pipelines broke and where. It also gathers the failed job and step details needed for repair.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to inspect staging-branch workflows, identify the ones whose latest completed run failed, and launch fixes for each failure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/a5c-ai/babysitter/fix-failing-pipelines
About the project

Babysitter is a workflow engine for AI coding agents that enforces predefined steps, quality checks, human approvals, and decision records. It is used to coordinate complex, repeatable agent workflows across supported coding tools. The catalogue contains skills, agents, instructions, settings, a plugin, and an MCP integration for its workflow.

a5c-ai/babysitter · 1,788 stars · on GitHub · a5c.ai

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 a5c-ai/babysitter --skill fix-failing-pipelines
Clone the repo
git clone --depth 1 https://github.com/a5c-ai/babysitter

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 fix-failing-pipelines

README.md
[![agentmods](https://agentmods.dev/badge/skills/a5c-ai/babysitter/fix-failing-pipelines/github.svg)](https://agentmods.dev/skills/a5c-ai/babysitter/fix-failing-pipelines)
Your own site
<a href="https://agentmods.dev/skills/a5c-ai/babysitter/fix-failing-pipelines"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/fix-failing-pipelines/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 fix-failing-pipelines

Your own site · 80×15
<a href="https://agentmods.dev/skills/a5c-ai/babysitter/fix-failing-pipelines"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/fix-failing-pipelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 970 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00060 $0.00970
Opus 5 $0.00030 $0.00485
Sonnet 5 $0.00012 $0.00194
Haiku 4.5 $0.00006 $0.00097

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

Security

Grade A, and why

fix-failing-pipelines 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 12d 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.

.claude/skills/fix-failing-pipelines/SKILL.md · 87 lines

How it starts

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

Fix Failing Pipelines

Check GitHub Actions workflows on the staging branch of https://github.com/a5c-ai/babysitter/actions, identify workflows whose most recent run is failing, and dispatch /babysitter:yolo to fix each one.

Workflow

Step 1: Fetch Most Recent Run Per Workflow

Use the gh CLI to list recent workflow runs on the staging branch:

gh run list --repo a5c-ai/babysitter --branch staging --limit 50 --json databaseId,workflowName,status,conclusion,createdAt,headBranch

Group the results by workflowName. For each workflow, keep only the most recent run (by createdAt). Discard workflows where the most recent run is still in_progress -- we only care about completed runs.

Step 2: Identify Failures

From the grouped results, select only workflows where the most recent completed run has conclusion: "failure". Skip workflows whose latest run succeeded, was cancelled, or is still running.

If no workflows have a failing most-recent run, report that all staging pipelines are green and stop.

Step 3: Get Failure Details

For each failing workflow run, fetch the failed job and step details:

gh run view <run_id> --repo a5c-ai/babysitter --json jobs --jq '.jobs[] | select(.conclusion == "failure") | {name, conclusion, steps: [.steps[] | select(.conclusion == "failure") | .name]}'

Then fetch the logs to understand the actual error:

gh run view <run_id> --repo a5c-ai/babysitter --log-failed 2>&1 | tail -100

Step 4: Present Failures

Display the list of failing workflows to the user with:

  • Workflow name
  • Run ID and link
  • Failed job name(s) and failed step name(s)
  • Brief summary of the error from the logs

Step 5: Fix via Babysitter

For each failing workflow, invoke the babysitter:yolo skill with a prompt that includes the failure context:

/babysitter:yolo fix the failing "<workflow_name>" pipeline on staging. The most recent run (<run_id>) failed in job "<job_name>" at step "<step_name>". Error details: <brief_error_summary>. Investigate the failure, fix the root cause, and push a fix to the staging branch. Do not create a new branch -- commit directly to staging.

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

  1. 12d ago First seen · 87 lines · 60 tokens per session scan A e09ee9d72f84

Subscribe to this mod's changes

fix-failing-pipelines is a skill published in the GitHub repository a5c-ai/babysitter (1,788 stars, last pushed 6d ago), licensed MIT. It adds 60 tokens to every session and 970 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-08-30.