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.
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 agentmods add skills/cbrock84/headcount/virtualization-operationsnpx skills add cbrock84/headcount --skill virtualization-operationsgit clone --depth 1 https://github.com/cbrock84/headcountWrote 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/cbrock84/headcount/virtualization-operations)<a href="https://agentmods.dev/skills/cbrock84/headcount/virtualization-operations"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/virtualization-operations.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 | $0.00086 | $0.01090 |
| Opus 5 | $0.00043 | $0.00545 |
| Sonnet 5 | $0.00017 | $0.00218 |
| Haiku 4.5 | $0.00009 | $0.00109 |
Grade A, and why
virtualization-operations 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Virtualization operations
Virtualization is the layer most infrastructure problems actually live in, and the one most monitoring is blind to. A guest reports healthy CPU while contending for a core it never gets. The usual failure is diagnosing upward — into the application — when the constraint is a host two layers below.
Consolidation ratio is a decision, not a result
Every cluster has a ratio of virtual resources to physical ones, and most organizations discover theirs rather than choosing it. Overcommitting memory and CPU is normal and correct; the question is how far, and what happens at peak rather than average.
Two numbers worth knowing at all times: what the cluster runs at now, and what it runs at when one host is gone. If losing a single host takes you past capacity, you have a cluster that survives hardware failure on paper and not in practice. Size for N-1 and keep the spare capacity visible in the budget, or the first thing cut is the headroom that makes the design work.
Memory is usually the real ceiling, not CPU. Cores oversubscribe gracefully; RAM does not.
Sprawl is a lifecycle problem wearing an infrastructure costume
VMs are trivially easy to create and socially difficult to delete. Nobody remembers what the box does, so it stays — consuming license, backup capacity, patching effort, and an attack surface nobody reviews.
The fix is ownership recorded at creation, not an annual cleanup. Every VM gets a named owner and a review date before it is built. Anything that cannot name an owner is a candidate for decommissioning, and the decommission path is: power off, wait a defined period, then delete. Powering off first turns an irreversible decision into a reversible one and produces the phone call that tells you what the machine did.
Templates and golden images keep the estate consistent. Builds that started from a template drift
less than builds someone assembled, and drift is what makes patching unpredictable — see
it-operations:systems-administration for the configuration baseline this feeds.
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.
- yesterday First seen · 90 lines · 86 tokens per session scan A 17922c0567dd
virtualization-operations is a skill published in the GitHub repository cbrock84/headcount (1,247 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 1,090 once invoked, about $0.0004 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
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.
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…
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…
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.
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.
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.