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.
npx agentmods add skills/cloudbees-oss/devops-agent-kit/ci-healthnpx skills add cloudbees-oss/devops-agent-kit --skill ci-healthgit clone --depth 1 https://github.com/cloudbees-oss/devops-agent-kitWhat 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 | $0.00027 | $0.00503 |
| Opus 5 | $0.00014 | $0.00251 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
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 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.
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
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.
- 2d ago First seen · 51 lines · 27 tokens per session scan A 92dea1f11d34
ci-health is a skill published in the GitHub repository cloudbees-oss/devops-agent-kit (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 503 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.