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 telephony-and-conferencinggit 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/telephony-and-conferencing)<a href="https://agentmods.dev/skills/cbrock84/headcount/telephony-and-conferencing"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/telephony-and-conferencing/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/telephony-and-conferencing"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/telephony-and-conferencing.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.00085 | $0.01000 |
| Opus 5 | $0.00043 | $0.00500 |
| Sonnet 5 | $0.00017 | $0.00200 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
telephony-and-conferencing 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 6d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telephony and conferencing
Voice is the service where failure is most visible and least tolerated. Nobody files a ticket when email is slow; everyone notices a dead phone, and customers notice first. It is also the service most likely to be nobody's stated job — inherited from a facilities vendor, half-migrated to a collaboration suite, with the parts that still work unowned.
Voice is an application on the network now, and behaves like one
A phone system is real-time traffic sharing a network built for everything else. That makes voice the first service to expose problems the network was hiding: jitter, packet loss, and asymmetric routing that a file transfer absorbs and a conversation does not.
Quality complaints are almost never about the phone system. Diagnose them as network problems on
the path, and prioritize voice traffic explicitly rather than assuming capacity is enough — a link
with headroom on average still queues at the moment someone is talking. See
it-operations:network-administration for the diagnosis order.
The corollary is that a network change can break voice without touching it, which is an argument for including voice in the change review rather than discovering it afterward.
Emergency calling is a legal obligation, not a feature
Emergency calls must reach the right dispatch center with a location accurate enough to send help to, and in most jurisdictions this is regulated rather than optional. Two requirements that routinely get missed: a caller must be able to dial emergency services directly without a prefix, and someone on site should be notified when such a call is placed.
Remote and hybrid work is what makes this hard. A softphone carries its number, not its location, so a home worker dialing for help may route to the office's dispatch center hundreds of miles away. Provider features exist to handle this and they require configuration and user prompting to work.
Treat location records as data that goes stale. Desk moves, new floors, and new home addresses all invalidate them, and nobody discovers the error at a good moment.
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.
- 6d ago First seen · 84 lines · 85 tokens per session scan A 1771e6b77cb5
telephony-and-conferencing is a skill published in the GitHub repository cbrock84/headcount (1,335 stars, last pushed 7d ago), licensed MIT. It adds 85 tokens to every session and 1,000 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
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.