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 procurement-and-sourcinggit 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/procurement-and-sourcing)<a href="https://agentmods.dev/skills/cbrock84/headcount/procurement-and-sourcing"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/procurement-and-sourcing/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/procurement-and-sourcing"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/procurement-and-sourcing.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.00062 | $0.00722 |
| Opus 5 | $0.00031 | $0.00361 |
| Sonnet 5 | $0.00012 | $0.00144 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
procurement-and-sourcing 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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Procurement and sourcing
This is everything before signature: deciding what to buy, from whom, and on what terms.
operations:vendor-management takes over afterward — performance, renewals, exit.
Specify the need, not the product
Most bad purchases are decided before any supplier is contacted, when a requirement is written as a product someone already wanted. Specify the outcome and the constraints; let suppliers propose how.
Separate genuine requirements from preferences, and be honest about which is which. A requirements list that only one supplier satisfies is a purchase order with extra steps, and everyone involved knows it.
Involve the people who will live with the choice. Procurement that optimizes price against a specification the users did not agree to produces a cheap thing nobody uses.
Competition is the leverage
Price is set by the credible presence of an alternative, not by negotiating skill. The single most effective act in sourcing is having a real second option — and being willing to take it.
Run a fair process: same information to every bidder, same questions answered for all, scoring agreed before responses arrive. Scoring invented afterward reliably rediscovers the preferred supplier.
Where genuine competition is impossible — an incumbent with switching costs, a sole source — acknowledge it rather than staging a process. Then negotiate on the things still open: term length, renewal caps, service levels, exit assistance.
Total cost, not price
The quoted figure is a fraction of what you will spend. Model implementation, integration, training, the internal effort to run it, and what leaving costs.
Watch for cost that arrives later by design: per-seat pricing that grows with headcount, usage pricing with no cap, renewal uplifts, and support tiers that turn out to be mandatory. Ask what this costs in year three, and get the answer in the contract.
Category strategy
Aggregate spend before negotiating it. The same category bought independently by four teams is four weak negotiating positions and usually four overlapping tools.
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.
- 4d ago First seen · 74 lines · 62 tokens per session scan A cd3c5e504c00
procurement-and-sourcing is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 5d ago), licensed MIT. It adds 62 tokens to every session and 722 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
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.