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 niels-emmer/myace --skill azure-naming-tagginggit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/azure-naming-tagging)<a href="https://agentmods.dev/skills/niels-emmer/myace/azure-naming-tagging"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/azure-naming-tagging/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/niels-emmer/myace/azure-naming-tagging"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/azure-naming-tagging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00037 | $0.01163 |
| Opus 5.5 | $0.00015 | $0.00465 |
| Sonnet 5.5 | $0.00007 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
Azure Naming And Tagging 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- GCP Naming And Labeling — 91% identical, 74 lines differ
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Give every Azure resource a name and a set of tags that let anyone — not just
the person who created it — answer "what is this, who owns it, what does it
cost, and can we turn it off" without asking around. This is the
Azure-specific companion to iac-expert's generic resource-naming skill:
it keeps the same segment structure and adds the Azure-specific abbreviations,
region codes, and character constraints that the generic skill can't name.
When to use it
Any time you're scaffolding a new Azure resource, renaming an existing one to bring it into line, or reviewing a plan/diff for naming and tagging consistency.
Naming convention
Compose resource names from fixed segments, in a fixed order, separated by a single consistent delimiter (hyphen is the safest default — many Azure resource types disallow underscores, dots, or uppercase):
<resource-type-abbreviation>-<workload>-<environment>-<region>[-<instance>]
- resource-type-abbreviation — a short, consistent code for what the
resource is. Pick one abbreviation per resource type and never vary it.
Common Azure examples:
vm(virtual machine),vnet(virtual network),nsg(network security group),st(storage account),kv(Key Vault),sql(SQL Database),app(App Service),func(Function App),aks(AKS cluster),rg(resource group),pip(public IP),nic(network interface). - workload — the application or system the resource belongs to, short and
stable (e.g.
billing,checkout,ingest). Usually the most important segment for grouping resources in cost/ownership views. - environment —
dev,test,stage,prod(or your project's fixed vocabulary — pick one set and don't let synonyms likeproduction/prd/prodcoexist). - region — a short code for the deployed region (e.g.
eusfor East US,weufor West Europe,uksfor UK South). Omit only if the resource is genuinely global/region-less. - instance (optional) — a numeric or short suffix when more than one of
the same resource exists in the same workload/environment/region (
-01,-02).
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.
- 1mo ago First seen · 94 lines · 37 tokens per session scan A a4a6e1af8e44
Azure Naming And Tagging is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,163 once invoked, about $0.0001 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-31.
Other skills, from other repositories
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations. Not for: a loom orchestration job or CI pipeline job — see loom-ci-cd.
loom-prometheus
Prometheus monitoring and alerting for cloud-native observability. Not for: a loom orchestration job or CI pipeline job — see loom-ci-cd.
ai-foundry-posture-check
Assess security, reliability, and cost posture of Azure OpenAI and Microsoft Foundry deployments. Detects critical anti-patterns: API keys instead of Managed Identity, public endpoints without firewall, disabled content filtering, missing diagnostic settings, deprecated model versions, over-provisioned PTU, absence of…
digital-native-governance-check
Assess Azure governance maturity for Digital Natives and startups. Detects the most common anti-patterns from the "Digital Natives on Azure" series: incomplete Service Health alerts, flat subscription topology without Management Groups, excessive RBAC (everyone is Owner), missing budget alerts, no Managed Identity…
well-architected-review
Run a Well-Architected Framework (WAF) review against Azure resources in scope. Use when asked about best practices, architecture review, WAF assessment, or pillar compliance (Reliability, Security, Cost, Operational Excellence, Performance Efficiency).
compliance-governance-audit
Audit Azure environment for compliance and governance posture. Checks Azure Policy, RBAC, tagging, resource locks, naming conventions, and regulatory alignment. Use when asked about compliance, governance, audit readiness, or policy violations.