terraform-azurerm-avm-ptn-alz
Azure/terraform-azurerm-avm-ptn-alz/AGENTS.md
Azure Verified Modules (AVM) and Terraform
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Azure/terraform-azurerm-avm-ptn-alz/AGENTS.md
Azure Verified Modules (AVM) and Terraform
Azure/terraform-azure-avm-res-insights-privatelinkscope/AGENTS.md
Azure Verified Modules (AVM) and Terraform
wshobson/agents/docs/agents.md
debugging, log analysis, deployment troubleshooting | | [deployment-engineer](../plugins/cloud-infrastructure/agents/deployment-engineer.md) | sonnet | CI/CD pipelines, containerization, cloud deployments | | [terraform-specialist](../plugins/cloud-infrastructure/agents/terraform-specialist.md) | opus | Infrastructure as Code with Terraform modules and state management | | [dx-optimizer](../plugins/team-collaboration/agents/dx-optimizer.md
block/buzz/AGENTS.md
building the relay Docker image and pushing to internal ECR | | [squareup/block-coder-tf-stacks](https://github.com/squareup/block-coder-tf-stacks) | Terraform + ArgoCD deploying the relay to the staging Kubernetes cluster | | [squareup/sprout-backend-blox](https://github.com/squareup/sprout-backend-blox) | Desktop backend
hashicorp/terraform-provider-aws/AGENTS.md
when working with code in this repository. ## Repository Overview This is the Go-based Terraform AWS Provider (`github.com/hashicorp/terraform-provider-aws`). It maps AWS API resources to Terraform resources, data sources, ephemeral
google/adk-recipes/core/python/ambient-expense-agent/AGENTS.md
discovery, an IAP-protected approval UI, and Cloud Monitoring email alerts, all provisioned by **Terraform**. ## When To Use - The user wants an **event-driven / ambient** agent (triggered by Pub/Sub
google/adk-recipes/core/python/deep-search/AGENTS.md
powered FastAPI backend. There is no datastore, no ingestion pipeline, and no Terraform — all "data" comes from the built-in `google_search` tool at runtime. ## When To Use - The user
google/adk-recipes/core/python/genmedia-for-commerce/AGENTS.md
validation/retry), the **in-memory catalogue vector search**, and the **full app stack** (FastAPI + React + Terraform + Agent Engine / Gemini Enterprise registration). ## When To Use - The user wants an **orchestrator agent** that
google/adk-recipes/core/python/long-horizon-harness/AGENTS.md
harness interfaces this guide teaches. When studying the *interfaces*, you can skip: - `terraform/` — deploy infra; relevant only if you're running Horizon as a starter. - `tests/eval/` — LLM-behavior validation
google/adk-recipes/core/python/rag-agent-search/AGENTS.md
agent (a thin wrapper around one search tool); it's the **Terraform + data-connector plumbing**. ## When To Use - The user wants a RAG agent without building/maintaining an ingestion pipeline
google/adk-recipes/core/python/rag-vector-search/AGENTS.md
documents into a Collection that auto-generates embeddings server-side. The hard/interesting parts are **Terraform** (Collection + auto-embedding config + IAM) and **data handling** (the ingestion pipeline); the agent itself
maximhq/bifrost/AGENTS.md
skills) ├── go.work # Go workspace — requires Go 1.27.0 ├── Makefile # Build, test, dev commands (1300+ lines) └── terraform/ # Infrastructure as Code ``` --- ## Go Workspace Bifrost is a **multi-module Go workspace**. Each module
google/agents-cli/extensions/langchain/template/AGENTS.md
after `agents-cli install`. - Same error three times means fix the cause, not retry. - Terraform 409: `terraform import`, don't recreate
microsoft/skills/Agents.md
repositories | ### Development Tools | MCP | Purpose | |-----|---------| | `github` | GitHub API operations | | `playwright` | Browser automation and testing | | `terraform` | Infrastructure as code | | `eslint` | JavaScript/TypeScript linting | ### Utilities | MCP | Purpose | |-----|---------| | `sequentialthinking` | Step-by-step reasoning
JetBrains/intellij-plugins/terraform/AGENTS.md
Terraform plugin tests Use these conventions when writing or changing tests in this plugin. ## User interactions - Exercise user interactions, such as opening a file, invoking an action, or formatting code
GoogleCloudPlatform/kubernetes-engine-samples/ai-ml/anthropic-agent-sandbox/AGENTS.md
sandbox (tool execution) runs here, in gVisor pods. Three small containers (`src/worker`, `src/dispatcher`, `src/stats-adapter`), Terraform for the cluster + bucket, Kustomize for the manifests. ## Layout | Path | Purpose | Edit when | | --- | --- | --- | | `terraform
vellum-ai/vellum-assistant/AGENTS.md
meta/feature-flags/AGENTS.md` for naming, registry, resolver, and the required companion PR in `vellum-assistant-platform` (Terraform). **Permission controls v2 rule**: Under `permission-controls-v2`, do not introduce new deterministic approval modes
asklokesh/loki-mode/references/agents.md
Agents) ### ops-devops **Capabilities:** - CI/CD (GitHub Actions, GitLab CI, Jenkins) - Infrastructure as Code (Terraform, Pulumi, CDK) - Container orchestration (Docker, Kubernetes) - Cloud platforms (AWS, GCP, Azure) - GitOps (ArgoCD, Flux) **Task Types
GoogleCloudPlatform/magic-modules/AGENTS.md
Agent Instructions Magic Modules (MMv1) defines the Google Cloud Terraform providers: resource schemas in `mmv1/products/`, handwritten code and tests under `mmv1/third_party/terraform/`, generated into the downstream `terraform-provider-google` and `terraform
cloudflare/mcp/AGENTS.md
user, account, and offline-access OAuth bootstrap scopes sit outside the API catalog. Terraform registration must land before deploying picker additions. The app does not impose a scope-count
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.