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/cloudbeesnpx skills add Arvo-AI/aurora --skill cloudbeesgit 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)<a href="https://agentmods.dev/skills/arvo-ai/aurora/cloudbees"><img src="https://agentmods.dev/badge/skills/arvo-ai/aurora/cloudbees.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.00023 | $0.01259 |
| Opus 5 | $0.00012 | $0.00629 |
| Sonnet 5 | $0.00005 | $0.00252 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
cloudbees 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CloudBees CI Integration
Overview
CloudBees CI integration for investigating builds and deployments during Root Cause Analysis. CloudBees CI uses the same APIs as Jenkins: Core REST API, Pipeline REST API (wfapi), and Blue Ocean REST API.
Instructions
Tool: cloudbees_rca
Unified CloudBees CI investigation tool for Root Cause Analysis.
Actions:
recent_deployments-- Query stored deployment events; optionalservicefilter andtime_window_hoursbuild_detail-- Core API: SCM revision, changeSets, build causes, parameters. Requiresjob_path+build_numberpipeline_stages-- wfapi: stage-level breakdown with status and timing. Requiresjob_path+build_numberstage_log-- wfapi: per-stage log output for a specificnode_id. Requiresjob_path+build_number+node_idbuild_logs-- Core API: console output, truncated to ~1MB. Requiresjob_path+build_numbertest_results-- Core API: test report with failure details. Requiresjob_path+build_numberblue_ocean_run-- Blue Ocean API: run data with changeSet and commit info. Requirespipeline_name+run_numberblue_ocean_steps-- Blue Ocean API: step-level detail for a pipeline node. Requirespipeline_name+run_number
Required params vary by action: job_path + build_number for Core/wfapi, pipeline_name + run_number for Blue Ocean. service is optional for recent_deployments.
RCA Investigation Flow
Recent deployments are a leading indicator of root cause. Always check if a deployment occurred shortly before the alert fired.
cloudbees_rca(action='recent_deployments', service='SERVICE')-- Check for recent deployscloudbees_rca(action='build_detail', job_path='JOB', build_number=N)-- Build details + commitscloudbees_rca(action='pipeline_stages', job_path='JOB', build_number=N)-- Stage breakdowncloudbees_rca(action='build_logs', job_path='JOB', build_number=N)-- Console outputcloudbees_rca(action='test_results', job_path='JOB', build_number=N)-- Test failures
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.
- 4d ago First seen · 100 lines · 23 tokens per session scan A 33205e702d23
cloudbees is a skill published in the GitHub repository Arvo-AI/aurora (404 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 1,259 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.
console-audit
Audit the running app via chrome-devtools MCP — console errors/warnings + failed/slow network by default; perf (LCP/CLS) and Lighthouse (a11y/SEO) are opt-in. Token-efficient (compacts findings in-browser via a console/network hook); the report is shown inline in the response — no files to open. Target one tab / an…
create-issue
Create GitHub issues using repo templates (feature, bug, spike).