blaktron/azure-environment-builder
Designs an Azure environment with you step by step, then deploys it through Azure Resource Manager from a plan file or with your approval.
Declared capabilities
Ships knowledge: azure_knowledge (77.2 KB), in the release archive under knowledge/<name>/, scanned with the version. What the scan read
Capabilities are the author's declaration and the basis for policy and scanning. The registry cannot enforce them at run time. Your runtime should.
MCP servers & tools
agentry run serves exactly the tools this contract declares, through a per-run MCP gateway. An undeclared capability is a tool that does not exist at run time.
Tools the runner grants
| Manifest declaration | Tool(s) granted |
|---|---|
| (always) | write_report — reports → the run's output folder |
| (always) | list_inputs, read_input, search_inputs — operator-provided input files, read-only |
| (always) | scratch_list, scratch_read, scratch_write, scratch_search — the run's own scratch folder at /scratch, private to the run and deleted at its end; the runner's grant, not a line of the contract |
| (always) | export_pdf — a Markdown report as a PDF in reports/, laid out in your report design; the runner's grant, not a line of the contract |
| (always) | grep, glob — search file contents by regular expression and list files by path pattern (ripgrep), one area a call: the inputs, attached knowledge, /scratch; the runner's grant, not a line of the contract |
| network.egress | fetch — pinned to management.azure.com, prices.azure.com |
MCP servers involved
- QuickAgent Tools — the runner's companion server, served through a per-run Docker MCP Gateway; its tool surface is exactly the table above.
- Operator-cataloged MCP servers may be attached for the declared dataAccess category (other); undeclared categories are never wired in.
Keys & identities
AZURE_ACCESS_TOKEN
The runner's guided setup collects these once into the QuickAgent's MCP profile, kept or removed per the operator's choice. Values are never published or shown.
In an embedded install
Installed into an existing coding agent (agentry install), the same contract maps to the host's built-in tools — enforcement there is the host's. Allowed tools: WebFetch(domain:management.azure.com), WebFetch(domain:prices.azure.com).
Install
agentry install blaktron/azure-environment-builder@0.1.0git clone https://secureagentry.net/blaktron/azure-environment-builder.gitgit clone ssh://git@git.secureagentry.net/blaktron/azure-environment-builder.gitclaude-skill is this agent's default target, so the flag is not needed.
- knowledge/
- AGENT.md20.4 kB
- agent.yaml3.2 kB
- LICENSE1.1 kB
- README.md168 B
README.md
azure-environment-builder
Designs an Azure environment with you step by step, then deploys it through Azure Resource Manager from a plan file or with your approval.