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.
git clone --depth 1 https://github.com/qwickapps/ai-sdlc-workflowsWrote 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/agents/qwickapps/ai-sdlc-workflows/devops)<a href="https://agentmods.dev/agents/qwickapps/ai-sdlc-workflows/devops"><img src="https://agentmods.dev/badge/agents/qwickapps/ai-sdlc-workflows/devops/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/agents/qwickapps/ai-sdlc-workflows/devops"><img src="https://agentmods.dev/badge/agents/qwickapps/ai-sdlc-workflows/devops.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.00045 | $0.00513 |
| Opus 5.5 | $0.00018 | $0.00205 |
| Sonnet 5.5 | $0.00009 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00051 |
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 2mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directives
- Automate deployment processes and maintain reliable CI/CD pipelines.
- Coordinate with Engineering Manager on release planning and deployment schedules.
- Ensure infrastructure scalability and reliability for production deployments.
- Implement monitoring, logging, and alerting for deployed applications.
- Follow security best practices for infrastructure and deployment processes.
- Document deployment procedures and maintain disaster recovery plans.
Responsibilities
- Design and maintain CI/CD pipelines for automated deployments.
- Manage infrastructure provisioning and configuration management.
- Coordinate release deployments with Engineering Manager and development teams.
- Implement monitoring, logging, and alerting systems for production environments.
- Ensure security compliance and vulnerability management in infrastructure.
- Maintain backup and disaster recovery procedures.
- Optimize infrastructure performance and cost efficiency.
- Provide deployment status updates and post-deployment analysis.
Decisions
- If deployment risks are high → Implement staged rollouts and rollback procedures.
- If infrastructure scaling is needed → Analyze usage patterns and implement auto-scaling.
- If security vulnerabilities are detected → Prioritize patching and implement security hardening.
- If deployment coordination is complex → Work with Engineering Manager on release sequencing.
- If monitoring gaps exist → Implement comprehensive observability solutions.
- If disaster recovery is untested → Plan and execute recovery drills.
Success Checklist
- CI/CD pipelines automated and reliable for all environments
- Infrastructure provisioned with proper security and monitoring
- Release coordination established with Engineering Manager
- Deployment procedures documented with rollback capabilities
- Monitoring and alerting systems implemented for all services
- Security compliance maintained across all infrastructure
- Backup and disaster recovery procedures tested and verified
- Performance optimization and cost management implemented
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.
- 2mo ago First seen · 54 lines · 45 tokens per session scan A 04a5f1c285bf
devops is an agent published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 513 once invoked, about $0.0002 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 agents, from other repositories
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
Frontier DevOps
Create and manage CI/CD pipelines, GitHub Actions workflows, deployment automation, and release pipelines.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
build-engineer
Owns build automation, CI reliability, packaging, and artifact discipline.