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 scaleway-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/scaleway-naming-tagging)<a href="https://agentmods.dev/skills/niels-emmer/myace/scaleway-naming-tagging"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/scaleway-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/scaleway-naming-tagging"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/scaleway-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.00038 | $0.01173 |
| Opus 5.5 | $0.00015 | $0.00469 |
| Sonnet 5.5 | $0.00008 | $0.00235 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
Scaleway 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Give every Scaleway 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
Scaleway-specific companion to iac-expert's generic resource-naming skill:
it keeps the same segment structure and adds the Scaleway-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 Scaleway 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 Scaleway 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 Scaleway examples:
instance(Compute instance),vpc(VPC/private network),sg(security group),bucket(Object Storage bucket),db(Managed Database),lb(load balancer),k8s(Kubernetes cluster),fn(Serverless Function),container(Serverless Container),iam(IAM policy/application),nat(NAT gateway). - 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.
fr-par,nl-ams,pl-waw). Omit only if the resource is genuinely global/region-less (e.g. IAM, DNS). - 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 · 95 lines · 38 tokens per session scan A 2570687044d4
Scaleway Naming And Tagging is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 1,173 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
corp-new
A workflow for creating a new department folder inside a local agent headquarters, with its own rules, skills, tasks, and links back to the headquarters.
manager
A session-to-GitHub tracker that creates, updates, and reads issues across repositories, including their labels, parent epics, and project-board placement.
corp-doctor
A guided maintenance and setup tool for a Personal Corp system, meaning a business workflow built from AI agents, department repositories, and shared rules. It checks what exists before making changes.
gh-issues
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq…
retro
A structured weekly retrospective for a department. It reviews tasks and evidence from an ISO calendar week, then records findings and the next planning goal.
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).