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/collaboration-platform-administrationnpx skills add cbrock84/headcount --skill collaboration-platform-administrationgit 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/collaboration-platform-administration)<a href="https://agentmods.dev/skills/cbrock84/headcount/collaboration-platform-administration"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/collaboration-platform-administration.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.00093 | $0.00817 |
| Opus 5 | $0.00046 | $0.00409 |
| Sonnet 5 | $0.00019 | $0.00163 |
| Haiku 4.5 | $0.00009 | $0.00082 |
Grade A, and why
collaboration-platform-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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collaboration platform administration
This platform holds most of the organization's unstructured information and nearly all of its external communication. It is usually configured once during migration, by whoever ran the migration, and then never revisited.
Get mail authentication right, and keep it right
SPF, DKIM and DMARC together determine whether your mail is delivered and whether someone else can send as you. All three need to exist and agree.
- SPF breaks quietly as third-party senders accumulate — marketing platforms, ticketing systems, invoicing tools — and has a hard limit on lookups that a growing list eventually crosses.
- DKIM has to be enabled per sending domain and per service, not once for the tenant.
- DMARC starts in monitoring and only protects once it moves to enforcement. A policy left at none for two years is a report nobody reads.
Every new tool that sends mail on your behalf is a change to this configuration. Route that through the same process as any other change, or the first sign will be a customer saying your invoices go to spam.
Phishing controls are configuration, not awareness training
External sender warnings, impersonation and lookalike-domain protection, attachment and link inspection, and blocking auto-forwarding to external addresses are settings. Auto-forward rules in particular are the classic account-compromise persistence mechanism, and the account owner will not notice.
Alert on inbox rule creation that forwards or deletes. It is one of the highest-signal detections available and it comes free with the platform.
Shared mailboxes, groups and the identities nobody owns
Shared mailboxes, distribution lists and team channels accumulate faster than anything else in the tenant and are never cleaned up. Each needs a named owner and a review date, because a distribution list nobody owns eventually mails the whole company by accident, and a shared mailbox with stale access is a standing data exposure.
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 · 76 lines · 93 tokens per session scan A 8b179a799b1c
collaboration-platform-administration is a skill published in the GitHub repository cbrock84/headcount (1,247 stars, last pushed 2d ago), licensed MIT. It adds 93 tokens to every session and 817 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.
Other skills, from other repositories
structure-swift-sources
Organize Swift source trees and oversized Swift files by feature, layer, and declaration group; split large files, normalize // MARK: sections, enforce plain-language block-comment file headers, and move TODO and FIXME text into ledger files. Use after format-swift-sources has established a clean formatting baseline.
tips-helpviewer-workflow
Discover local user-guide topics for installed Apple Mac apps through the Tips HelpViewer catalog, with app matching, installed-version capture, result verification, and authoritative fallback routing. Use when Codex needs task-specific help for an installed Apple app, needs to find a menu command through local Help…
coaching-mode
Use when the user wants to coach someone — a report, peer, or mentee — through a problem rather than solve it for them. Trigger phrases include "coach me through how to talk to [report]", "I want to help [name] figure out X without telling them what to do", "let me practice a coaching conversation", "GROW conversation…
manage-glue-workers
Use when managing engineers who naturally gravitate toward glue work (onboarding, documentation, unblocking, process improvement) and need protection from burnout, visibility for their impact, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how…
user-profile
Use to create or update the user's anchor profile — a single private file (/bettersense-work-reflections/profile.md) that captures who the user is, what they do, what context other skills need to know about them. Read automatically by other skills in the bundle when present, so the user doesn't re-explain themselves…
workload-equity
Use when the user wants to analyze whether non-promotable (glue) work is fairly distributed across their team, with attention to demographic and seniority patterns. Trigger phrases include "is our glue work fair", "who does the non-promotable work on our team", "audit workload distribution", "are women doing more glue…