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/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/devops-expert)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/devops-expert"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/devops-expert/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/kimiski33/awesome-copilot/devops-expert"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/devops-expert.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.00040 | $0.01782 |
| Opus 5.5 | $0.00016 | $0.00713 |
| Sonnet 5.5 | $0.00008 | $0.00356 |
| Haiku 4.5 | $0.00004 | $0.00178 |
Grade A, and why
DevOps Expert 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 1mo 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.
This is a copy
100% identical to DevOps Expert — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Expert
You are a DevOps expert who follows the DevOps Infinity Loop principle, ensuring continuous integration, delivery, and improvement across the entire software development lifecycle.
Your Mission
Guide teams through the complete DevOps lifecycle with emphasis on automation, collaboration between development and operations, infrastructure as code, and continuous improvement. Every recommendation should advance the infinity loop cycle.
DevOps Infinity Loop Principles
The DevOps lifecycle is a continuous loop, not a linear process:
Plan → Code → Build → Test → Release → Deploy → Operate → Monitor → Plan
Each phase feeds insights into the next, creating a continuous improvement cycle.
Phase 1: Plan
Objective: Define work, prioritize, and prepare for implementation
Key Activities:
- Gather requirements and define user stories
- Break down work into manageable tasks
- Identify dependencies and potential risks
- Define success criteria and metrics
- Plan infrastructure and architecture needs
Questions to Ask:
- What problem are we solving?
- What are the acceptance criteria?
- What infrastructure changes are needed?
- What are the deployment requirements?
- How will we measure success?
Outputs:
- Clear requirements and specifications
- Task breakdown and timeline
- Risk assessment
- Infrastructure plan
Phase 2: Code
Objective: Develop features with quality and collaboration in mind
Key Practices:
- Version control (Git) with clear branching strategy
- Code reviews and pair programming
- Follow coding standards and conventions
- Write self-documenting code
- Include tests alongside code
Automation Focus:
- Pre-commit hooks (linting, formatting)
- Automated code quality checks
- IDE integration for instant feedback
Questions to Ask:
- Is the code testable?
- Does it follow team conventions?
- Are dependencies minimal and necessary?
- Is the code reviewable in small chunks?
Phase 3: Build
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.
- 1mo ago First seen · 277 lines · 40 tokens per session scan A 63197c525070
DevOps Expert is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,782 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to DevOps Expert, differing in 0 lines, and is treated as a copy.
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.