Attributed metadata history

headcount: 172 skills organized as a company org chart, now with a Chinese README

There is a specific kind of mess that shows up once you have more than about thirty prompts saved. You stop remembering what you have. Two prompts do nearly the same thing and you can't tell which one is current. You paste a whole "mega-prompt" into a session because you can't be bothered to find the right one, and half of it is irrelevant to the task. headcount is one answer to that. It arranges agent skills as a company: one chief executive, 16 departments, 172 skills. Each department installs as its own plugin, so a project loads only what it needs. Skills are addressed as department:skill, which means names never collide across departments. The original repository is cbrock84/headcount, 2047 stars, written in Markdown, MIT licensed. A Chinese translation of the README now exists at yangshun2005/headcount-cn. That's what this post is mostly about, because the translation does something a plain translation usually doesn't. What the project actually is The official one-liner: an agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs in Claude Code and ChatGPT. The README's own numbers are 16 departments and 172 skills. The one-liner says 15+ and 125+. Both appear in the source material; I'm not going to reconcile them, and you shouldn't assume the smaller number is the stale one — the README's department tables are the more granular source. The structural idea is the part worth understanding. Most prompt libraries are a flat list. headcount is a tree with an install boundary at every branch. The CEO office sits at the top with 7 skills, and the departments below it each carry their own skills plus an agent charter in .claude/agents/. That charter is what lets a department be delegated to as a subagent with its own exclusive write scope — the producer/auditor split the agent-hierarchy skill describes. Addressing is namespaced. security:threat-modeling, finance:unit-economics, demand-generation:landing-page-cro-expert. You can ask in natural language and let matching load the skill, or you can call it by name when you want a specific perspective: /finance:financial-modeling Install, and the constraint that shapes everything Claude Code: /plugin marketplace add cbrock84/headcount /plugin install security@headcount Then add departments as you need them — /plugin install it-operations@headcount, and so on. ChatGPT and Codex use the same repository. You add it as a plugin marketplace (ChatGPT reads the manifest at .agents/plugins/marketplace.json), or you copy the departments you want into your own project's .agents/skills/ directory. The skill files are identical on both sides; only the manifests differ, and both manifests are generated from the same directory tree, so a fix lands in both at once. That's what AGENTS.md is about. Here is the constraint that explains the whole design. On the ChatGPT/Codex side, skill descriptions share a context budget of roughly 8000 characters. All 16 departments together come to roughly 50000. Installing only the departments you'll actually use isn't tidiness — it's the only thing that fits. If you've ever wondered why a plugin system would bother with per-department granularity instead of one big install, that ratio is the answer. Installing a department doesn't touch your project. It adds skills to the assistant. It doesn't write to your repo, add dependencies, or run anything on its own. What the Chinese version adds The Chinese repository is a translation of the original README, dated 2026-10-14, with the original preserved as README_en.md. Stars: zero, as of writing. It was published today. I'm not going to pretend otherwise. The interesting part is that it isn't only a translation. The page carries two clearly separated layers: A 中文快速上手 section at the top, explicitly marked as supplementar

This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.