A report on the health of continuous integration (CI), the system that automatically builds and tests code. It uses Jenkins and other CI data to review runs, controllers, plugins, and security findings.

Use it to review one component or an entire organization, calculate pass rates, find common failure patterns, check controller health, and summarize open security findings.

It brings scattered build results and system checks into one view, making repeated failures, unhealthy CI servers, and security issues easier to spot.

ci-health — Skill for Claude Code by cloudbees-oss/devops-agent-kit

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 cloudbees-oss/devops-agent-kit --skill ci-health

Clone the repo

git clone --depth 1 https://github.com/cloudbees-oss/devops-agent-kit

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/ci-health/github.svg)](https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/ci-health)

Your own site

<a href="https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/ci-health"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/ci-health/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/cloudbees-oss/devops-agent-kit/ci-health"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/ci-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 503 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.00027	$0.00503
Opus 5.5	$0.00011	$0.00201
Sonnet 5.5	$0.00005	$0.00101
Haiku 4.5	$0.00003	$0.00050

Measured 1mo ago against content hash 92dea1f11d34, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ci-health 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 1mo 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/ci-health/SKILL.md · 51 lines

What it actually says

CI Health Report: $ARGUMENTS

controllers_list — find all CI controllers (Jenkins instances)
For each controller, pull analytics: a. controllers_data_get(ci2) — System Information (version, plugins, nodes, executors) b. controllers_data_get(ci3) — System Health (disk, threads, plugins) c. controllers_data_get(ci4) — Runs Overview (active, queued, wait times) NOTE: ci5, ci6, ci7 may return empty data. If they do, skip gracefully. d. report_drilldown_get(pluginsInfo) — plugin health details
If specific component: a. components_search — find the component b. runs_list(limit=20) — pull recent run history c. Calculate pass rate from run statuses d. security_issues_all_get — security posture
If 'org': a. components_list — all components b. Per component: runs_list(limit=10) — recent runs c. security_issues_all_get — org-wide security
Calculate and report:
- Pass rate: Per CI tool, per component. Break out GitHub Actions vs. CloudBees Workflows vs. Jenkins.
- Failure patterns: Common failure steps/categories across runs
- Controller health: System health score, plugin status, version
- Security posture: Open findings count and severity
- Queue time: From ci4 — how long runs wait before starting
Provide a "CI Health Score" (0-100) based on:
- Pass rate (weight: 35%)
- Controller health (weight: 20%)
- Security posture (weight: 25%)
- Queue efficiency (weight: 20%)
List top 3 actionable recommendations
Offer next actions:
- "/triage [component]" for components with low pass rates
- "/security-scan" if security posture is poor
- Post health report to Slack

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.

1mo ago First seen · 51 lines · 27 tokens per session scan A 92dea1f11d34

Subscribe to this mod's changes

ci-health is a skill published in the GitHub repository cloudbees-oss/devops-agent-kit (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 503 once invoked, about $0.0001 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-08-31.

Analytics and metrics CI and CD DevOps and cloud

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

atmos-profiles

Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.

cloudposse/atmos · 35 tokens

webhook-management

Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.

hoangsonww/Claude-Code-Agent-Monitor · 56 tokens

managing-github-actions-secrets

Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.

PostHog/posthog-foss · 67 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens

deployment-engineer

Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…

rmyndharis/antigravity-skills · 77 tokens