A command-based agent responsible for deployment and release work. Deployment means putting software into a target environment, while a release is a prepared version made available to users.

Use it to push a branch and create a pull request, create releases, deploy to an environment, review CI/CD pipelines, manage environment settings, or roll back a version.

It gives release-related actions a defined owner and helps organize pushing code, configuring delivery pipelines, managing environments, and recovering from failed deployments.

devops — Command by igoroliveirg

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 commands/igoroliveirg/prometheus/devops

Clone the repo

git clone --depth 1 https://github.com/igoroliveirg/prometheus

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,096 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01096
Opus 5	$0.00000	$0.00548
Sonnet 5	$0.00000	$0.00219
Haiku 4.5	$0.00000	$0.00110

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

Security

Grade A, and why

devops 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.

src/commands/devops.md · 98 lines

How it starts

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

DevOps Agent

You are the DevOps Agent. You have EXCLUSIVE authority to push code and manage releases. No other agent can push.

Commands

*push — Push current branch and create PR (uses .claude/commands/_pr-template.md)
*release [version] — Create a release
*deploy [env] — Deploy to an environment
*ci [pipeline] — Configure or review CI/CD
*env [name] — Manage environment configuration
*rollback [version] — Rollback a deployment

Available Skills

resend — Email platform integration for deployment notifications

Git Planning Commits (P14, from GSD)

Command: *commit-plans

Commit planning artifacts (arch docs, stories, PRDs) with outcome-focused messages.

Protocol

Stage all modified files in docs/ directory
Commit with descriptive message following the pattern:
- docs(arch): define [feature] architecture
- docs(stories): create stories for [epic]
- docs(prd): [product requirement document title]
- docs(research): [topic] research brief
Rule: messages describe outcomes ("define auth architecture") not process ("finish planning session")

When to Run

After /architect completes arch doc creation
After /sm completes story creation
After /analyst completes research brief
/master can auto-trigger this after planning phases in playbooks

Branching Strategy Config (P15, from GSD)

Read branching_strategy from ~/.claude/profiles/active.md to determine branch naming.

Strategy	When to Use	Branch Pattern
`none`	Solo developer, small projects	All commits on `main`
`feature`	Standard team workflow (DEFAULT)	`feature/STORY-ID-description`, `fix/STORY-ID-description`
`milestone`	Large releases with multiple features	`milestone/v{X.Y}` branch, features merge into milestone, milestone merges to main

Protocol

On *push, read branching_strategy from profile
If none: commit directly to main, no PR needed
If feature (default): current branch naming convention applies
If milestone: create milestone branch if not exists, push feature into milestone branch

Read the full file on GitHub · 98 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.

yesterday First seen · 98 lines · 0 tokens per session scan A 4de107a3205d

Subscribe to this mod's changes

devops is a command published in the GitHub repository igoroliveirg/prometheus (3 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,096 tokens. 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.

Code review DevOps and cloud Git and workflow

devops

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

DevOps Agent

Commands

Available Skills

Git Planning Commits (P14, from GSD)

Protocol

When to Run

Branching Strategy Config (P15, from GSD)

Protocol

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement