agentleFS
Microsoft AzureKnown publisherAzure/terraform-azurerm-avm-res-dataprotection-backupvault/AGENTS.md

terraform-azurerm-avm-res-dataprotection-backupvault

AGENTS.md3 starsChanged 34 days agoMITView on GitHub

Azure Verified Modules (AVM) and Terraform

232 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use the AVM Terraform agent for specification-driven module development.

    line 10
  2. Very specific:

    Do not hand-edit generated README.md files.

    line 17
  3. Very specific:

    Use PowerShell 7.4 or later and Avm.Authoring.

    line 18
  4. Very specific:

    Run the smallest relevant test tier, run avm pre-commit, commit the complete worktree, then run avm pr-check.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Azure Verified Modules (AVM) Terraform

The authoritative repository instructions are .github/copilot-instructions.md. Read that file completely before analyzing or modifying this repository, then load the relevant skill from .github/skills.

Use the AVM Terraform agent for specification-driven module development. When these instructions conflict with a current published AVM specification, the specification takes precedence.

Safety-critical fallback

  • Fetch https://azure.github.io/Azure-Verified-Modules/llms.txt and read the current raw page for every relevant specification. Do not cite AVM requirements from memory.
  • New AVM Terraform modules use Azure/azapi for every control-plane resource and every supported direct Azure operation. Do not use hashicorp/azurerm for convenience, supporting infrastructure, examples, tests, or fixtures.
  • Permit AzureRM only for a specifically documented data-plane or non-ARM operation that AzAPI cannot perform. Independently justify each block and follow avm-tf-azapi and avm-tf-tflint.
  • Do not hand-edit generated README.md files. Edit _header.md and _footer.md, then use avm docs or avm pre-commit.
  • Use PowerShell 7.4 or later and Avm.Authoring; do not substitute retired Make, Porch, container, or repository-launcher workflows.
  • Run the smallest relevant test tier, run avm pre-commit, commit the complete worktree, then run avm pr-check.

The canonical file contains the complete module discovery, tooling, quality, and skill index guidance. Do not duplicate or independently extend those sections here.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.