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 events-and-field-marketinggit 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/events-and-field-marketing)<a href="https://agentmods.dev/skills/cbrock84/headcount/events-and-field-marketing"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/events-and-field-marketing/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/events-and-field-marketing"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/events-and-field-marketing.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.00065 | $0.00888 |
| Opus 5.5 | $0.00026 | $0.00355 |
| Sonnet 5.5 | $0.00013 | $0.00178 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
events-and-field-marketing 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Events and field marketing
Events are the most expensive marketing channel per contact and the easiest to spend badly on, because the outputs — booth traffic, badge scans, attendance — feel like results and are not.
Decide before you sponsor
The question is never "should we be at this event" but "what specifically do we expect, and what is that worth." Answer three things first:
- Who is actually there. Attendee seniority and function, not the headline number. A ten-thousand-person event where forty of your buyers attend is a forty-person event.
- What the goal is, and pick one: pipeline from new accounts, advancing deals already open, customer retention and advocacy, or category presence. These need different booths, different staff, and different follow-up, and an event asked to do all four does none.
- Total cost. Sponsorship is often under half. Add booth build, shipping, travel, staff time out of the field, and the content produced for it. The fully loaded figure changes decisions.
Small, self-hosted, targeted formats — a dinner for fifteen right accounts, a focused workshop — routinely outperform large sponsorships per dollar for enterprise pipeline, and are unglamorous enough that they get proposed rarely.
Follow-up is where the money is lost
Most event spend is wasted after the event, not during it. A scanned badge is not a lead, and the value decays in days.
Agree before the event: who follows up, in what timeframe, with what message, and how those contacts
are treated differently from inbound. Route it through revenue:revenue-operations so the tracking
exists in advance, and hand the sequence to demand-generation:lifecycle-messaging.
Score contacts honestly. Everyone who took a branded item is not a lead, and passing them to sales as if they were is how sales stops working the source at all.
Webinars and digital formats
Same discipline, different economics. Registration is not attendance and attendance is not interest; the segment worth pursuing is people who stayed and asked something.
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 b6a1bfffa57d
- 2mo ago First seen · 76 lines · 65 tokens per session scan A 68e4ff55dd8e
events-and-field-marketing is a skill published in the GitHub repository cbrock84/headcount (2,574 stars, last pushed 19d ago), licensed MIT. It adds 65 tokens to every session and 888 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-09-03.
events-and-field-marketing compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| events-and-field-marketingcbrock84/headcount | Skill | 2.6k | 19d ago | MIT | A | 65 | Claude Code |
| dnsproyecto26/system-design-skills | Skill | 123 | 10d ago | MIT | A | 131 | Claude Code |
| distributed-searchproyecto26/system-design-skills | Skill | 123 | 10d ago | MIT | A | 117 | Claude Code |
| sharded-countersproyecto26/system-design-skills | Skill | 123 | 10d ago | MIT | A | 106 | Claude Code |
| launch-google-searchmarkifact/markifact-mcp | Skill | 57 | 8d ago | MIT | A | 56 | Claude Code |
| negative-keyword-sweepmarkifact/markifact-mcp | Skill | 57 | 8d ago | MIT | A | 56 | Claude Code |
| rotate-creativemarkifact/markifact-mcp | Skill | 57 | 8d ago | MIT | A | 57 | Claude Code |