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 skills add cbrock84/headcount --skill business-continuity-and-resiliencegit 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/business-continuity-and-resilience)<a href="https://agentmods.dev/skills/cbrock84/headcount/business-continuity-and-resilience"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/business-continuity-and-resilience/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/cbrock84/headcount/business-continuity-and-resilience"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/business-continuity-and-resilience.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00069 | $0.00805 |
| Opus 5 | $0.00034 | $0.00402 |
| Sonnet 5 | $0.00014 | $0.00161 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
business-continuity-and-resilience 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business continuity and resilience
Continuity is a business question wearing technical clothing. The technical restore is covered by
it-operations:backup-and-recovery; this is about which processes must keep running, for whom, and
how long you can survive without them.
Start with impact, not systems
A business impact analysis asks, per process: what breaks downstream, how fast, and who notices. Work outward from the customer-visible failure, not inward from the asset register — an inventory of systems tells you what you own, never what matters.
For each critical process establish:
- Maximum tolerable outage — the point past which the damage is not recoverable by working harder afterwards. This is a business judgment, made by the process owner, not by IT.
- RTO — how quickly it must be back. Always shorter than someone wants to pay for.
- RPO — how much data you can afford to lose, measured in time. An RPO of zero is a claim about spending, not about intent.
RTO and RPO that were not signed by the person accountable for the process are aspirations.
Plans people can follow badly
A continuity plan is read by a stressed person at 03:00 who did not write it. Optimize for that reader: named roles rather than names, decision authority stated explicitly, and the first three actions on the first page.
Include what to do when the plan's assumptions fail — the alternate site is also affected, the key person is unreachable, the supplier is not answering. Plans that only handle the anticipated failure handle almost nothing.
Exercises
Untested plans are documents, not capabilities. Escalate the rigour:
- Walkthrough — read it aloud together and find the steps nobody can actually perform.
- Tabletop — inject a scenario and make the decisions under time pressure.
- Live failover — actually run on the alternate path, in production, with the real people.
The exercise produces findings or it was theater. Track them as work with owners and dates, and re-run the scenario that failed rather than a fresh one, so improvement is demonstrable.
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 · 75 lines · 69 tokens per session scan A 263d55feeb90
business-continuity-and-resilience is a skill published in the GitHub repository cbrock84/headcount (1,351 stars, last pushed 8d ago), licensed MIT. It adds 69 tokens to every session and 805 once invoked, about $0.0003 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
companion-clis
Companion CLIs for Runpod workflows — HuggingFace, GitHub, Docker, and AWS.
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.