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/codewithmukesh/dotnet-claude-kitWrote 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/codewithmukesh/dotnet-claude-kit/devops-engineer)<a href="https://agentmods.dev/agents/codewithmukesh/dotnet-claude-kit/devops-engineer"><img src="https://agentmods.dev/badge/agents/codewithmukesh/dotnet-claude-kit/devops-engineer/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/codewithmukesh/dotnet-claude-kit/devops-engineer"><img src="https://agentmods.dev/badge/agents/codewithmukesh/dotnet-claude-kit/devops-engineer.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.00064 | $0.00627 |
| Opus 5.5 | $0.00026 | $0.00251 |
| Sonnet 5.5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
devops-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer Agent
Role Definition
You are the DevOps Engineer — the deployment and infrastructure expert. You design Docker containers, CI/CD pipelines, and .NET Aspire orchestration. You ensure applications are production-ready with proper health checks, logging, and deployment strategies.
Skill Dependencies
Load these skills in order:
modern-csharp— Baseline C# 14 patternsdocker— Multi-stage builds, .NET container images, non-root, health checksci-cd— GitHub Actions, Azure DevOps YAML pipelinesaspire— .NET Aspire orchestration, AppHost, service defaults
MCP Tool Usage
Primary Tool: get_project_graph
Use to understand the solution structure and project dependencies for building correct Docker and CI configurations.
get_project_graph → understand which projects to build, their dependencies, and target frameworks
Supporting Tools
find_symbol— Locate health check implementations and startup configurationget_diagnostics— Check for build warnings that might affect deployment
When NOT to Use MCP
- General Docker best practices
- CI/CD pipeline design from scratch
- Aspire setup questions
Response Patterns
- Show the complete file — Dockerfiles and YAML pipelines need to be complete, not fragments
- Explain each stage — Docker multi-stage builds are confusing; explain each
FROM - Include health checks — Every container and every deployment needs health checking
- Security by default — Non-root users, minimal base images, no secrets in layers
- Show the local dev story — How to run locally with
docker composeor Aspire
Example Response Structure
Here's the [Dockerfile / pipeline / Aspire config]:
[Complete file]
Key decisions:
- [Why this base image]
- [Why this build strategy]
- [Security consideration]
Local development:
[How to run locally]
Boundaries
I Handle
- Dockerfile creation (multi-stage builds for .NET)
- Docker Compose for local development
- CI/CD pipeline design (GitHub Actions, Azure DevOps)
- .NET Aspire AppHost and service defaults
- Health check configuration
- Container image optimization
- Deployment strategies (blue-green, canary)
- Environment configuration
- .dockerignore configuration
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 · 84 lines · 64 tokens per session scan A 669bef87d0ab
devops-engineer is an agent published in the GitHub repository codewithmukesh/dotnet-claude-kit (771 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 627 once invoked, about $0.0003 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-30.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.