Headcount plugin for Grok Build

Community Claude Code plugin, installs in GrokPluginDevelopment

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.

How to install Headcount in Grok Build

1. Add this repo as a plugin marketplace in Grok Build (once per computer):

grok plugin marketplace add cbrock84/headcount

2. Install the plugin:

grok plugin install executive@cbrock84/headcount --trust
✓ Install-checked in Grok Buildchecked Oct 18, 2026

Review before you trust it. --trust lets this plugin's hooks, MCP servers and scripts run code on your computer. It's a community repo that neither xAI nor GrokStacks has reviewed, so read its code first.

This repo's marketplace has 16 plugins; we checked executive, it-operations, technology. Install another the same way: grok plugin install <name>@cbrock84/headcount --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Inside Grok Build: type /plugins, open the Marketplace tab, press a and add cbrock84/headcount, then select executive and press i.

Command format: Grok Build's plugin guide

What we checked: on Oct 18, 2026 it installed with grok 1.0.62 and Grok found 38 skills. That's an install check only: we haven't run it in a live Grok session.

What it contains

Skills (38)

  • agent-hierarchy — Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the u
  • ai-research-analyst — Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map com
  • business-growth-consultant — Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where
  • ceo-advisor — Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging bef
  • chief-executive — Sets direction, allocates capital and attention, and makes the calls no one else can make. Use this when a decision spans more than one function, when priorities conflict and something must be cut, when a plan needs pressure-testing before
  • fundraising-and-investor-relations — Raises capital and manages the relationship afterward — deciding how much and why, understanding what dilution and preferences actually cost, running a process with real competitive tension, preparing for diligence before it starts, and rep
  • saas-idea-validator — Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather than encouragement. Use this when an idea needs pressure-testing before anyone builds, when
  • ai-workflow-architect — Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, desig
  • api-design — Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers
  • branch-and-worktree-workflow — Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when imp
  • chief-technology-officer — Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeof
  • cloud-infrastructure — Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale o
  • code-review — Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedbac
  • completion-verification — Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or pas
  • data-migration — Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and parallel-run cutover, reconciling counts and values rather than assuming, handling the records tha
  • implementation-planning — Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a
  • observability-and-reliability — Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliabi
  • parallel-agent-delivery — Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. Use this when facing several independent tasks with no shared state, when a plan has parallelizable steps, when a broa
  • prompt-optimizer — Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it across models. Use this when a prompt is not producing what was wanted, when output varies run t
  • release-and-deployment — Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. Use this to design a deployment pipeline, reduce release risk, roll out a risky change gradually, plan a schema migration, or
  • skill-authoring — Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do. Use this when creating a new skill, editing an existing one, diagnosing a skill that fires too often or never fires, or reviewing
  • solution-architecture — Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. Use this to design a new system or major component, choose between architectural options, review an existing design
  • solution-exploration — Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component,
  • systematic-debugging — Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom th
  • technical-debt-management — Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritize debt, decide whether to fix or live with something, just
  • test-driven-development — Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing implementation code for any feature or bugfix, when a bug needs a regression test, when existing code is hard to change sa
  • backup-and-recovery — Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or
  • chief-information-officer — The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap,
  • cloud-administration — Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider
  • collaboration-platform-administration — Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external shari
  • endpoint-management — Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardize builds, roll out software or an OS upgrade, handle
  • identity-lifecycle-administration — Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning. Use this to set up or fix joiner-mover-leaver, deprovision someone completely, clean up accumulated ac
  • it-asset-management — Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. Use this to build an asset register, prepare for a software audit, plan a refresh cycle, control license spend, or dispose of
  • network-administration — Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan ad
  • service-desk — Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat co
  • systems-administration — Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. Use this to establish a patching cadence, standardize server configuration, plan a maintenance window
  • telephony-and-conferencing — Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this t
  • virtualization-operations — Runs the hypervisor layer beneath the servers — host capacity and consolidation ratios, VM sprawl, snapshot discipline, resilience and live migration, and licensing that counts cores rather than instances. Use this to size or expand a clust

