devops-flow

A guide for managing software operations in cloud environments such as AWS, Azure, and Google Cloud.

In plain words
What is it for?
Creating infrastructure-as-code, CI/CD configurations, container files, Kubernetes resources, and deployment plans.
Why use it?
It brings infrastructure setup, deployment pipelines, containers, and security practices into one repeatable workflow based on specifications and architecture decisions.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/ushibo/brigade/devops-flow
Any agent
npx skills add ushibo/brigade --skill devops-flow
Clone the repo
git clone --depth 1 https://github.com/ushibo/brigade

Made for: Claude Code, Codex.

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,045 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00026 $0.07045
Opus 5 $0.00013 $0.03522
Sonnet 5 $0.00005 $0.01409
Haiku 4.5 $0.00003 $0.00705

Measured yesterday against content hash fa4b4b30f85a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

devops-flow scanned grade C with 2 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

&& rm -rf /var/lib/apt/lists/*

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

RESPONSE=$(curl -s -o /dev/null -w "%{http_code}" --max-time $TIMEOUT "$HEALTH_URL")
skills/devops-flow/SKILL.md · 1,172 lines

How it starts

The opening of the file, as written. The whole thing — 1,172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

devops-flow

Description: Infrastructure as Code, CI/CD pipeline automation, and deployment management

Category: DevOps & Deployment

Complexity: High (multi-cloud + orchestration + automation)


Purpose

Automate infrastructure provisioning, CI/CD pipelines, and deployment processes based on SPEC documents and ADR decisions. Ensures consistent, repeatable, and secure deployments across environments.


Capabilities

1. Infrastructure as Code (IaC)

  • Terraform: Cloud-agnostic infrastructure provisioning
  • CloudFormation: AWS-native infrastructure
  • Ansible: Configuration management and provisioning
  • Pulumi: Modern IaC with standard programming languages
  • Kubernetes manifests: Container orchestration

2. CI/CD Pipeline Generation

  • GitHub Actions: Workflow automation
  • GitLab CI: Pipeline configuration
  • Jenkins: Pipeline as code
  • CircleCI: Cloud-native CI/CD
  • Azure DevOps: Microsoft ecosystem integration

3. Container Configuration

  • Dockerfile: Container image definition
  • Docker Compose: Multi-container applications
  • Kubernetes: Production orchestration
  • Helm charts: Kubernetes package management
  • Container registry: Image storage and versioning

4. Deployment Strategies

  • Blue-Green: Zero-downtime deployments
  • Canary: Gradual rollout with monitoring
  • Rolling: Sequential instance updates
  • Feature flags: Progressive feature enablement
  • Rollback procedures: Automated failure recovery

5. Environment Management

  • Environment separation: dev, staging, production
  • Configuration management: Environment-specific configs
  • Secret management: Vault, AWS Secrets Manager, etc.
  • Infrastructure versioning: State management
  • Cost optimization: Resource tagging and monitoring

6. Monitoring & Observability

  • Logging: Centralized log aggregation
  • Metrics: Performance and health monitoring
  • Alerting: Incident response automation
  • Tracing: Distributed request tracking
  • Dashboards: Real-time visualization

Read the full file on GitHub · 1,172 lines

Changes

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.

  1. yesterday First seen · 1,172 lines · 26 tokens per session scan C fa4b4b30f85a

Subscribe to this mod's changes

devops-flow is a skill published in the GitHub repository ushibo/brigade (1 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 7,045 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.