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 flag-rolloutgit 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/flag-rollout)<a href="https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/flag-rollout"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/flag-rollout/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/flag-rollout"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/flag-rollout.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.00025 | $0.00558 |
| Opus 5.5 | $0.00010 | $0.00223 |
| Sonnet 5.5 | $0.00005 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
flag-rollout 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flag Rollout: $ARGUMENTS
Parse the arguments to determine action and target.
Action: list (default if no flag name given)
-
flags_applications_list— find all flag applications -
For each application:
flags_list— list all flags -
flags_environments_list— list all environments -
For each environment:
flags_configurations_list— get flag states -
Present a flag inventory:
Feature Flags — [Application Name]
Flag Type Production Staging Default Value name Bool ON/OFF ON/OFF value
Action: status [flag-name]
flags_applications_listthenflags_get_by_name— find the flagflags_environments_list— list environmentsflags_configurations_list— get configuration per environment- Present detailed flag status:
- Flag name, type, description, labels
- State in each environment (enabled/disabled, default value)
- Whether the flag is permanent or temporary
Action: enable [flag-name] [environment]
- Find the flag using
flags_get_by_name - Find the environment using
flags_environments_list - Show current state and what will change
- Ask for confirmation — "Enable [flag] in [environment]?"
flags_configuration_state_update(enabled=true)— enable the flag- Confirm the change
- Offer to post the change to Slack
Action: disable [flag-name] [environment]
Same as enable, but with flags_configuration_state_update(enabled=false)
Action: create [flag-name]
flags_applications_list— find the target application- Ask the user for: flag type (Boolean/String/Number), description, labels
flags_add— create the flag- Confirm creation with flag ID
- Offer to enable it in an environment
Safety guardrails for flag changes:
- Always show current state before any change
- Always ask for confirmation before enable/disable
- After any change, verify the new state with
flags_configurations_list - If changing production flags, add an extra warning: "This will affect production traffic. Confirm?"
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 · 65 lines · 25 tokens per session scan A 2b7294db46bf
flag-rollout 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 25 tokens to every session and 558 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…