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 gcp-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/gcp-naming-tagging)<a href="https://agentmods.dev/skills/niels-emmer/myace/gcp-naming-tagging"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/gcp-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/gcp-naming-tagging"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/gcp-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.00036 | $0.01200 |
| Opus 5 | $0.00018 | $0.00600 |
| Sonnet 5 | $0.00007 | $0.00240 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
GCP Naming And Labeling 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 8d 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.
This is a copy
91% identical to Azure Naming And Tagging — 74 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Give every GCP resource a name and a set of labels 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 GCP-specific
companion to iac-expert's generic resource-naming skill: it keeps the same
segment structure and adds the GCP-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 GCP resource, renaming an existing one to bring it into line, or reviewing a plan/diff for naming and labeling 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 GCP 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 GCP examples:
vm(Compute Engine instance),vpc(VPC network),fw(firewall rule),gcs(Cloud Storage bucket),sql(Cloud SQL instance),lb(load balancer),gke(GKE cluster),bq(BigQuery dataset),sa(service account),nat(Cloud NAT),psc(Private Service Connect endpoint). - 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.
us-central1,europe-west1,asia-southeast1). Omit only if the resource is genuinely global/region-less (e.g. IAM, Cloud DNS, some load balancers). - 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.
- 8d ago First seen · 96 lines · 36 tokens per session scan A 788ffc356f2c
GCP Naming And Labeling is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 1,200 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to Azure Naming And Tagging, differing in 74 lines, and is treated as a copy.
Other skills, from other repositories
implementing-gcp-organization-policy-constraints
Implement GCP Organization Policy constraints to enforce security guardrails across the entire resource hierarchy, restricting risky configurations and ensuring compliance at organization, folder, and project levels.
weekly-retro
A structured weekly retrospective for a one-person business run with AI agents. It gathers evidence from code, project tools, and canonical business files, then records findings and outcomes.
idea
Use when capturing ONE new idea the user voices and wants recorded — "save this idea", "I have an idea", "log this idea", "/idea", "idea: ...". Creates a provenance-tracked folder (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a GitHub Project view filtered by label:idea. NOT…
meeting-copilot
Use when preparing for, running, or closing a live meeting with an AI assistant dashboard. Triggers on "meeting copilot", "live copilot", "prepare for a call", "update copilot", "close the session", or requests to turn transcript chunks into meeting questions, topic maps, decisions, and follow-ups.
daily
A daily-planning workflow that reports the current department’s active work and refreshes its weekly plan. It uses the department’s defined task source and follows the project’s local instructions.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.