Manifest
The manifest as the registry validated and stored it, in canonical JSON.
{
"name": "azure-environment-builder",
"tags": [
"azure",
"cloud",
"infrastructure",
"arm",
"deployment",
"architecture",
"landing-zone"
],
"guide": {
"task": "e.g. Set up dev and prod for a web app with a SQL database in West Europe, budget 500 EUR a month",
"files": "Optional: a plan or requirements document (Word, PDF, Markdown, text), YAML or JSON, an ARM template, or a Bicep file.",
"connect": {
"AZURE_ACCESS_TOKEN": "Optional. Needed only if you want the agent to make changes or read your subscription. It is a short-lived token (about an hour) that carries the rights of whoever created it.\n\n1. Sign in with Azure CLI, preferably as a service principal limited to one resource group: `az ad sp create-for-rbac --name <name> --role Contributor --scopes /subscriptions/<id>/resourceGroups/<rg>`, then `az login --service-principal ...`. Never share the printed secret.\n2. Run `az account get-access-token --resource https://management.azure.com --query accessToken -o tsv`.\n3. Paste the output here when the run starts.\n\nGive the least role that does the job at the narrowest scope. Creating resource groups or role assignments needs a wider scope. Without the token the agent works in design-only mode."
},
"prepare": [
"Know roughly what you will run in Azure, who uses it, your region and your monthly budget.",
"Have your Azure subscription ID if you already have one.",
"To let it make changes, sign in with Azure CLI, preferably as a service principal limited to one resource group, and create an access token.",
"For an unattended run, write your plan as a document, YAML, an ARM template or a Bicep file.",
"Leave the token out to get design, templates and steps only."
],
"overview": "Works with you to design an Azure environment from your requirements, then builds it. It proposes a design and a cost estimate for your approval, writes ARM deployment templates, and, if you give it a short-lived Azure access token, validates, previews and deploys them stage by stage. If you give it a plan file it follows that plan, and it can run on its own with a plan and a token. Without a token it hands you the templates and exact steps. It ends with a report."
},
"modes": [
"autonomous",
"interactive"
],
"license": "MIT",
"publish": {
"include": [
"agent.yaml",
"AGENT.md",
"README.md",
"LICENSE",
"knowledge/**"
]
},
"summary": "Designs an Azure environment with you step by step, then deploys it through Azure Resource Manager from a plan file or with your approval.",
"version": "0.1.0",
"knowledge": {
"ships": [
{
"name": "azure_knowledge"
}
]
},
"namespace": "blaktron",
"entrypoints": {
"instruction": "AGENT.md"
},
"interactive": {
"opening": "Tell me what you want to run in Azure (an app, VMs, a data platform, a team sandbox, a landing zone) and who will use it. Add your region, budget and any plan file you have. I'll ask for the rest, propose a design for your approval, then build it if you gave me a token, or give you templates and steps to apply yourself."
},
"capabilities": {
"exec": "none",
"network": {
"egress": [
"management.azure.com",
"prices.azure.com"
]
},
"secrets": [
"AZURE_ACCESS_TOKEN"
],
"dataAccess": [
"other"
],
"filesystem": {
"read": "none",
"write": "none"
},
"optionalSecrets": [
"AZURE_ACCESS_TOKEN"
]
},
"schemaVersion": "2"
}