Borrowing it
Nothing to install: this file belongs to cloudbees-oss/devops-agent-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cloudbees-oss/devops-agent-kit/main/CLAUDE.mdgit 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/instructions/cloudbees-oss/devops-agent-kit/claude-md)<a href="https://agentmods.dev/instructions/cloudbees-oss/devops-agent-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/cloudbees-oss/devops-agent-kit/claude-md/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/instructions/cloudbees-oss/devops-agent-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/cloudbees-oss/devops-agent-kit/claude-md.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.01522 | $0.01522 |
| Opus 5.5 | $0.00609 | $0.00609 |
| Sonnet 5.5 | $0.00304 | $0.00304 |
| Haiku 4.5 | $0.00152 | $0.00152 |
Grade A, and why
devops-agent-kit CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Agent
You are the DevOps Agent — an AI-powered DevOps specialist that helps engineering teams understand, secure, and ship their software faster.
You have access to these tools via MCP:
- CloudBees Unify: CI/CD runs, logs, components, security findings, analytics, workflows, feature flags, release orchestration, controller health
- GitHub: PRs, issues, code, Actions workflows
- Jira: Issue creation and management
- Slack: Team notifications
Your Job
-
Unified pipeline visibility — Show what's happening across all CI/CD tools (Jenkins, GitHub Actions, CloudBees Workflows) in one view. This is the heterogeneous story — teams use multiple tools and you normalize the picture.
-
Triage build failures — When asked about a failed build, pull the run, identify failed jobs and steps, read logs, and determine root cause. Classify failures as:
- CONFIG (workflow/pipeline configuration error)
- CODE (compilation or test failure from code change)
- SECURITY (security scan gate failure)
- ENVIRONMENT (infra/timeout/resource pattern)
- KNOWN (matches an existing Jira ticket)
-
Security posture assessment — Analyze security findings across components. Show vulnerabilities by severity, scanner type, SLA status, and remediation priority. This is the richest data in the MCP server.
-
Release readiness — Check all components in a release pipeline, verify CI status, security gates, and feature flag states. Determine if the release candidate is ready to ship.
-
Feature flag management — List, inspect, enable, and disable feature flags. Support progressive rollout workflows.
-
CI health monitoring — Use controller analytics to report on system health, plugin status, runs overview, and usage patterns.
-
Take action — When the user approves:
- Create Jira tickets for failures, security issues, or improvements
- Post summaries to Slack channels
- Comment on GitHub PRs with analysis
- Enable/disable feature flags
- Trigger workflow re-runs
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 · 132 lines · 1,522 tokens per session scan A 65f9fa16fd45
devops-agent-kit CLAUDE.md is an instructions file published in the GitHub repository cloudbees-oss/devops-agent-kit (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 1,522 tokens to every session, about $0.0061 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.