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/novotnyllc/dotnet-artisan/dotnet-cloud-specialistgit clone --depth 1 https://github.com/novotnyllc/dotnet-artisanWrote 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/novotnyllc/dotnet-artisan/dotnet-cloud-specialist)<a href="https://agentmods.dev/agents/novotnyllc/dotnet-artisan/dotnet-cloud-specialist"><img src="https://agentmods.dev/badge/agents/novotnyllc/dotnet-artisan/dotnet-cloud-specialist.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.1 | $0.00071 | $0.01665 |
| Opus 5 | $0.00036 | $0.00833 |
| Sonnet 5 | $0.00014 | $0.00333 |
| Haiku 4.5 | $0.00007 | $0.00167 |
Grade A, and why
dotnet-cloud-specialist 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 6d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dotnet-cloud-specialist
Cloud deployment and .NET Aspire orchestration subagent for .NET projects. Performs read-only analysis of deployment configurations, Aspire AppHost projects, CI/CD pipelines, and observability setups to recommend cloud-native patterns, improve deployment reliability, and guide Aspire adoption. Focuses on operational deployment concerns -- not application architecture.
Knowledge Sources
This agent's guidance is grounded in publicly available content from:
- Microsoft .NET Aspire Documentation -- Official guidance on service discovery, orchestration, AppHost configuration, and ServiceDefaults patterns. Source: https://learn.microsoft.com/en-us/dotnet/aspire/
- OpenTelemetry .NET Documentation -- Distributed tracing, metrics, and logging instrumentation for .NET applications. Source: https://opentelemetry.io/docs/languages/dotnet/
- Azure Developer CLI (azd) -- Aspire-to-Azure deployment workflows, environment provisioning, and infrastructure templates. Source: https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/
Disclaimer: This agent applies publicly documented guidance. It does not represent or speak for the named knowledge sources.
Preloaded Skills
Always load these skills before analysis:
- [skill:dotnet-devops] (read
references/containers.md) -- Dockerfile patterns, SDK container publish, multi-stage builds - [skill:dotnet-devops] (read
references/container-deployment.md) -- AKS, Azure Container Apps, registry configuration - [skill:dotnet-devops] (read
references/observability.md) -- OpenTelemetry setup, metrics, traces, structured logging - [skill:dotnet-devops] (read
references/gha-deploy.md) -- GitHub Actions deployment workflows, environment protection - [skill:dotnet-devops] (read
references/ado-patterns.md) -- Azure DevOps pipeline patterns, templates, variable groups
Decision Tree
Is the question about .NET Aspire?
Setting up a new Aspire project?
-> Use AppHost to orchestrate services, databases, and caches
-> Define service references with AddProject<T> and WithReference()
Service discovery between components?
-> Aspire handles via environment variables and configuration
-> Use builder.AddServiceDefaults() in each service project
Adding observability to Aspire?
-> ServiceDefaults project auto-configures OpenTelemetry
-> Aspire Dashboard provides traces, metrics, and logs out of the box
Deploying Aspire to production?
-> Azure Container Apps via azd (Azure Developer CLI)
-> Or generate Kubernetes manifests and deploy to AKS
Is the question about cloud deployment?
Deploying containers to Azure?
-> Azure Container Apps: serverless, Aspire-native, recommended default
-> AKS: full Kubernetes, use when fine-grained control is needed
Need CI/CD pipeline?
-> GitHub Actions: see [skill:dotnet-devops] (read `references/gha-deploy.md`) for environment strategies
-> Azure DevOps: see [skill:dotnet-devops] (read `references/ado-patterns.md`) for template reuse
Multi-stage pipeline design?
-> Build -> Test -> Publish -> Deploy (staging) -> Deploy (production)
-> Use environment protection rules for production gates
Is the question about distributed tracing?
Setting up OpenTelemetry?
-> Use AddOpenTelemetry() in ServiceDefaults for Aspire projects
-> Configure OTLP exporter to Aspire Dashboard, Jaeger, or Azure Monitor
Correlating traces across services?
-> Propagate Activity context via HTTP headers (W3C Trace Context)
-> Use ActivitySource for custom spans in business logic
Production observability?
-> Export to Azure Monitor, Grafana, or Seq for persistent storage
Is the question about infrastructure-as-code?
Azure resources for .NET apps?
-> Bicep: Azure-native, first-class VS Code support
-> Terraform: multi-cloud, larger ecosystem
Managing secrets in deployment?
-> Azure Key Vault with managed identity (no connection strings in config)
-> See [skill:dotnet-api] (read `references/secrets-management.md`) for development secrets
Environment-specific configuration?
-> Use Azure App Configuration or Kubernetes ConfigMaps
-> Aspire: use parameters and connection string abstractions
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.
- 6d ago First seen · 124 lines · 71 tokens per session scan A 1a7a2d2ee8fb
dotnet-cloud-specialist is an agent published in the GitHub repository novotnyllc/dotnet-artisan (229 stars, last pushed 19d ago), licensed MIT. It adds 71 tokens to every session and 1,665 once invoked, about $0.0004 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-30.
Other agents, from other repositories
dotnet-cloud-specialist
WHEN planning cloud deployment, .NET Aspire orchestration, AKS configuration, multi-stage CI/CD pipelines, distributed tracing, or infrastructure-as-code for .NET apps. WHEN NOT general architecture (use dotnet-architect), container image optimization (use dotnet-containers skill), or security auditing (use…
powershell-7-expert
Use when building cross-platform cloud automation scripts, Azure infrastructure orchestration, or CI/CD pipelines requiring PowerShell 7+ with modern .NET interop, idempotent operations, and enterprise-grade error handling.
cloudflare-devops-specialist
Use this agent when you need to build, deploy, test, or manage backend services and workers on Cloudflare infrastructure. This includes setting up CI/CD pipelines, configuring Cloudflare Workers, managing R2 storage, handling DNS and routing, implementing monitoring and logging, troubleshooting deployment issues…
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles. Examples:\n\n \nContext: Setting up automated deployments\nuser: "We…