Plugins in this marketplace (16)

  • executive — Direction, capital and attention allocation, cross-functional arbitration, strategy validation, and the method for structuring the organization itself.
  • technology — Architecture, engineering delivery, development discipline, debugging, review, and AI and automation systems.
  • it-operations — Corporate IT: service desk, systems and network administration, virtualization and cloud, telephony and conferencing, endpoints, assets, identity lifecycle, and backup and recovery.
  • product — Product strategy, UX and usability audit, design systems, interface craft, brand expression, and visual direction.
  • marketing — Positioning, content strategy and production, social and video, brand voice, copywriting, PR, and partnerships.
  • demand-generation — Organic and paid acquisition, conversion, measurement, experimentation, lifecycle messaging, and distribution.
  • revenue — Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
  • finance — Financial modeling, budgeting and forecasting, unit economics, and financial decision support.
  • operations — Program management, process design, vendor and supplier management, and operational delivery.
  • pmo — Enterprise program management office: portfolio governance, program and project delivery, delivery risk, benefits realization, and adoption.
  • people — Org design, hiring and interviewing, compensation and leveling, and workforce planning.
  • legal-risk — Contract review, privacy and data protection, enterprise risk, compliance, and audit readiness.
  • security — Threat modeling, security architecture review, incident response, vulnerability management, and access and identity. Reviewer-class.
  • customer-experience — Support operations, escalation management, voice of customer, and self-service. Owns what the customer experiences after the sale.
  • data-analytics — Data governance, warehouse and semantic modeling, business intelligence, and AI/ML governance.
  • corporate-strategy — Portfolio strategy, corporate development, strategic alliances, and scenario planning.

About this listing

Headcount is a community plugin on GitHub by cbrock84, written as a Claude Code plugin that Grok Build installs. We install-checked it in Grok; we haven't run it in a live session or reviewed its code. When we installed it, Grok found 38 skills, 16 plugins in this marketplaces. Its license is MIT. We checked commit 7d3ddf170a85. It's one of 409 listings in the Development category on GrokStacks.

Stacks Weekly: every new Grok Build and Codex plugin, every Tuesday.

One short email for GrokStacks and CodexStacks readers, with each new plugin's install line and what it ships. Subscribe and get the free starter list: 20 Grok Build plugins worth installing first.

You'll get a confirmation email first. Unsubscribe anytime.

Headcount FAQ

How do I install Headcount in Grok Build?

Add the repo as a marketplace with grok plugin marketplace add cbrock84/headcount, then run grok plugin install executive@cbrock84/headcount --trust. This repo's marketplace has 16 plugins; we checked executive, it-operations, technology. Install another the same way: grok plugin install <name>@cbrock84/headcount --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Is Headcount an official Grok Build plugin?

No. Headcount is a community plugin on GitHub by cbrock84, not in xAI's official Grok Build marketplace. We checked that it installs and what Grok loads from it, but haven't run it in a live Grok session or reviewed its code.

What does Headcount include?

According to what Grok loaded in our install check, Headcount includes 38 skills, 16 plugins in this marketplaces: agent-hierarchy, ai-research-analyst, business-growth-consultant, ceo-advisor, chief-executive, fundraising-and-investor-relations….

Details

Type
Plugin
Category
Development
Source
Community Claude Code plugin, installs in Grok
License
MIT
Author
cbrock84
Keywords
agent-marketplace, chatgpt-plugin, chatgpt-skills, claude-code, claude-code-plugin, claude-plugin, claude-skills, mcp, organization
Source repo
https://github.com/cbrock84/headcount
Checked commit
7d3ddf170a85
Homepage
https://cbrock84.github.io/headcount/
Checked by GrokStacks
Install-checked in Grok Build on Oct 18, 2026; not run in a live session

Something wrong or missing? Submit or improve this listing. Marketplace listings also refresh automatically every night.

For maintainers: badge and embeds

Maintain Headcount? Add the badge; it links to this page.

Listed on GrokStacks

Markdown

[![Listed on GrokStacks](https://grokstacks.com/badge.svg)](https://grokstacks.com/p/headcount/)

HTML

<a href="https://grokstacks.com/p/headcount/"><img src="https://grokstacks.com/badge.svg" alt="Listed on GrokStacks" width="164" height="28"></a>

Embed card (static HTML and inline CSS, no JavaScript). Preview:

<a href="https://grokstacks.com/p/headcount/" style="display:block;max-width:380px;box-sizing:border-box;padding:14px 16px;border:1px solid #2a2e3c;border-radius:12px;background:#0a0b0f;color:#e8eaf0;font:14px/1.45 -apple-system,Segoe UI,Roboto,Helvetica,Arial,sans-serif;text-decoration:none"><span style="display:block;font-size:16px;font-weight:700;color:#e8eaf0">Headcount</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 38 skills, 16 plugins in this marketplaces</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing…</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[Headcount on GrokStacks](https://grokstacks.com/p/headcount/)**: Community plugin for Grok Build with 38 skills, 16 plugins in this marketplaces. Install: `grok plugin install executive@cbrock84/headcount --trust` (after `grok plugin marketplace add cbrock84/headcount`)

More on badges, embeds and keeping your listing up to date: GrokStacks for plugin authors.

Also in Development

All 409 development listings →