horizon: Instructions file for GitHub Copilot

.github/instructions/azure-arm-client.instructions.md

horizon azure-arm-client.instructions.md is an instructions file for GitHub Copilot from peters/horizon. It costs 267 tokens per session, scanned A, original, MIT.

A set of review rules for an Azure Resource Manager client, which is code that manages Azure resources through Microsoft's API. It covers URL validation, response handling, polling, retries, and reconciliation.

In plain words
What is it for?
It is for reviewing or implementing Azure resource-management API code while preserving its network, error, and operation boundaries.
Why use it?
It prevents unsafe requests, leaks of response data, invalid operation polling, and incorrect handling of uncertain Azure responses.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is peters/horizon's own configuration. It tells GitHub Copilot how to work on horizon itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything horizon configures →

Reuse

Borrowing it

Nothing to install: this file belongs to peters/horizon. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/peters/horizon/main/.github/instructions/azure-arm-client.instructions.md
Clone the repo
git clone --depth 1 https://github.com/peters/horizon

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for horizon azure-arm-client.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/peters/horizon/azure-arm-client/github.svg)](https://agentmods.dev/instructions/peters/horizon/azure-arm-client)
Your own site
<a href="https://agentmods.dev/instructions/peters/horizon/azure-arm-client"><img src="https://agentmods.dev/badge/instructions/peters/horizon/azure-arm-client/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.

agentmods 80×15 button for horizon azure-arm-client.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/peters/horizon/azure-arm-client"><img src="https://agentmods.dev/badge/instructions/peters/horizon/azure-arm-client.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 267 This file is loaded in full into every session.
When invoked 267 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00267 $0.00267
Opus 5.5 $0.00107 $0.00107
Sonnet 5.5 $0.00053 $0.00053
Haiku 4.5 $0.00027 $0.00027

Measured 3d ago against content hash 35839fb6d6fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

horizon azure-arm-client.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 3d 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.

.github/instructions/azure-arm-client.instructions.md · 23 lines

What it actually says

Azure ARM client boundary

Read docs/architecture/azure-arm-client.md before review.

  • An ARM answer is untrusted data: status, headers, body and operation URL.
  • Build each URL only from validated segments. A bad segment sends nothing.
  • Keep the HTTPS-only, no-redirect and 30-second rules of the production agent. Do not make with_agent or with_sleeps public.
  • Read a success body with RESPONSE_LIMIT and a failure body with FAILURE_BODY_LIMIT. Never put body text in an error except as a Reason.
  • Poll an operation URL only after owns_operation_url accepts it.
  • A 409 is not definite and is never retried.
  • reconcile sends GET requests only and adopts a group only with the exact name and horizon-operation tag.
  • Do not add credential sources, power actions, run commands or UI, CLI or MCP callers as part of this client.
  • azure/catalog.rs and azure/catalog/** are not part of this client. Review them with azure-price-catalog.instructions.md.
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. 3d ago First seen · 23 lines · 267 tokens per session scan A 35839fb6d6fe

Subscribe to this mod's changes

horizon azure-arm-client.instructions.md is an instructions file published in the GitHub repository peters/horizon (722 stars, last pushed today), licensed MIT. It adds 267 tokens to every session, about $0.0011 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-10-25.

Related

Other instructions, from other repositories

plan-forge dapr.instructions.md

Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.

srnichols/plan-forge · 4,975 tokens

vscode buildNext.instructions.md

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 · 9,715 tokens

next.js AGENTS.md

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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens