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 customer-onboarding-and-implementationgit 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/customer-onboarding-and-implementation)<a href="https://agentmods.dev/skills/cbrock84/headcount/customer-onboarding-and-implementation"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/customer-onboarding-and-implementation/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/customer-onboarding-and-implementation"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/customer-onboarding-and-implementation.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.00094 | $0.00752 |
| Opus 5 | $0.00047 | $0.00376 |
| Sonnet 5 | $0.00019 | $0.00150 |
| Haiku 4.5 | $0.00009 | $0.00075 |
Grade A, and why
customer-onboarding-and-implementation 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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer onboarding and implementation
The period between signature and first real use is where the largest share of preventable churn is created, and where a customer's opinion of the product is formed permanently.
Agree what live means before the contract is signed
The most common implementation failure happens in the sales cycle: nobody wrote down what success would look like, so the project has no finish line and every party quietly holds a different one.
Define the go-live criteria concretely — which teams, doing what, with what data in place — along with the date, who does what on each side, and what the customer must supply. Put it in the contract or an agreed plan before the deal closes, not after.
Sales commitments become implementation scope. If a deal was won on something the product does not do yet, the implementation team inherits it. Route that decision back to whoever can make it rather than absorbing it silently.
Plan the implementation as a project with a customer-side owner
Nothing predicts implementation failure like the absence of a named, empowered owner on the customer side. They need authority to make decisions and time genuinely allocated. If the customer cannot name that person, the project is at risk before it starts, and saying so early is a service.
Set a cadence from the beginning and hold it — a stalled implementation almost never announces itself; the calls quietly stop being attended.
Sequence for early value, not for completeness
Get one team doing one useful thing quickly, then widen. A phased approach produces a customer who has seen the product work, which changes every subsequent conversation.
The alternative — configure everything, migrate everything, launch to everyone — pushes all the value past a long window during which nothing works and the sponsor is defending the purchase.
Data and integrations are where the time actually goes
Both are routinely under-scoped because both depend on the customer's environment rather than
yours. Profile their data early; expect it to be worse than described. For the mechanics of moving
it, technology:data-migration covers the discipline.
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.
- 5d ago First seen · 71 lines · 94 tokens per session scan A 47ceb9b762dc
customer-onboarding-and-implementation is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 5d ago), licensed MIT. It adds 94 tokens to every session and 752 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
user-story-map
Build an interactive, drag-and-drop user story map so the user can re-slice work across release phases. Use when the user wants a story map, a phased roadmap, release slicing, a backbone/activities journey map, or to decide "which stories go in which phase" and move them around.
agile-ledger
Plain-Markdown Scrum / Agile product-management system for Claude Code. Manage a product backlog of Epics and User Stories, plan and run sprints, drive a board, track velocity, cut Major.Minor releases, and keep GitHub branches/commits/PRs traceable to stories — all from slash commands, with no Jira and no database.…
agile-ledger-workspace
Optional multi-repo orchestrator for Agile-Ledger. Install once at a workspace root to manage many repositories at once: discover new repositories on a GitHub org (including ones nobody told you about), clone and bootstrap them, run a single cross-repo "what changed while I was away" sync, and reconstruct undocumented…
people-integration
Design the first 90 days for acquired product talent so they stay, contribute, and feel ownership. Produces decision map session template, mentor pairing matrix, 30/60/90 ownership plan, retention risk review (purpose and influence), and 1:1 coaching question library.
roadmap-convergence
Facilitate the post-acquisition roadmap convergence process across Weeks 1 to 8. Produces the conflict log, three-session facilitation guides, merged 90-day plus 12-month roadmap, and the 30/60/90 execution plan.
week-0-readiness
Run a product leader through pre-close (Week 0) integration readiness for an acquisition. Produces the integration lead charter, decision rights one-pager, combined product narrative draft, customer commitment inventory, and the five-question Day 1 readiness check.