cloud-administration

cloud-administration is a skill for Claude Code, Codex from cbrock84/headcount. It costs 100 tokens per session (1,151 once invoked), scanned A, original, MIT.

A guide to managing the cloud services a company uses internally, including accounts, subscriptions, software services, access, ownership, and spending. It distinguishes this from the infrastructure used to build and run a product.

In plain words
What is it for?
Use it to organize tenants and subscriptions, assign owners and cost centres, manage access, control SaaS applications, and review provider responsibilities.
Why use it?
It helps replace untracked tools, unclear ownership, uncontrolled access, and surprise cloud bills with a structured company-wide setup.

Skill for Claude CodeCodex

Part of the it-operations plugin — 12 skills shipped together

About the project

headcount is an organization of independently installable Claude Code plugins, each grouping skills for a department such as finance, security, or demand generation. Claude Code users install the departments they need and invoke their skills for specialized work; the catalogue entries are skills and related agent tooling from that organization.

cbrock84/headcount · 1,247 stars · on GitHub · cbrock84.github.io

Install

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.

agentmods
npx agentmods add skills/cbrock84/headcount/cloud-administration
Any agent
npx skills add cbrock84/headcount --skill cloud-administration
Clone the repo
git clone --depth 1 https://github.com/cbrock84/headcount

Made for: Claude Code, Codex.

Or install it-operations, the plugin that ships this one along with the rest of its 12 skills.

Wrote 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.

agentmods badge for cloud-administration

README.md
[![agentmods](https://agentmods.dev/badge/skills/cbrock84/headcount/cloud-administration.svg)](https://agentmods.dev/skills/cbrock84/headcount/cloud-administration)
Your own site
<a href="https://agentmods.dev/skills/cbrock84/headcount/cloud-administration"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/cloud-administration.svg" alt="Measured on agentmods" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,151 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00100 $0.01151
Opus 5 $0.00050 $0.00575
Sonnet 5 $0.00020 $0.00230
Haiku 4.5 $0.00010 $0.00115

Measured yesterday against content hash 9153df81fee6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

cloud-administration 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 yesterday.

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.

plugins/it-operations/skills/cloud-administration/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cloud administration

Corporate cloud is bought, not architected. Someone needed a tool, expensed it, and it entered the estate without a review, an owner, or an offboarding path. The characteristic failure is not a bad design — it is discovering the estate years later, one invoice at a time.

This is the cloud the business runs on. For the cloud a product is built on — environments, infrastructure as code, scaling, region failure — see technology:cloud-infrastructure. The two follow different rules and the boundary is worth keeping sharp.

Structure the tenant before you need to

Subscription and account structure encodes what you can later separate: billing, access, policy, and blast radius. Retrofitting it means moving live workloads, so the cheap moment is the first one.

A workable default is to separate by what you would want to bill, govern, or lose independently — production corporate services, non-production, and anything with a distinct compliance obligation. Resist a subscription per team; teams reorganize, and the structure outlives them.

Tag at creation with owner, cost center, and environment, and enforce it with policy rather than documentation. Untagged resources become unattributable spend within a quarter, and nobody volunteers to claim them.

The SaaS estate is the part nobody is managing

Most companies underestimate their application count by a wide margin, because the ones they know about were bought by IT and the rest were bought by everyone else. The discovery methods that actually work are financial, not technical: expense reports, corporate card statements, and the identity provider's sign-in logs. Network monitoring finds less than the accounting system does.

Every application needs a named business owner, a renewal date, and a data classification. Without the owner there is nobody to ask at renewal. Without the renewal date the negotiation happens after auto-renewal. Without the classification, nobody knows which breach notification obligations apply when the vendor is compromised.

Read the full file on GitHub · 102 lines

Changes

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.

  1. yesterday First seen · 102 lines · 100 tokens per session scan A 9153df81fee6

Subscribe to this mod's changes

cloud-administration is a skill published in the GitHub repository cbrock84/headcount (1,247 stars, last pushed 2d ago), licensed MIT. It adds 100 tokens to every session and 1,151 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

cloud-deployment-routing-workflow

Choose a cloud deployment path before implementation. Route AWS work to the official AWS Agent Toolkit and Azure work to Microsoft's Azure Skills plugin while keeping credentials, regions, and mutation boundaries explicit.

gaelic-ghost/socket · 43 tokens

blob-store

This skill should be used when the user wants a "blob store" or "object storage", names "S3" or an S3-compatible store, needs to "store images / video / files", asks about "multipart upload" or "resumable upload", "signed / presigned URLs", "media storage", "unstructured data at scale", object "versioning", storage…

proyecto26/system-design-skills · 147 tokens

dns

This skill should be used when the user asks about "DNS", "domain resolution", "GeoDNS / geo routing", "latency-based routing", "weighted / failover routing", "Route 53 / Cloud DNS", an "A/CNAME/ALIAS record", "anycast", or "DNS TTL / propagation". It gives the global front door that maps a name to the right IP and…

proyecto26/system-design-skills · 131 tokens

macos-distribution-workflow

Inspect, prepare, validate, and troubleshoot exported macOS distribution artifacts. Use when checking signing identities, entitlements, hardened runtime, nested code, Gatekeeper, notarization readiness/results, stapling, or distribution-only launch failures.

gaelic-ghost/socket · 53 tokens

prepare-isolated-analysis-lab

Prepare a verified disposable Linux or macOS analysis lab from an approved isolation decision. Use before active research to control host integration, networking, baseline, monitoring, evidence export, reset, and teardown.

gaelic-ghost/socket · 46 tokens

flash

Write code locally, iterate with flash dev — it runs your functions on remote Runpod GPUs/CPUs with hot-reload and live worker logs — then flash deploy to ship. Endpoint handles provisioning.

gaelic-ghost/socket · 23 tokens