agent-hierarchy SKILL.md skillA
agent-hierarchy from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/agent-hierarchy@git:20260901.aa45383Pins git:20260901.aa45383 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/executive/skills/agent-hierarchy/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260901.aa45383, committed Sep 1, 2026
- First version recorded
- Aug 28, 2026
- Size
- 5,001 bytes
- Repository stars
- 2,543
- License
- MIT
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 user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Agent hierarchy A method for standing up an orchestrator → specialist-subagent hierarchy, extracted from a working implementation of ~24 agents over a 1,500-file monorepo, machine-checked on every PR. ## The whole method in one paragraph Split agents by **write surface, not by topic**. Two classes only: **builders**, which edit inside exactly one exclusive surface and never commit, and **reviewers**, which are permanently read-only and can always run in parallel. The orchestrator — the main chat — is the sole committer. Write the surface map **before** any charters, keep it in one Markdown file, and enforce it with a script that runs in CI. Each row also carries an **authority** — `autonomous`, `proposes`, or `escalates` — which answers the separate question of whether that agent's work may land without a decision; most rows are `autonomous`, and gating everything makes the gate meaningless. Producer and auditor are never the same agent. For each class of fact, exactly one file owns it and everyone else derives. ## Why topic splits fail "One agent on SEO, one on UI" is the intuitive split and it breaks immediately: both end up …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/agent-hierarchy@sha256:87c4f28f64168313The line at the top of this page pins the label git:20260901.aa45383, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_g4k5kxpzlckxoitw)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 28, 2026 and Sep 1, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260901.aa45383 latest | 2026-09-01 | aa45383 | 5,001 B | A | view · diff |
| git:20260830.9f3436c | 2026-08-30 | 9f3436c | 4,652 B | A | view · diff |
| git:20260828.f80dcb5 | 2026-08-28 | f80dcb5 | 4,392 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5001 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_g4k5kxpzlckxoitw GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/agent-hierarchy GET https://markdownregistry.com/api/v1/blob/87c4f28f64168313974712db340ff6baef98b0249361b51a59eae6a598b22bc1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.