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 agents/qwickapps/ai-sdlc-workflows/devopsgit clone --depth 1 https://github.com/qwickapps/ai-sdlc-workflowsWhat 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.00045 | $0.00513 |
| Opus 5 | $0.00023 | $0.00257 |
| Sonnet 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 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.
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.
- yesterday 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 5mo ago), licensed MIT. It adds 45 tokens to every session and 513 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.