Awesome azd is a curated collection of articles, videos, tutorials, documentation, and ready-to-use templates for the Azure Developer CLI, a tool for coding, building, deploying, and monitoring applications on Azure. Developers use it to learn azd and find application templates with Bicep or Terraform infrastructure definitions. The catalogue add-ons support working with this resource collection and its Azure development workflows.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Azure/awesome-azd --skill awesome-azd-template-submitgit clone --depth 1 https://github.com/Azure/awesome-azdWrote 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.
[](https://agentmods.dev/skills/azure/awesome-azd/awesome-azd-template-submit)<a href="https://agentmods.dev/skills/azure/awesome-azd/awesome-azd-template-submit"><img src="https://agentmods.dev/badge/skills/azure/awesome-azd/awesome-azd-template-submit/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.
<a href="https://agentmods.dev/skills/azure/awesome-azd/awesome-azd-template-submit"><img src="https://agentmods.dev/badge/skills/azure/awesome-azd/awesome-azd-template-submit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00083 | $0.01031 |
| Opus 5.5 | $0.00033 | $0.00412 |
| Sonnet 5.5 | $0.00017 | $0.00206 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
awesome-azd-template-submit 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Awesome AZD Template Submission
You submit azd templates to the awesome-azd gallery by filing a GitHub issue that triggers the automated submission pipeline. Given a repository URL, you create the issue — everything else is auto-detected from the repository.
Usage
The user provides a repository URL. That's it.
Submit this template: https://github.com/Azure-Samples/my-ai-app
Steps
1. Validate the URL
Confirm the URL points to a valid GitHub repository
(https://github.com/{owner}/{repo}). If the URL is malformed or missing, ask
the user to provide one.
2. Extract the repo name for the issue title
Parse {owner}/{repo} from the URL to use in the issue title.
3. Confirm with the user
Show the user the issue title and source URL. This is a write operation —
require explicit approval before executing gh issue create.
4. File the issue
Use the GitHub CLI to create an issue in the Azure/awesome-azd repository.
The issue body must use ### Heading format matching the issue form fields so
the automated parser can extract the values.
Only the Source Repository field is required. All other fields are auto-detected by the pipeline. Do NOT fill in optional fields unless the user explicitly provides overrides.
For author attribution, use the source repository owner as the default author. Use their GitHub profile as the author URL unless the submitter explicitly declares a different author URL.
gh issue create \
--repo Azure/awesome-azd \
--title "[Template]: {repo-name}" \
--body "### Source Repository
{url}
### Template Title
_No response_
### Description
_No response_
### Author
_No response_
### Author URL
_No response_
### Author Type
_No response_
### Trusted Author
_No response_
### Preview Image URL
_No response_
### IaC Provider
_No response_
### Languages
_No response_
### Frameworks
_No response_
### Azure Services
_No response_
### Additional Information
_No response_"
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.
- 12d ago Changed · +13 lines fa8a3e9c5f25
- 1mo ago Changed · +10 lines · +11 tokens per session 1a109acc4b4e
- 1mo ago First seen · 149 lines · 72 tokens per session scan A 3b606da809e1
awesome-azd-template-submit is a skill published in the GitHub repository Azure/awesome-azd (273 stars, last pushed 4d ago), licensed MIT. It adds 83 tokens to every session and 1,031 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
cloud-security
Multi-cloud security assessment skill for AWS, Azure, and GCP. Use when performing cloud security audits, scanning for misconfigurations, testing IAM policies, auditing storage permissions, and identifying privilege escalation paths. Triggers on requests to audit cloud security, scan AWS/Azure/GCP, check cloud…
azure-cli
A command-line tool for managing Microsoft Azure, Microsoft's cloud platform, from a terminal. It covers account sign-in, subscriptions, resource groups, virtual machines, and other cloud resources.
aws-cli
CLI-first AWS orchestration skill for Lambda, ECS/Fargate, and S3 workflows rooted in .☁️ runbooks.
analyzing-azure-activity-logs-for-threats
Queries Azure Monitor activity logs and sign-in logs via azure-monitor-query to detect suspicious administrative operations, impossible travel, privilege escalation, and resource modifications. Builds KQL queries for threat hunting in Azure environments. Use when investigating suspicious Azure tenant activity or…
azure-resource-manager-durabletask-dotnet
Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: "Durable Task Scheduler", "create scheduler", "task hub", "DurableTaskSchedulerResource", "provision…
azure-mgmt-fabric-dotnet
Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: "Fabric capacity", "create capacity", "suspend capacity", "resume capacity"…