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 skills add cloudbees-oss/devops-agent-kit --skill pipeline-overviewgit clone --depth 1 https://github.com/cloudbees-oss/devops-agent-kitWrote 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.
[](https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/pipeline-overview)<a href="https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/pipeline-overview"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/pipeline-overview/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.
<a href="https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/pipeline-overview"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/pipeline-overview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00037 | $0.00512 |
| Opus 5.5 | $0.00015 | $0.00205 |
| Sonnet 5.5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
pipeline-overview 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.
What it actually says
Pipeline Overview: $ARGUMENTS
Show the user a unified view of their CI/CD pipelines across all tools.
-
If the user specified a component name, search for it using
components_search. Otherwise, list all components withcomponents_list. -
For each component, gather: a.
workflow_list— all configured workflows (CloudBees + GitHub Actions) b.runs_list(limit=3)— the 3 most recent runs per workflow c. Skip any workflows with names containing "code_scan" — these are infrastructure-managed scans, not user pipelines -
Get controller data: a.
controllers_list— find Jenkins controllers b. For each controller:controllers_data_get(ci4)— runs overview (active runs, queued, wait times) -
Get security context: a.
security_issues_all_get— open vulnerability count per component -
Get feature flag context: a.
flags_applications_list— find flag applications b. For each application:flags_list— count of active flags -
Present a unified dashboard:
Organization Pipeline Status
Component GitHub Actions CloudBees Workflow Jenkins Security Flags name #N PASS/FAIL #N PASS/FAIL status N HIGH N active For each component, show:
- Latest run status per CI tool (pass/fail/running)
- Open security findings count and max severity
- Active feature flags
- Any blockers or issues
-
Provide a summary:
- Components green vs. red
- Cross-tool patterns (e.g., "GitHub Actions healthy but CloudBees Workflows failing on all 3 components — likely a common config issue")
- Top recommendations
-
Offer next actions:
- "/triage [component]" for any failed component
- "/security-scan all" if security findings exist
- "/release-status" if all components are green
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 · 58 lines · 37 tokens per session scan A c4a2192eb3cb
pipeline-overview 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 37 tokens to every session and 512 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.
Other skills, from other repositories
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.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
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.
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/.
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.
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.…