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 resource-naminggit 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/resource-naming)<a href="https://agentmods.dev/skills/niels-emmer/myace/resource-naming"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/resource-naming/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/resource-naming"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/resource-naming.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.00967 |
| Opus 5 | $0.00018 | $0.00483 |
| Sonnet 5 | $0.00007 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
Resource 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 9d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Give every 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 having to ask around. This is the concrete template behind the "Consistent Naming And Tagging" rule.
When to use it
Any time you're scaffolding a new 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 — some resource types don't allow underscores or dots):
<resource-type-abbreviation>-<workload>-<environment>-<region>[-<instance>]
- resource-type-abbreviation — a short, consistent code for what the resource is (e.g.
vm,sql,stfor storage,kvfor a secret/key vault,funcfor a function app). Pick one abbreviation per resource type and never vary it. - workload — the application or system the resource belongs to, short and stable (e.g.
billing,checkout,ingest). This is usually the most important segment for grouping resources in cost/ownership views. - environment —
dev,test,stage,prod(or your project's equivalent set — pick one fixed vocabulary and don't let synonyms likeproduction/prd/prodcoexist). - region — a short code for the deployed region (provider-specific, e.g.
eusfor East US,weufor West Europe,use1for AWS us-east-1). 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).
Adjust casing and allowed characters to whatever the specific resource type permits (some cloud resource types disallow hyphens or force lowercase) — the segment order and content is what stays constant across providers and resource types, not the exact character set.
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.
- 9d ago First seen · 56 lines · 37 tokens per session scan A ed11053cd8e9
Resource Naming And Tagging is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 37 tokens to every session and 967 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations.
loom-prometheus
Prometheus monitoring and alerting for cloud-native observability.
loom-terraform
Infrastructure as Code with Terraform/OpenTofu.
loom-karpenter
Kubernetes node autoscaling and cost optimization with Karpenter.
vercel
Operate Next.js 16 SaaS on Vercel with Cloudflare DNS + Supabase. Use when deploying to Vercel, reducing build costs, managing secrets, or splitting traffic between Vercel and Cloudflare.
wrangler
Deploy and manage Cloudflare Workers, Pages, R2, D1, KV. Use when working with wrangler, Cloudflare Workers, or edge deployments.