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 lifecycle-messaginggit 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/lifecycle-messaging)<a href="https://agentmods.dev/skills/cbrock84/headcount/lifecycle-messaging"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/lifecycle-messaging/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/lifecycle-messaging"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/lifecycle-messaging.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.00071 | $0.01023 |
| Opus 5.5 | $0.00028 | $0.00409 |
| Sonnet 5.5 | $0.00014 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00102 |
Grade A, and why
lifecycle-messaging 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 1mo 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lifecycle messaging
Map the lifecycle before writing any message
For each stage, name what the person is trying to do and what would move them forward. Messages written without that answer become announcements, and announcements get unsubscribed from.
The stages that matter: just signed up, activated but not habitual, habitual, at risk, lapsed. Most programs over-invest in the first and neglect at-risk entirely, which is where the money is.
The welcome sequence
The highest-engagement messages you will ever send. Do not waste them on company history.
- Immediate — deliver whatever was promised, plus the single next action.
- Within days — the fastest route to first value, one step.
- After that — the use case most people miss, or the objection most people have.
Set expectations early: what you send, how often. It reduces unsubscribes more than any subject-line technique.
Timing and cadence
Trigger on behavior, not the calendar, wherever possible. A message sent because someone did something is many times more relevant than one sent because it is Tuesday.
Cadence sustainable at your worst week. Every message should be one the recipient would miss.
SMS is a different medium
Higher consent bar, higher intrusion, higher cost. Reserve it for time-sensitive and transactional messages — delivery, appointment, security, an expiring window. Marketing SMS at any volume trains people to opt out.
Explicit opt-in, honored opt-out, sending hours respected in the recipient's timezone. These are legal requirements in most jurisdictions, not preferences.
SMS compliance is not optional
Consult qualified counsel before launching an SMS program. The exposure here is statutory damages per message, which is how these become class actions.
In the US, marketing SMS requires express written consent obtained before sending — implied consent, an existing customer relationship, or a phone number collected for another purpose does not qualify. The consent record must show what the person agreed to receive and when, and it must be retained.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +7 lines e7d07d1e2a23
- 1mo ago Changed · +11 lines 6a6bd87c7eaf
- 1mo ago First seen · 86 lines · 71 tokens per session scan A e2adde9a93af
lifecycle-messaging is a skill published in the GitHub repository cbrock84/headcount (2,069 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,023 once invoked, about $0.0003 per session on Opus 5.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-08-30.
Other skills, from other repositories
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
rotate-creative
Pause fatigued ads and ship fresh creative variants in their place. Works on both Meta and Google Ads. Use when CTR is dropping, frequency is climbing, or the user says "creative is tired" / "let's refresh ads". Always starts new variants paused.
launch-google-search
Launch a complete Google Ads Search campaign — campaign, ad group, responsive search ads, keywords, sitelinks, callouts, and negatives — built paused and ready to review. Use when the user wants to spin up a new Search campaign on Google Ads.
go
Compatibility entry for Visual Stack's former /vstack:go command. Runs the wireframe and UI review tool, now called review. Use only when the user invokes /vstack:go.
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
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…