agentmods.dev

openclaw-dev copilot-instructions.md

A set of instructions for working with the openclaw-dev Azure deployment template. It defines the approved commands, configuration locations, region rules, and operating constraints for the template.

In plain words
What is it for?
Use it whenever you deploy, configure, operate, troubleshoot, connect to Teams, or remove this OpenClaw environment.
Why use it?
It prevents deployment work from using the wrong entry point, unsupported settings, or unsafe teardown steps.

Instructions file for GitHub Copilot

25 2mo ago A scan 861 tokens original MIT
View the source file microsoft/openclaw-dev
Install

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.

agentmods
npx agentmods add instructions/microsoft/openclaw-dev/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/microsoft/openclaw-dev

Made for: GitHub Copilot.

Per session 861 This file is loaded in full into every session.
When invoked 861 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00861 $0.00861
Opus 5 $0.00430 $0.00430
Sonnet 5 $0.00172 $0.00172
Haiku 4.5 $0.00086 $0.00086

Measured yesterday against content hash ba381ac5fa5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

openclaw-dev copilot-instructions.md 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.

.github/copilot-instructions.md · 54 lines

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.

Copilot instructions — openclaw-dev

This repo deploys OpenClaw as a secure, hosted 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, with an optional Microsoft Teams channel. It is an alpha, single-tenant dev/test template.

When the user asks you to deploy, configure, operate, troubleshoot, connect to Teams, or tear down this template, follow the playbook in skills/openclaw-dev/SKILL.md. Use this repo's own scripts, env-var contract, region list, and error catalog instead of guessing.

Always-on rules

  • Single entrypoint: drive everything through ./devclaw <cmd> (Windows: .\devclaw.cmd <cmd>), which wraps azd. Fall back to azd up/azd deploy/ azd down directly only if the wrapper isn't runnable.
  • Configuration is via azd env set <KEY> <VALUE> before devclaw up — there is no .env file to edit. Model/version/capacity are Bicep params in infra/main.bicep (aiModelName/aiModelVersion/aiModelCapacity), not env vars.
  • Region: AZURE_LOCATION must be in the allowed list in infra/main.bicep. If the chosen region lacks the model SKU, set AZURE_OPENAI_LOCATION separately.
  • Teams is opt-in: default devclaw up is browser-only — no Bot app registration, no Azure Bot, no Teams channel. To enable: azd env set ENABLE_TEAMS true then re-run devclaw up, or just run devclaw teams (it prompts to enable and re-provisions). Don't suggest creating bot app registrations by default — they fail on restricted tenants.
  • Restricted subscriptions/tenants: before devclaw up, set whichever of these apply: SERVICE_MANAGEMENT_REFERENCE=<smr-guid> (tenants that require it on new app regs), SKIP_STORAGE=true (subscriptions whose Azure Policy blocks shared-key storage — ACA file mounts need shared keys today; gateway token + sessions won't persist across replica restarts). ACR admin is already disabled; image pulls use the container app's managed identity.
  • Model scope: today this targets Azure OpenAI models only (default gpt-5.4-mini). Do not claim Claude or other Foundry Models work today — they are "near future" scope.
  • Passwordless: the model is called keyless via Managed Identity (disableLocalAuth: true). Never add API keys or suggest key-based auth.
  • Secrets: never commit secrets. _local/, .azure/, .azure-cli/, .azd-config/, the generated teams/package/manifest.json, and teams/openclaw-teams-app.zip are gitignored — keep it that way.
  • Confirm destructive actions: before devclaw down / azd down, az ad app delete, RBAC removal, or deleting state, state exactly what will be destroyed and get explicit user confirmation. Never pass --force/--no-prompt to skip a confirmation the user hasn't given.
  • Cost: to pause, use devclaw stop (scale to 0, $0, state kept) — not down.

Read the full file on GitHub · 54 lines

Changes

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.

  1. yesterday First seen · 54 lines · 861 tokens per session scan A ba381ac5fa5b

Subscribe to this mod's changes

openclaw-dev copilot-instructions.md is an instructions file published in the GitHub repository microsoft/openclaw-dev (25 stars, last pushed 2mo ago), licensed MIT. It adds 861 tokens to every session, about $0.0043 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.

DebuggingDevOps and cloud
Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens