# A CIO drew an org chart for AI: headcount 70 days 2,578 stars, then the whole account vanished · GitHub open-source project

> Source: https://stringers.io/en/github/gh_cbrock84__headcount.html (Stringers / 什么值得做, generated 2026-11-08)
> Stringers answers one question every day: what small product can one or two people build in a few months and actually make money from. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these verdicts and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools today / hot / products / directions / direction / data. Setup: https://github.com/komako-workshop/stringers (the user logs in at stringers.io → "配置 agent" to get a personal URL). Site index: https://stringers.io/llms.txt

> The author had real CIO experience and, in the first week, posted to Reddit, wrote a long-form piece, and sent PRs to awesome lists. After that, big X accounts and Facebook repost accounts ran the ready-made line "someone open-sourced an entire AI company" through two waves.

[GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-6

C

cbrock84/headcount · cbrock84

# A CIO drew an org chart for AI: headcount 70 days 2,578 stars, then the whole account vanished

**What it is** An open-source skills library that splits 172 Claude Code / Codex skills by company structure into 16 separately installable departments. Review departments like security and legal only have veto power.

**Why it took off** The author had real CIO experience. In the first week he posted on Reddit himself, wrote a long article, and submitted PRs to awesome lists. Afterwards, big X accounts and Facebook repost accounts ran with the ready-made line "someone open-sourced an entire AI company" in two waves.

**B** **How you could get in** Build a Chinese or China-market version, or go deep on just one department: copy the structure of per-department installs, namespaces, and review veto power, write the content for real roles and local regulations, and put numbers on the README's first screen so repost accounts can use them in templates.

Grade B: the original repo's disappearance leaves a gap, and founder-skill hitting 2,488 stars in a month shows the path still works. But the "AI company" narrative is already occupied by a project with over a hundred thousand stars, the ceiling is roughly two to three thousand stars, and it's easy to be seen as a repost. Being passed around in small circles

Data (updated daily) · repo created 2026-08-28 · 2,578 stars

GitHub · stars

Data 2026-08-29 → 2026-11-05 (69 days, 30 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

An Atlanta CIO with 25 years in IT arranged 172 Claude Code skills into 16 departments that make up "one company" and open-sourced them. In a little over two months it got 2,578 stars and 429 forks. When people looked again in Nov 6, the repo, the author's homepage, and the org chart web page were all 404. Below: what it is, why it took off, and whether the vacated spot is worth taking.

### Two agents edited the same file

In Aug 2026 30, Chris Brock published "Giving AI agents an org chart" on his Substack. It opens with a small incident: he was running several Claude Code agents at once, one handling SEO and one handling UI, and both ended up editing the same file. The page title counts as SEO, the page itself counts as UI, and "neither agent did anything wrong."

His fix was the CIO's old method: don't divide work by "what topic you own," divide it by "which files you can write." Concrete paths like `/security/*`, with one path having exactly one owner. Every push runs a script, and whoever crosses a boundary breaks the build. "The same conflict now surfaces in 4 seconds, not two days later." Writing it out, he realized each agent now had an exclusive scope of responsibility, which is an org chart.

The day before (Aug 28) he created the repo cbrock84/headcount, and by the next day it had 190 stars (Wayback snapshot, 08-29). It was his only repo on GitHub.

### What it is

A pure Markdown skills library organized as a company: under the CEO office are 16 departments (technology, security, IT operations, product, marketing, demand generation, revenue, finance, operations, PMO, legal and risk, people, and more), 172 skills in total (README, 09-25). A few design choices set it apart from other skill collections:

- **One plugin per department, install as needed.** `/plugin install security@headcount`. Want a financial model? Install Finance. Hiring ten people? Install People. Installing all skills comes to roughly 50k characters, while the skill-description budget on Codex / ChatGPT is only around 8,000 characters, so without splitting by department it simply won't fit.

- **`Department:skill` naming.** `security:threat-modeling`, `finance:unit-economics`, so names never collide.

- **Review departments can only veto.** Security and legal report directly to the top, write no files themselves, and can only block; the people being reviewed can't override them. In the author's words: "In a company, getting this reporting line right takes years and a general counsel. Here it's a few lines of config."

- **The same directory works on both sides.** Claude Code plugin marketplace and ChatGPT / Codex skills both generate manifests at once.

The source of the content is also deliberate. The author says he's personally run security, IT operations, and architecture, so he can write those. Tax, benefits and leave, procurement, and marketing events he couldn't write, so he used the Indeed and ZipRecruiter MCPs to read real job postings, then checked against the U.S. Bureau of Labor Statistics occupational classification and filled in nearly a dozen missing functions. The pitch in the intro is "citing the standards and regulators that actually make the call."

### How the stars grew

| Timeline | star | What happened |
|---|---|---|
| 08-29 | 190 | The author posted "I turned 25 years of company experience into an open-source 'company in a box'" on r/claudeskills |
| 08-30 to 09-02 | — | A Substack long-form piece; the author personally submitted PRs to 3 awesome lists including VoltAgent and BehiSecc; a dozen AI auto-content sites rewrote it in unison |
| About 09-03 | About 1,100 | A LinkedIn blogger with 20k followers posted "about 1,100 stars in the first week" |
| 09-25 | 1,665 | Wayback snapshot |
| From ¥09-30 | 10-09 to 2,015 | @RoundtableSpace on X, with 271k followers, posted "Someone open-sourced an entire AI company with 172 specialists", 50k views |
| 10-10 to 10-27 | 2,017 → 2,088 | 0 to 11 stars a day, basically flat |
| 10-28, 10-29 | +45, +280 | A batch of Facebook accounts and groups posted the same "🚨 This GitHub repo turns Claude Code, ChatGPT and Codex into an agent organization…" text at the same time |
| 11-05 | 2,578 / 429 fork | Afterwards, single digits per day |
| 11-06 | 404 | The repo, homepage, and org chart page were all gone |

(The daily figures from October onward come from GitHub daily snapshots. I couldn't confirm which post brought the 10-29 stars at 280; only the timing lines up.)

Two things are worth noting. First, about 65% of the stars came in the first month, driven by the author himself: a Reddit post grounded in real experience, a long article explaining the "why," PRs he submitted to awesome lists by hand, and an interactive org chart you can search, where each cell links to its skill. That kind of page is made for screenshots. Second, the next two waves weren't posted by the author; repost accounts put a ready-made line on top. It didn't make Hacker News, Product Hunt, or GitHub Trending (new repos can't get in within about 60 days).

The fork rate is 16.6%, higher than typical for a new repo. Skills libraries often work this way: people fork them and adapt them to their own company, or use them directly as an install source.

### What it really borrowed was a ready-made line

"Someone open-sourced an entire AI company" was not written for headcount. The phrasing blew up on X in June, originally from msitarzewski/agency-agents, an "AI agency" of 147 agent roles, now at 167k stars. After that, repost accounts seeing similar repos only had to change a number to post: "172 specialists" or "16 departments." The headcount README put those two numbers right at the very top.

A comparison makes the point clearly: w95/awesome-claude-corporate-skills built almost the same thing in February (166 skills organized by company role), and it's at 304 stars now. The difference isn't content; it's that the headcount author spread it himself in the first week, and it happened to get picked up by big accounts that turned it into a template. The structural care made knowledgeable people willing to fork it and write long recommendations, but the volume came from that line.

### How crowded this space is

The idea of "organizing AI into a company" was already crowded:

| Project | star(11-05/06) | How it differs from headcount |
|---|---|---|
| msitarzewski/agency-agents | 167k | A concept prototype, persona-style roles, leaning toward creative marketing, with no per-department install and no veto power |
| anthropics/knowledge-work-plugins | 35k | Official sales, finance, and legal plugins that only cover a few broad categories |
| garrytan/gstack | 140k | Celebrity endorsement, playing CEO, design, and engineering manager, leaning toward dev workflow |
| paperclipai/paperclip | 111k | An executable "AI company" orchestration app with a UI |
| coreyhaines31/marketingskills | 59k | Only a marketing department, but deep |
| Jakeschincariol/founder-skill | 2,488 | Created only in Oct 7; a "board + departments" tool for testing startup ideas, matched headcount in one month |

Headcount's position: no celebrity, no big-company backing; among the latecomers, the one with the most solid content. Now it's gone, leaving 429 forks and seven or eight full re-uploaded copies (imft-debug/headcount-claude-company, NDay27/headcount, etc.), plus a Chinese translation, headcount-cn, created in Oct 13 with only 1 stars.

Why it vanished is unclear. Checking the author's profile along with 404 points more to an account-level event (a rename or a ban) than to a single repo being deleted (inference). The author's compliance company Keel-GRC and personal site chrisbrock.io are both still up, and I found no new address after a move.

### If it were you

**Verdict: B.** Worth a try. The original repo is gone, so this direction does have an open spot, and founder-skill reaching 2,488 stars in a month shows the "department-based skills library + template copy" path still works. But the "AI company" narrative itself is already held by a project with over a hundred thousand stars, so what you build will most likely land in the two-to-three-thousand-star range, and it's easy to be dismissed as another repost.

**Who it suits:** People who've actually worked in an industry and can write "real stuff": developers who've been finance, HR, legal, or operations leads; or people who know the domestic work environment and want to make a Chinese version. Headcount got eight times as many stars as w95 mainly because its author really was a CIO.

**Who it doesn't suit:** Anyone planning to rename a fork of headcount and republish it (there are already seven or eight of those, none of which took off); anyone with no industry experience who plans to have AI batch-generate hundreds of skills to pad the count. That's exactly the "hollow company filler" the author said he wanted to avoid.

**How to do it:** Three paths, ordered from most to least confidence:

1. **Chinese / domestic version.** Rewrite it using the departments and rules of Chinese companies: tax by VAT and individual income tax, HR by the Labor Contract Law and social insurance, legal citing domestic regulations, and support common domestic agent tools beyond Claude Code and Codex. The English original's content can be referenced, but the sources need to be swapped for domestic ones.

2. **A well-maintained successor.** MIT-licensed, so the content in forks can be legally reused. State the origin, fill in the departments the original author didn't finish, make "which standard each skill cites" visible, and keep updating. The original repo has stopped at its last commit in Oct 18.

3. **Only one department, but deep.** Follow the marketingskills approach: for example, only a "security and compliance department" or a "finance department," which goes far deeper than a collection of 172 skills.

Copy its three structures: install by department, name as `department:skill`, and review roles have only veto power. Then add an interactive, screenshot-friendly org chart page.

**How to get users:** Use its first-week playbook: post a personal-experience piece in the relevant subreddit (or in China on Jike, V2EX, or Juejin), write a long article explaining clearly "why it's split this way," and submit PRs to awesome lists yourself. Put the numbers on the README's first screen ("N departments, M skills") so repost accounts can directly use the line "someone open-sourced an entire AI company."

**When to move:** The sooner the better, ideally within a month. In early November people were still searching for headcount and clicking through to 404, and that attention will quickly scatter to forks and other projects.

**Signs you've misread it:** ① The author renames the account and restores the repo, with the original stars and forks intact, and the gap disappears; ② after you've executed the plan above for a month, stars stall at a few hundred, which means the "AI company" narrative is fatigued and template copy no longer drives volume; ③ Anthropic's official knowledge-work-plugins expands to cover "a whole company," and third-party collections get squeezed out wholesale.

### Data and sources

GitHub daily stars / forks (10-16 to 11-05); 11-06 direct visits to the repo, the author's profile, and cbrock84.github.io/headcount are all 404. Wayback snapshots (08-29, 09-25 README). Author's Substack "Giving AI agents an org chart" (08-30), chrisbrock.io. Reddit r/claudeskills (08-29). awesome-list PRs: VoltAgent/awesome-agent-skills #1227, BehiSecc/awesome-claude-skills #1067, JackyST0/awesome-agent-skills #136. X @RoundtableSpace (09-3.05M views); LinkedIn (09-03); Facebook posts and groups (10-02, 10-28). Trendshift sync-stop notice; Nix collector sudosubin/agents.nix 11-04, 11-05 removal PRs. Competitor star counts from GitHub (11-05/06). Anywhere marked "inferred" is inference.

[GitHub repo ↗](https://github.com/cbrock84/headcount)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| msitarzewski/agency-agents | Open source | 2025-10-13 | 167k stars / 27k forks | The prototype of the "AI company" concept, 147 personal-style agents; no per-department installs, no review veto or write boundaries, shallow business functions |
| obra/superpowers | Open source | 2025-10-09 | 313K stars | Only covers software development methodology, not finance, legal, HR, or other business departments |
| anthropics/knowledge-work-plugins (and anthropics/skills) | Big-company features | 2026-01-23 | 35k stars (skills 188k) | Official sales, finance, and legal plugins for Cowork covering only a few broad categories, with no whole-company organizational or governance structure |
| garrytan/gstack | Open source | 2026-03-11 | 140K stars | A celebrity-endorsed set of 23 tools playing CEO, designer, and engineering manager, skewed toward dev workflows |
| paperclipai/paperclip | Open source | 2026-03-02 | 111K stars | An interactive, executable "AI company" orchestration app; headcount is just skill text |
| coreyhaines31/marketingskills | Open source | 2026-01-15 | 59K stars | Covers only one department, marketing, but goes deep |
| alirezarezvani/claude-skills | Open source | 2025-10-19 | 29K stars | 380+ skills in a flat grab-bag, no departmental structure |
| w95/awesome-claude-corporate-skills | Open source | 2026-02-26 | 304 stars | Nearly the same idea (166 skills split by company role), but no author-driven distribution and no big accounts reposting it; it didn't take off |

Where users come from

- **Verified** **The author's Reddit post and Substack long-form** : r/claudeskills 08-29 "I turned 25+ years of corporate experience into an open-source org in a box"; Substack "Giving AI agents an org chart" 08-30

- **Verified** **The author submitted PRs to awesome lists himself** : cbrock84 personally opened VoltAgent/awesome-agent-skills#1227, BehiSecc/awesome-claude-skills#1067, and JackyST0/awesome-agent-skills#136; code search shows it was added to several awesome lists

- **Verified** **AI auto-generated content sites and skill directories (long-tail SEO)** : Zentor/MoClaw 08-30/31, Enterprise DNA 08-31, explainx 09-01, githubawesome 09-02, DeepWiki, SkillsLLM, QAI, agentmods, and others

- **Verified** **Secondary spread on LinkedIn** : Arthi R. (about 20k followers) 09-03 "about 1,100 stars in the first week"

- **Verified** **Big X accounts running the viral template** : @RoundtableSpace (271k followers) 09-30 "Someone open-sourced an entire AI company with 172 specialists", 50.6k views; @alex_verem the same day; 09-25→10-09 +350 stars

- Inferred **FB/IG/Threads repost account network** : Chris KE 10-02 (196 likes / 73 shares); 10-28 Chris Porter's personal account and several FB groups posted the same "🚨 This GitHub repo turns Claude Code…" copy, with +10-28/29→325 stars over the same period; we haven't confirmed each one matches

## Why cbrock84/headcount took off

> Source: GitHub · Research day 2026-11-06 · Data card gh_cbrock84/headcount

### The most important thing first: the repo has been gone since 11-06

- Checked 2026-11-06: `github.com/cbrock84/headcount`, `github.com/cbrock84` (author profile), and `cbrock84.github.io/headcount/` (interactive org chart) are all 404; the GitHub API returns Not Found for both the repo and the user; GitHub search can't find it even by its original description.

- The last time our GitHub collector captured it was 2026-11-05 (2578 stars / 429 forks, source=snap), so the disappearance happened between 11-05 and 11-06.

- Corroborating signals: the Trendshift page shows "Trendshift can no longer sync data for this repository from GitHub"; the Nix collector sudosubin/agents.nix sent PRs on 11-04 and 11-05 marking it "retired from collection, last pinned at 7d3ddf1" (PRs #110441 and #111937).

- The author's company org Keel-GRC and personal site chrisbrock.io are both still up (200); we found no new address after a "move" (Keel-GRC/headcount, vibld/headcount, etc. all 404).

- Cause unverified: the author may have deleted, renamed, or been banned by GitHub. Their profile page is also 404, which points more to an account-level event (a username change or a ban) than to a single repo being removed.

This matters most for "is it worth watching": the original repo is gone, but its 429 forks and a pile of full-repo reposts (see "Copycats") remain, and the slot in this opportunity is now open.

### What it is

A Markdown "skill library" organized like a company: one CEO office with 16 departments beneath it (engineering, security, IT ops, product, marketing, demand generation, revenue, finance, operations, PMO, legal and risk, HR, and more), 172 skills in total (README 2026-09-25 snapshot). Each department is a separately installable Claude Code plugin: `/plugin marketplace add cbrock84/headcount`, then `/plugin install security@headcount`. Skills are named `department:skill` (`security:threat-modeling`, `finance:unit-economics`) so they don't collide, and the same directory tree generates manifests for both Claude and ChatGPT/Codex. Each department also ships a `.claude/agents/` subagent charter that specifies which files it may write; security and legal are "review" departments that produce nothing themselves and can only veto. The pitch in the description is "cites the standards and regulators that actually make the call" (sources: Wayback 2026-09-25 README snapshot, the author's Substack).

Author Chris Brock is CIO at a company in Atlanta, has spent 25 years in IT, and founded the compliance firm Keel-GRC (keelgrc.com) (sources: chrisbrock.io, the author page on bestgithubrepositories.com).

### Growth curve (our GitHub repo_day data + Wayback)

| Date | stars | fork | Notes |
|---|---|---|---|
| 08-28 | 0 | — | Repo created |
| 08-29 | 190 | 26 | Wayback snapshot, day two after creation |
| ~09-03 | ~1,100 | — | LinkedIn (Arthi R., 20k followers) posted "about 1,100 stars in the first week" |
| 09-25 | 1,665 | 247 | Wayback |
| 10-09 | 2,015 | 316 | Our deep history |
| 10-10 to 10-27 | 2,017 → 2,088 | → 323 | 0–11 per day, basically flat |
| 10-28 | 2,133 (+45) | 339 |  |
| **10-29** | **2,413 (+280)** | 390 | Biggest single-day gain during the observation window |
| 10-30 to 11-05 | 2,483 → 2,578 | → 429 | +70, +41, +18, +12, +9, +8, +7, decaying day by day |
| 11-06 | 404 |  | The repo and the account are both gone |

Most of it came in the first month: about 65% of the stars (1,665/2,578) arrived before 09-25. The fork-to-star ratio is about 16.6%, above the median of 5000% for new repos with ≥11 stars (the baseline from the repo SCHEMA). This is common for skill libraries: people fork them to modify or use them as an install source. The suspect column in the repo is empty.

### Where users came from (in chronological order)

1. **The author's own launch (08-29 to 08-30)** : a r/claudeskills post, "I turned 25+ years of corporate experience into an open-source 'org in a box' for Claude" (08-29); a Substack long-form, "Giving AI agents an org chart" (08-30). The piece covers a real problem he hit: several Claude Code agents running in parallel edited the same file, so he restructured around which paths each role may write, with CI checking for boundary violations; review departments report directly to the top and hold only veto power. It's a CIO's management experience carried over to agents, not another prompt collection.

2. **The author submitted PRs to awesome lists himself** : VoltAgent/awesome-agent-skills #1227, BehiSecc/awesome-claude-skills #1067, and JackyST0/awesome-agent-skills #136, all opened by cbrock84 personally; code search shows it was added to lists from VoltAgent, BehiSecc, heilcheng (multilingual version), jqueryscript/awesome-claude-code, and others (confirmed).

3. **AI auto-content sites rewrote it within 72 hours** : Zentor, MoClaw (08-30/31, same article), Enterprise DNA's "AI Pulse" (08-31), explainx.ai (09-01), githubawesome.com (09-02), tom-doerr/repo_posts (09-14), DeepWiki, SkillsLLM, QAI, agentmods, claudecodexplugins, skills-hub, TypingMind's skill page, and auto-generated YouTube "podcasts"… These sites watch for new repos and auto-publish articles about them. For this repo it was free long-tail SEO, and it sends people back to GitHub.

4. **Secondary spread on LinkedIn in the first week** : Arthi R. (about 20k followers) 09-03 "about 1,100 stars in the first week"; Daniel Kornaś and others also posted about it.

5. **X big account (09-30)** : @RoundtableSpace (271k followers) 09-30 posted "Someone open-sourced an entire AI company with 172 specialists", 50k views and 155 likes (verified via fxtwitter); the same day @alex_verem posted "Found a GitHub repo that gives your AI agent an entire company of specialists for free." This copy follows the template from the agency-agents wave in June, "Someone open-sourced an entire AI company" (@sulekhat95, @RodmanAi, and others; 147 agents, 50k stars). It was then reposted word-for-word on Facebook (Chris KE 10-02,196 likes / 73 shares), Threads (@iffikhans), and Instagram Reels. 09-25→10-09 over these two weeks: +350 stars, which lines up with this wave in time.

6. **10-28 to 10-29 +325 stars** : Starting 10-28, a wave of Facebook copy went around: "🚨 This GitHub repo turns Claude Code, ChatGPT and Codex into an agent organization with 16 departments and 172 specialist skills. It's called Headcount, from cbrock84…" The same paragraph was posted several times by Chris Porter's personal account, the "Vibe Coding for Beginners" group (10-28 18:16), the "Html Css Bootstrap & JavaScript" group, Fatalinya and other accounts, plus a repodir.com link and Instagram Reels. This is the "one post, many accounts" matrix of AI news repost accounts. The timing lines up, but we couldn't confirm which post drove the 280 stars; no late-October original X post turned up in the local x-radar corpus (unverified).

7. **Channels we didn't find** : HN (no cbrock84 / headcount posts in Algolia), Product Hunt, and paid promotion turned up nothing. GitHub Trending doesn't list repos younger than about 60 days, and this one was only 10-27 days old when it was 60 days; in our database trending_days_any=0.

### Competitors (same idea: install a full set of "roles / departments" skills for Claude Code / Codex)

| Name | Form | Launched | Scale (GitHub repo 2026-11-05/06) | How headcount differs |
|---|---|---|---|---|
| msitarzewski/agency-agents | Open source | 2025-10-13 | 167k stars / 27k forks | The prototype of the "AI agency" concept, with 147 agent personas, leaning into character design and creative marketing; it doesn't install by department and has no review authority or write boundaries |
| obra/superpowers | Open source | 2025-10-09 | 313K stars | Software development methodology skills only; doesn't touch finance, legal, or HR functions |
| anthropics/skills, anthropics/knowledge-work-plugins | Big-company official | 2025-09 / 2026-01 | 188k / 35k stars | Official plugins for Cowork covering sales, finance, legal and more; authoritative but limited to a few broad categories, with no "whole company" narrative |
| garrytan/gstack | Open source | 2026-03-11 | 140K stars | Garry Tan's 23 tools, playing CEO, design and engineering manager; relies on a famous name and is development-process focused |
| paperclipai/paperclip | Open-source app | 2026-03-02 | 111K stars | An orchestration app that runs an "AI company" (with a UI, and it executes); headcount is just skill text |
| alirezarezvani/claude-skills | Open source | 2025-10-19 | 29K stars | 380+ skills in a flat grab bag |
| wshobson/agents | Open-source plugin marketplace | 2025-07-24 | 42K stars | Multi-harness plugin marketplace, development-oriented |
| coreyhaines31/marketingskills | Open source | 2026-01-15 | 59K stars | Covers only one department, marketing, but goes deep |
| w95/awesome-claude-corporate-skills | Open source | 2026-02-26 | 304 stars | Nearly the same idea (166 skills grouped by company role), but it never took off |
| Jakeschincariol/founder-skill | Open source | 2026-10-07 | 2,488 stars | Tests startup ideas with a "board + departments" setup, 11 skills, narrower and more like a toy |
| Bennettxai/FounderOS, 777genius/agent-teams-ai, aAAaqwq/AGI-Super-Team | Open source | 2026-02 to 07 | 1.4k / 2.4k / 114 stars | Same "departmentalized company OS" narrative |

Bottom line: "organizing AI into a company" isn't new; agency-agents already took the idea to hundreds of thousands of stars, and the "Someone open-sourced an entire AI company" template spreading on social media came from it. headcount's position is a later entrant with higher quality: the templated viral copy fits it directly, so it rides that wave naturally.

### Why it made the charts

1. **Riding a viral narrative that's already been proven** : "AI company / AI employees" is a topic that has flooded X and Facebook repeatedly for 2026 years (agency-agents has 167k stars). Repost accounts take ready-made copy, change a number and post it, which effectively "reposted" headcount: RoundtableSpace 09-30, FB matrix 10-28, and both waves brought star growth.

2. **The author has real industry credibility, so the content isn't hollow** : 25 years as an IT / CIO. The department breakdown draws on real job descriptions from Indeed and ZipRecruiter and the U.S. Bureau of Labor Statistics (BLS) occupational classifications, filling in functions like procurement, tax, benefits and leave, facilities, and events that are often missed. The bio stresses citing standards and regulators that have the final say. Among piles of hollow AI-generated skill libraries, this holds up in long posts and Reddit threads.

3. **The structure has a new point worth talking about** : each department can be installed on its own (the Codex/ChatGPT skill description has a budget of roughly 8,000 characters, and the full install is about 50k characters, so you can only install on demand), `department:skill` naming doesn't collide, sub-agents are split by write path, and review departments only have veto power. It grows out of real pain points in multi-agent collaboration, and "Add a department, not a prompt" is easy to repeat.

4. **The author handled distribution in the first week** : Reddit, Substack, PRs to 3+ awesome lists, plus a searchable interactive org chart page (good for screenshots and Reels). Dozens of AI auto-content sites and skill directories indexed it right after launch.

5. **Works on both platforms, good timing** : the Claude Code plugin marketplace and Codex/ChatGPT skills were both expanding 2026 years ago, and the same catalog installs on both, doubling reach.

### Differentiation, and was it the reason it worked?

The differentiation has three layers: (1) full business functions (finance, legal, HR, IT ops, PMO...), not just coding; (2) install by department with namespacing, which solves triggering and context problems when there are too many skills; (3) organizational governance: write boundaries, producers paired with reviewers, and review departments with veto power.

These are indeed why it didn't get buried: some content sites were willing to write about it, and someone on LinkedIn explained "why install by department." But a 2,578-star scale mainly came from the ready-made viral "AI company" narrative and the repost accounts. The same idea, w95/awesome-claude-corporate-skills, has only 304 stars; the difference is the author handling distribution, plus a big account happening to use the template. The structural care is what keeps knowledgeable people around (fork rate 16.6%), but growth still came from the narrative.

### How many people have seen it

Word spread in small circles: open source, no revenue involved; it was posted by an X account with 270k followers (RoundtableSpace, 50k views) and a batch of FB/IG/Threads repost accounts, plus a dozen or so AI auto-content sites; it didn't make HN and had no mainstream media coverage. Now the original repo is 404, and attention is spreading to forks and repost repos.

### Copycats

- Full-repo copies or re-uploads: imft-debug/headcount-claude-company, NDay27/headcount, icdance/headcount, Achal-Aggarwal/headcount, GGCryptoh/headcount, WaiChan8/headcount, MaxKElunic/headcount-max, ianmcgregor2904git/Headcount (Brave search results, star counts unverified), plus 429 forks.

- Chinese translation: yangshun2005/headcount-cn (created 10-13, 1 stars); the author also wrote a dev.to promotion post.

- Later entrants with the same concept: Jakeschincariol/founder-skill (created 10-07, 2,488 stars), serenakeyitan/agent-org-chart (created 09-22, 99 stars), another-bbzj/claude-agent-team (created 09-17).

### What others can borrow

- "Packaging by real org structure" is easier to explain and more useful than "N flat skills": single-department install, namespacing, and review-only veto roles can all be copied directly.

- Content credibility comes from external grounding: real job descriptions, BLS occupational classifications, regulatory standards. That holds up better than "I had AI write 200 prompts."

- Growth playbook: personal story posts on Reddit, long Substack pieces, your own PRs to awesome lists, and a screenshot-friendly interactive page, then let AI repost accounts and auto-content sites spread it for you. Put the numbers in the title ("172 specialists", "16 departments") so repost accounts can directly use the "Someone open-sourced an entire AI company" template.

- Opportunity: the original repo is at 11-06 and 404, and this spot is open. A well-maintained, department-installable, source-attributed "company skill library" (including a Chinese version and versions for domestic models and agents) could catch this traffic.

### Still unclear

- The reason the repo and account disappeared (self-deletion, rename, or ban) wasn't found; the 11-04 Nix indexer has already delisted it, and it may have had problems earlier (such as restructuring or going private).

- The direct source of 08-29's 190 stars that day: Reddit post scores and comment counts weren't captured (Reddit JSON was blocked), and we didn't check whether the author posted a launch thread on X.

- We only confirmed that the FB matrix posted in sync on 10-28 and that the post that drove +280 stars on 10-29 was not the X original (not found on the X side).

- Star counts for the repost repos weren't verified (the GitHub API was rate-limited partway through the investigation).

### Sources

- Our github repo: repo_day / repo_profile (cbrock84/headcount; competitor star counts, 2026-11-05/06)

- Wayback: web.archive.org/web/20260925075844/[github.com/cbrock84/headcount](https://github.com/cbrock84/headcount) (full README); CDX shows snapshots at 08-29, 09-17, 09-25

- Author: cbrock84.substack.com/p/giving-ai-agents-an-org-chart (08-30); chrisbrock.io; bestgithubrepositories.com/developers/cbrock84

- Reddit: reddit.com/r/claudeskills/comments/1w1t2ez (08-29); r/ClaudeAI/comments/1w45dve (09-01 someone recommended it)

- Awesome PRs: VoltAgent/awesome-agent-skills#1227, BehiSecc/awesome-claude-skills#1067, JackyST0/awesome-agent-skills#136

- Content sites: zentor.ai/blog/headcount-claude-code, enterprisedna.co AI Pulse 08-31, explainx.ai (09-01), githubawesome.com (09-02), dev.to (sun_young, 10-14)

- LinkedIn: Arthi R. 09-03 "~1,100 stars in first week"

- X: x.com/RoundtableSpace/status/2105398528856207591 (09-30.3M followers, 50.6k views, fxtwitter); x.com/alex_verem (09-30)

- Facebook: Chris KE 10-02; Chris Porter and the Vibe Coding for Beginners group 10-28; Threads @iffikhans

- Disappearance: trendshift.io/repositories/195881; github.com/sudosubin/agents.nix/pull/110441 (11-04), #111937 (11-05); 11-06 requested 404 directly

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.