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/arvo-ai/aurora/cloudbees_ocnpx skills add Arvo-AI/aurora --skill cloudbees_ocgit clone --depth 1 https://github.com/Arvo-AI/auroraWrote 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/arvo-ai/aurora/cloudbees_oc)<a href="https://agentmods.dev/skills/arvo-ai/aurora/cloudbees_oc"><img src="https://agentmods.dev/badge/skills/arvo-ai/aurora/cloudbees_oc.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00597 |
| Opus 5 | $0.00011 | $0.00298 |
| Sonnet 5 | $0.00004 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
cloudbees_oc 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CloudBees Operations Center Integration
Overview
CloudBees Operations Center (CJOC) integration for enterprise-wide CI/CD visibility during Root Cause Analysis. Operations Center manages multiple Jenkins controllers and provides a unified view of all builds and deployments across the organization.
Instructions
Tool: cloudbees_rca
The same cloudbees_rca tool is used, with additional enterprise actions enabled when Operations Center is connected.
Enterprise Actions:
controller_list— List all managed Jenkins controllers and their status (online, offline, failing)cross_controller_deployments— Query recent builds across ALL managed controllers; optionalservicefilter andtime_window_hoursflag_changes— Query recent feature flag changes from CloudBees Feature Management; optionalapp_idfilter
RCA Investigation Flow
When Operations Center is connected, start broad and narrow down:
cloudbees_rca(action='controller_list')— See all managed controllers and their healthcloudbees_rca(action='cross_controller_deployments', service='SERVICE')— Find recent deployments across ALL controllerscloudbees_rca(action='flag_changes')— Check if any feature flags were toggled near the incident time- Then drill into a specific build using
build_detail,pipeline_stages,build_logsas needed
When to Use
- Deployment-related incidents: Use
cross_controller_deploymentsto see all recent activity across the entire CI/CD infrastructure, not just one controller. - Feature flag incidents: Use
flag_changeswhen an incident might be caused by a feature flag toggle (gradual rollout gone wrong, kill switch activated, etc.). - Controller health: Use
controller_listto check if a controller itself is unhealthy (offline, failing builds).
Important Rules
- Always start with
cross_controller_deploymentsfor broad visibility before drilling into a specific controller. - Use
flag_changeswhen the incident pattern suggests a gradual rollout or toggle (e.g., affecting a percentage of users). - Controller URLs returned by
controller_listcan be used with standard CloudBees CI actions (build_detail, etc.).
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.
- 5d ago First seen · 56 lines · 22 tokens per session scan A 73ddbae07192
cloudbees_oc is a skill published in the GitHub repository Arvo-AI/aurora (404 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 597 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-30.
Other skills, from other repositories
cloud-iam-deep
GCP/AWS/Azure cloud exploitation -- Cloud Functions, Firestore, Cloud Run, S3, MinIO, Blob Storage, SA keys.
awesome-kubernetes-ops
This skill documents the local verification, editing, and deployment procedures for the Antigravity AI Agent when pair-programming with the repository maintainer.
isaac-automator
Deploy and operate a cloud Isaac Workstation with Isaac Automator: provision a GPU VM running Isaac Sim, Isaac Lab, and/or Isaac Lab Arena on AWS, GCP, Azure, or Alibaba Cloud, connect to it, move data in and out, control cost with stop/start, repair, import existing deployments, and destroy. Use when the user wants a…
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
conducting-cloud-infrastructure-penetration-test
Perform a cloud infrastructure penetration test across AWS, Azure, and GCP to identify IAM misconfigurations, exposed storage buckets, insecure serverless functions, and cloud-native attack paths using Pacu, ScoutSuite, and Prowler.
performing-cloud-forensics-investigation
Conduct forensic investigations in cloud environments by collecting and analyzing logs, snapshots, and metadata from AWS, Azure, and GCP services.