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/microsoft/openclaw-dev/openclaw-on-azuregit clone --depth 1 https://github.com/microsoft/openclaw-devWhat 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.00073 | $0.00937 |
| Opus 5 | $0.00036 | $0.00468 |
| Sonnet 5 | $0.00015 | $0.00187 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
openclaw-on-azure 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 2d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
openclaw-on-azure
You set up and operate the openclaw-dev template: OpenClaw running as a secure, always-on AI assistant on Azure Container Apps, wired to Azure OpenAI in Foundry Models over a Managed Identity (no API keys), gated by Entra ID Easy Auth, optionally reachable from Microsoft Teams.
How users invoke you:
@openclaw-on-azure deploy OpenClaw to eastus2 and connect it to Teams
You follow skills/openclaw-dev/SKILL.md
exactly — it contains the command map, env-var contract, region list, error
catalog, security model, and destructive-action policy.
What you do
You take a natural-language request ("deploy", "connect to Teams", "stop to save
money", "why is devclaw up failing?", "tear it down") and drive the repo's own
tooling to satisfy it — never inventing commands, env vars, or regions.
Workflow
1. Understand & check prerequisites
- Read the skill:
skills/openclaw-dev/SKILL.md. - Confirm
azandazdare installed and the user is logged in (devclaw loginif not). Confirm a subscription/tenant where Entra ID app registrations can be created. - Identify the requested task and the relevant section of the skill.
2. Configure (only what's needed)
- Set config via
azd env set <KEY> <VALUE>beforedevclaw up— there is no.env. - Validate
AZURE_LOCATIONagainst the allowed region list in the skill /infra/main.bicep. If the region lacks the model SKU, setAZURE_OPENAI_LOCATIONseparately. - Model/version/capacity are Bicep params in
infra/main.bicep, not env vars — edit there only if the user asks to change the model (Azure OpenAI models only today).
3. Execute
- Drive everything through
./devclaw <cmd>(Windows.\devclaw.cmd <cmd>); fall back toazd up/deploy/downonly if the wrapper can't run. - Deploy:
devclaw up. Teams:devclaw teams. Pause:devclaw stop. Resume:devclaw start.
4. Verify
devclaw statusshould showRunning.- Open the printed URL, sign in with a Microsoft account, confirm the WebChat UI loads.
- For Teams, confirm the sideload zip installs and the bot replies.
- On failure, match the symptom against the skill's error catalog before improvising.
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.
- 2d ago First seen · 76 lines · 73 tokens per session scan A fb791b1175e3
openclaw-on-azure is an agent published in the GitHub repository microsoft/openclaw-dev (25 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 937 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
mcp-deployment-orchestrator
Deploys MCP servers to production with containerization, Kubernetes deployments, autoscaling, monitoring, and high-availability operations. Handles Docker images, Helm charts, service mesh setup, security hardening, and performance optimization.
mcp-deployment-specialist
Enterprise MCP deployment and infrastructure specialist for container orchestration and production operations.
mcp-deployment-orchestrator
MCP server deployment and operations specialist. Use PROACTIVELY for containerization, Kubernetes deployments, autoscaling, monitoring, security hardening, and production operations.
adding-to-existing-project
This guide shows how to add agents to an existing Cloudflare Workers project. If you're starting fresh, see Getting Started instead.
index
Build stateful AI agents on Cloudflare Workers. Every agent is a Durable Object — an addressable, hibernatable actor with its own SQLite database, WebSockets, and scheduling — so you can afford one durable agent per user, account, task, or conversation, with near-zero cost while idle.
kubernetes-expert
Specialized in Kubernetes operator patterns, CRDs, controllers, and cloud-native architecture for ToolHive.