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/payroll-operationsnpx skills add cbrock84/headcount --skill payroll-operationsgit 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/payroll-operations)<a href="https://agentmods.dev/skills/cbrock84/headcount/payroll-operations"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/payroll-operations.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.1 | $0.00104 | $0.00844 |
| Opus 5 | $0.00052 | $0.00422 |
| Sonnet 5 | $0.00021 | $0.00169 |
| Haiku 4.5 | $0.00010 | $0.00084 |
Grade A, and why
payroll-operations 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 2d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Payroll operations
Payroll is the process with the least tolerance for error and the least visibility until it breaks. Nobody notices it working; everybody notices a late or wrong payment, and trust recovers slowly.
Payroll tax registration, withholding and filing obligations vary by jurisdiction and change frequently. Get a qualified adviser or a provider who takes filing responsibility, and confirm where liability actually sits.
The calendar is the control
Work backwards from the pay date: funding date, approval, processing cutoff, time-entry deadline, change deadline. Publish it, and treat the change deadline as real — the alternative is a correction cycle running permanently alongside the pay cycle.
Bank holidays, month-end, and year-end all move cutoffs. A calendar that was right in January quietly stops being right, and the first sign is a late funding.
Know what feeds pay, and make the HRIS the source
Every input is a place errors enter: new hires and terminations, pay changes, hours from time systems, commissions and bonuses, expense reimbursements, benefit deductions, garnishments.
The failure that produces most wrong payments is two systems disagreeing about someone's status — a leaver still active in payroll, a pay change entered in one place. Identity, employment status, and pay data should originate in one system and flow outward. Where a feed is manual, it needs a reconciliation, not a reminder.
Gross to net, and what sits between
Gross pay, pre-tax deductions, taxable wages, withholding, post-tax deductions, net. Understanding the order matters because it determines what a change actually costs and why a raise produces a smaller increase than expected.
Employer cost is not gross pay. Employer taxes, benefit contributions, and mandated insurances sit on top, and a hiring plan built on salary alone understates cost materially.
Garnishments and support orders have legal priority and limits on how much can be taken. They are one of the few payroll items where getting it wrong exposes the employer directly.
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.
- 2d ago First seen · 76 lines · 104 tokens per session scan A 64033fcf8def
payroll-operations is a skill published in the GitHub repository cbrock84/headcount (1,247 stars, last pushed 3d ago), licensed MIT. It adds 104 tokens to every session and 844 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
stockbit-auth
Log in to Stockbit and capture the session for this server — opens the browser login flow and verifies the token was stored. Use when the user asks to log in or re-authenticate to Stockbit, or after a status check reports the session expired, HTTP 401, or logged out.
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.
morning-scan
The pre-open and first-hour routine for IDX — session state, movers, a scan over a universe, and a catalyst check on the leaders. Use when the user asks what is moving today, for a morning briefing, or what to watch.
list
List the local NeatContext Contexts available to Codex. Use when the user asks what contexts exist, what can be connected, or explicitly invokes this skill.
build-oxpecker-web-app
Build or modify an Oxpecker web application in idiomatic F#, using endpoint routing, functional EndpointHandler and EndpointMiddleware composition, ASP.NET Core metadata, and focused endpoint tests.
swiftui-app-architecture-workflow
Guide SwiftUI app-structure decisions for Apple apps across App, scenes, commands, focus, environment, preferences, window and document coordination, and reusable view composition. Use when the user wants help deciding where ownership belongs in a SwiftUI app, which data-flow mechanism fits a responsibility, or how to…