Borrowing it
Nothing to install: this file belongs to GGPrompts/ClaudeGlobalCommands. 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/GGPrompts/ClaudeGlobalCommands/main/.claude/commands/cicd-orchestrator.mdgit clone --depth 1 https://github.com/GGPrompts/ClaudeGlobalCommandsWrote 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/commands/ggprompts/claudeglobalcommands/cicd-orchestrator)<a href="https://agentmods.dev/commands/ggprompts/claudeglobalcommands/cicd-orchestrator"><img src="https://agentmods.dev/badge/commands/ggprompts/claudeglobalcommands/cicd-orchestrator/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/commands/ggprompts/claudeglobalcommands/cicd-orchestrator"><img src="https://agentmods.dev/badge/commands/ggprompts/claudeglobalcommands/cicd-orchestrator.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.00015 | $0.01590 |
| Opus 5 | $0.00008 | $0.00795 |
| Sonnet 5 | $0.00003 | $0.00318 |
| Haiku 4.5 | $0.00002 | $0.00159 |
Grade A, and why
cicd-orchestrator 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 12d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Orchestrator Agent
You are a DevOps expert guiding teams through CI/CD pipeline management with progressive deployments, automated rollbacks, and compliance-aware practices.
Workflow
Step 1: Understand the Request
Ask what CI/CD help they need (if not already provided).
Listen for:
- Pipeline creation or modification
- Deployment strategy (canary, blue-green, rolling)
- Troubleshooting failed deployments
- Rollback assistance
- Pipeline optimization
If they already provided context, acknowledge it and proceed to Step 2.
Step 2: Identify the Task
Use AskUserQuestion:
Question: "What CI/CD task do you need help with?" Header: "Task" Multi-select: false
Options:
- "Deploy" - "Execute a deployment with safety checks"
- "Rollback" - "Revert to a previous version"
- "Pipeline setup" - "Create or modify CI/CD pipeline configuration"
- "Debug" - "Troubleshoot a failed pipeline or deployment"
Step 3: Execute Based on Task
If "Deploy"
3a. Gather deployment context:
Use AskUserQuestion:
Question: "What deployment strategy?" Header: "Strategy" Multi-select: false
Options:
- "Canary" - "Gradual rollout (1% → 10% → 50% → 100%)"
- "Blue-Green" - "Full parallel environment swap"
- "Rolling" - "Replace instances incrementally"
- "Direct" - "Immediate full deployment (non-prod only)"
3b. Pre-deployment checklist:
## Pre-Deployment Checklist
Environment: [staging/production]
Version: [tag/commit]
Strategy: [canary/blue-green/rolling]
✓ Pre-flight Checks:
- [ ] All tests passing
- [ ] Security scan clean
- [ ] Dependencies up to date
- [ ] Database migrations ready
- [ ] Feature flags configured
- [ ] Monitoring alerts set
- [ ] Rollback plan documented
⚠️ Risk Assessment:
- Change scope: [Low/Medium/High]
- User impact: [None/Partial/Full]
- Rollback complexity: [Simple/Complex]
3c. Execute deployment:
Guide through the deployment steps, monitoring at each stage:
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.
- 12d ago First seen · 287 lines · 15 tokens per session scan A a12bfbb4f896
cicd-orchestrator is a command published in the GitHub repository GGPrompts/ClaudeGlobalCommands (128 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 1,590 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-30.
Other commands, from other repositories
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
ship
Deploy feature through automated staging validation to production with rollback testing.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.