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 ancoleman/ai-design-components --skill resource-tagginggit clone --depth 1 https://github.com/ancoleman/ai-design-componentsWrote 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/ancoleman/ai-design-components/resource-tagging)<a href="https://agentmods.dev/skills/ancoleman/ai-design-components/resource-tagging"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/resource-tagging.svg" alt="Measured on agentmods" 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.00048 | $0.03592 |
| Opus 5 | $0.00024 | $0.01796 |
| Sonnet 5 | $0.00010 | $0.00718 |
| Haiku 4.5 | $0.00005 | $0.00359 |
Grade A, and why
resource-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 7d 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 — 460 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resource Tagging
Apply comprehensive cloud resource tagging strategies to enable cost allocation, ownership tracking, compliance enforcement, and infrastructure automation across multi-cloud environments.
Purpose
Resource tagging provides the foundational metadata layer for cloud governance. Tags enable precise cost allocation (reducing unallocated spend by up to 80%), rapid ownership identification, compliance scope definition, and automated lifecycle management. Without proper tagging, cloud costs become untrackable, security incidents lack context, and automation policies fail to target resources effectively.
When to Use
Use resource tagging when:
- Implementing cloud governance frameworks for cost allocation and accountability
- Building FinOps practices requiring spend visibility by team, project, or department
- Enforcing compliance requirements (PCI, HIPAA, SOC2) through automated policies
- Setting up automated resource lifecycle management (backup, monitoring, shutdown)
- Managing multi-tenant or multi-project cloud environments
- Implementing disaster recovery and backup policies based on criticality
- Tracking resource ownership for security incident response
- Optimizing cloud costs through spend analysis and showback/chargeback
Minimum Viable Tagging Strategy
Start with the "Big Six" required tags for all cloud resources:
| Tag | Purpose | Example Value |
|---|---|---|
| Name | Human-readable identifier | prod-api-server-01 |
| Environment | Lifecycle stage | prod | staging | dev |
| Owner | Responsible team contact | [email protected] |
| CostCenter | Finance code for billing | CC-1234 |
| Project | Business initiative | ecommerce-platform |
| ManagedBy | Resource creation method | terraform | pulumi | manual |
Optional tags to add based on specific needs:
- Application: Multi-app projects requiring app-level isolation
- Component: Resource role (
web,api,database,cache) - Backup: Backup policy (
daily,weekly,none) - Compliance: Regulatory scope (
PCI,HIPAA,SOC2) - SLA: Service level (
critical,high,medium,low)
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/kubernetes/gatekeeper-constraints.yaml 5.5 KB
- examples/terraform/aws-required-tags.tf 7.4 KB
- examples/terraform/azure-tag-policies.tf 5.4 KB
- outputs.yaml 8.4 KB
- references/compliance-auditing.md 26 KB
- references/cost-allocation.md 22 KB
- references/enforcement-patterns.md 28 KB
- references/tag-taxonomy.md 19 KB
- scripts/audit_tags.py 12 KB runs code
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.
- 7d ago First seen · 460 lines · 48 tokens per session scan A cb3e2ef3f2fa
resource-tagging is a skill published in the GitHub repository ancoleman/ai-design-components (518 stars, last pushed 9mo ago), licensed MIT. It adds 48 tokens to every session and 3,592 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-08-30.
Other skills, from other repositories
cloudflare-api
Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide…
hono-api-scaffolder
Scaffold Hono API routes for Cloudflare Workers. Produces route files, middleware, typed bindings, Zod validation, error handling, and APIENDPOINTS.md documentation. Use after a project is set up with cloudflare-worker-builder or vite-flare-starter, when you need to add API routes, create endpoints, or generate API…
cloudflare-worker-builder
Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax…
runbook-generator
Generates comprehensive operational runbooks for any system or process. Reads codebase, infrastructure config, and deployment scripts to produce structured runbook.md files formatted for on-call engineers. Use when you need operations documentation, incident response guides, deployment procedures, or disaster recovery…
sre-bot
Answer questions about production health and investigate incidents using live Kubernetes and observability data. Invoke whenever someone asks whether something is broken, slow, erroring, or down; asks what happened during an outage or time window; asks about alerts, logs, metrics, traces, or error rates; asks why a…
dns-zonefile-config
Configurez correctement vos zones DNS pour l'email deliverability (SPF, DKIM, DMARC), la sécurité (DNSSEC, CAA), et l'automatisation (OVH API, Cloudflare, Terraform), basé sur les best practices 2024-2025. Use when: Configurer l'authentification email - SPF, DKIM, DMARC pour éviter le spam folder; Sécuriser un domaine…