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/release-statusnpx skills add cloudbees-oss/devops-agent-kit --skill release-statusgit 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.00029 | $0.00517 |
| Opus 5 | $0.00015 | $0.00259 |
| Sonnet 5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
release-status 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 yesterday.
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
Release Status: $ARGUMENTS
-
components_list— get all components in the organization -
For each component: a.
workflow_list— identify CI and release workflows b.runs_list(limit=5)— get latest run status per workflow Skip code_scan workflows. c.security_issues_open_getorsecurity_findings_summary_get— check for open vulnerabilities on the default branch d.branches_list— verify the default branch -
Check release orchestration: a. Look for components with release/deploy workflows (workflow_dispatch triggers, staged deployments) b.
automation_jobs_list— check for staged deployment jobs (staging -> approval -> production pattern) c. Check for PENDING_APPROVAL jobs — these are deployment gates waiting on human sign-off -
Check feature flags: a.
flags_applications_list— find flag applications b.flags_environments_list— list environments (staging, production) c.flags_configurations_list— check flag states per environment -
Present a release readiness report:
Release Readiness Report Date: [timestamp] Verdict: READY / NOT READY / BLOCKED
Component CI Status Security Flags Blocker name GREEN/RED N HIGH state desc Blockers by Priority:
- [Highest priority blocker with specific details]
- [Next blocker] ...
What Must Be Done Before Release:
- Specific action item 1
- Specific action item 2
-
Offer next actions:
- "/triage [component]" for any red component
- "/security-scan [component]" for components with findings
- "/flag-rollout [flag] enable" to activate flags for release
- Post release readiness to Slack
- Trigger release workflow via
workflow_trigger(with explicit user confirmation — show which workflow will be triggered and what it will do before executing)
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.
- yesterday First seen · 60 lines · 29 tokens per session scan A 00523e4b7010
release-status 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 29 tokens to every session and 517 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…