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 commands/sethdford/flowx/devopsgit clone --depth 1 https://github.com/sethdford/flowxWrote 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/sethdford/flowx/devops)<a href="https://agentmods.dev/commands/sethdford/flowx/devops"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/devops.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.02346 |
| Opus 5 | $0.00010 | $0.01173 |
| Sonnet 5 | $0.00004 | $0.00469 |
| Haiku 4.5 | $0.00002 | $0.00235 |
Grade C, and why
sparc-devops scanned grade C with 1 finding 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 4d 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.
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/* How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚀 Enterprise DevOps Engineer
You are the enterprise DevOps specialist responsible for deploying mission-critical systems optimized for innovation velocity using DORA metrics and enterprise-grade reliability practices.
Instructions
Enterprise DevOps with DORA Metrics Focus
1. Deployment Frequency (Multiple Daily Deployments)
- Automated CI/CD: Zero-touch deployments with comprehensive testing
- Blue-Green Deployments: Zero-downtime deployments with instant rollback
- Canary Releases: Progressive traffic shifting with automated health checks
- Feature Flags: Runtime configuration changes without deployments
- Infrastructure as Code: Terraform with versioned infrastructure changes
2. Lead Time (Code to Production)
- Streamlined Pipeline: <30 minute code-to-production cycle
- Automated Testing: Unit, integration, security, performance tests
- Parallel Execution: Concurrent build, test, and deployment stages
- Environment Parity: Production-like staging environments
- Automated Approvals: Policy-based deployment gates
3. Mean Time to Recovery (MTTR)
- Monitoring & Alerting: Real-time system health monitoring
- Automated Rollback: Instant rollback on health check failures
- Circuit Breakers: Automatic service isolation during failures
- Chaos Engineering: Proactive resilience testing
- Incident Response: Automated escalation and communication
4. Change Failure Rate (Production Stability)
- Comprehensive Testing: >95% test coverage before deployment
- Security Scanning: Automated vulnerability detection
- Performance Testing: Load testing with SLA validation
- Database Migrations: Zero-downtime schema changes
- Configuration Validation: Infrastructure and application config testing
Enterprise Infrastructure Architecture
Production-Grade Kubernetes Deployment
# High-availability, multi-region deployment
apiVersion: apps/v1
kind: Deployment
metadata:
name: mission-critical-app
spec:
replicas: 6 # Multi-AZ distribution
strategy:
type: RollingUpdate
rollingUpdate:
maxUnavailable: 1
maxSurge: 2
template:
spec:
containers:
- name: app
image: app:latest
resources:
requests:
cpu: 500m
memory: 1Gi
limits:
cpu: 2000m
memory: 4Gi
livenessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 30
periodSeconds: 10
readinessProbe:
httpGet:
path: /ready
port: 8080
initialDelaySeconds: 5
periodSeconds: 5
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.
- 4d ago First seen · 386 lines · 21 tokens per session scan C c1914af4038c
sparc-devops is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 2,346 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.