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 supply-chain-and-logisticsgit 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/supply-chain-and-logistics)<a href="https://agentmods.dev/skills/cbrock84/headcount/supply-chain-and-logistics"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/supply-chain-and-logistics/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/supply-chain-and-logistics"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/supply-chain-and-logistics.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.00583 |
| Opus 5 | $0.00032 | $0.00292 |
| Sonnet 5 | $0.00013 | $0.00117 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
supply-chain-and-logistics 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 6d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supply chain and logistics
Supply chains fail at variability, not at averages. A chain planned on average demand and average lead time will disappoint at both ends: stockouts when either runs long, dead stock when they do not.
Inventory is a bet on uncertainty
Safety stock exists to absorb variation in demand and in lead time. Sizing it needs both the average and the spread — a supplier averaging 20 days at ±2 is a different proposition from one averaging 20 days at ±15, and treating them the same guarantees you are wrong about one.
Set reorder points on lead-time demand plus safety stock, and revisit them when either input moves. A reorder point set once is a reorder point that is now wrong.
Hold inventory where it is most flexible. Stock held as components serves several finished configurations; the same value held as finished goods serves one and obsoletes faster.
Lead time is a distribution
Quoted lead time is a marketing number. Plan against your own measured receipt dates, including the bad months. Track the variance explicitly — reliability of lead time usually matters more than its length, because a long predictable lead time can be planned around and a short erratic one cannot.
Concentration is the risk that actually bites
Map dependencies past the first tier. Two suppliers on paper who share a single sub-supplier, a single port, or a single region are one supplier with extra paperwork.
For each critical input know: who else could supply it, how long qualifying them takes, and whether anything in the design makes switching hard. That answer is worth having before you need it — qualifying an alternate under pressure is where quality problems enter.
Supplier commercial terms and exit rights belong with operations:vendor-management; continuity of
the wider business process belongs with operations:business-continuity-and-resilience.
Fulfillment reliability
Measure on-time-in-full, not on-time and in-full separately — partial shipments that arrive on schedule are a way of appearing to hit a target while failing the customer.
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.
- 6d ago First seen · 55 lines · 65 tokens per session scan A 30ecf4b671f6
supply-chain-and-logistics is a skill published in the GitHub repository cbrock84/headcount (1,335 stars, last pushed 7d ago), licensed MIT. It adds 65 tokens to every session and 583 once invoked, about $0.0003 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
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.
mode
Show or set NeatContext routing to auto, ask, or manual for Codex, with an optional default shared with every other NeatContext host. Use only when the user explicitly invokes this skill or clearly asks to change routing behavior.
status
Report the NeatContext context and routing mode active in Codex, including missing-file or stale-routing warnings. Use when the user asks which context is connected or explicitly invokes this skill.
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.
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…