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.00072 | $0.00810 |
| Opus 5 | $0.00036 | $0.00405 |
| Sonnet 5 | $0.00014 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
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 11d 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 — 149 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.
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_"
5. Confirm success
After filing, report the issue URL and explain that:
- A maintainer will review and add the
template-submissionlabel to trigger processing - The pipeline auto-extracts metadata, validates the repo, and creates a PR
- The user will be notified on the issue when the PR is ready for review
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.
- 11d 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 (269 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 810 once invoked, about $0.0004 per session on Opus 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
bedrock-agentcore
Deploy and operate agents on Amazon Bedrock AgentCore — Runtime, Harness, Memory, Identity, and Observability. Use when hosting an agent on AWS, containerising an agent for AgentCore Runtime, wiring session or long-term memory, or choosing between Harness, Runtime, and plain Lambda.
mcp-server-hosting
Build and host a remote MCP server on AWS — Lambda, Fargate/ECS, or AgentCore Runtime — with OAuth via Cognito, Okta, or Auth0 and the RFC 7235 401 + WWW-Authenticate handshake. Use when deploying an MCP server for remote agents rather than local stdio use.
expo-dev-client
Custom development builds with expo-dev-client, build profiles, a custom dev menu, runtime-version compatibility, and EAS Update integration. Triggers on expo-dev-client, dev client, custom dev build, development build, dev menu, expo go, runtime version, debug build, dev launcher, scan qr, dev server.
expo-eas-build
A guide to profile discipline, credentials management, and the build process for EAS Build. Scoped to eas.json configuration, iOS provisioning + push cert, Android keystore + service account, secrets, and monorepo support. Store-submit DETAIL lives in expo-eas-submit.
expo-eas-update
Publishing OTA updates with EAS Update, channels, runtime versions, branch management, and rollback strategy. Triggers on eas update, ota, over-the-air, runtime version, channel, branch, rollback, embedded update, asset selection, expo-updates, hot update, partial release, release cohort.
terraform-modules
Design and implement reusable Terraform modules with proper interfaces, testing, and documentation. Use when creating or refactoring infrastructure modules.