org-design

org-design is a command for Claude Code from abinauv/business-consulting. It costs 7 tokens per session (408 once invoked), scanned A, original, MIT.

An assessment of how an organisation is arranged, including teams, reporting layers, manager workloads, support functions, and decision-making. It compares the structure with the organisation’s goals and relevant peers.

In plain words
What is it for?
Use it to review an org chart, spans of control, centralised versus local decisions, duplicated roles, and structural changes that could improve efficiency.
Why use it?
It helps reveal unnecessary management layers, duplicated work, slow decisions, and mismatches between strategy and structure.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the business-consulting plugin — 16 skills, 24 commands shipped together

Good fit Use it to review an org chart, spans of control, centralised versus local decisions, duplicated roles, and structural changes that could improve efficiency.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/abinauv/business-consulting/org-design
Install

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.

Clone the repo
git clone --depth 1 https://github.com/abinauv/business-consulting

Made for: Claude Code.

Or install business-consulting, the plugin that ships this one along with the rest of its 16 skills, 24 commands.

Wrote 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.

agentmods badge for org-design

README.md
[![agentmods](https://agentmods.dev/badge/commands/abinauv/business-consulting/org-design.svg)](https://agentmods.dev/commands/abinauv/business-consulting/org-design)
Your own site
<a href="https://agentmods.dev/commands/abinauv/business-consulting/org-design"><img src="https://agentmods.dev/badge/commands/abinauv/business-consulting/org-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 408 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.00408
Opus 5 $0.00003 $0.00204
Sonnet 5 $0.00001 $0.00082
Haiku 4.5 $0.00001 $0.00041

Measured 8d ago against content hash a8b71b03434e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

org-design 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 8d 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.

commands/org-design.md · 62 lines

What it actually says

Organizational Design Assessment

Assess organizational structure and recommend improvements for $ARGUMENTS.

Instructions

1. Current State Assessment

Structure Analysis:

  • Current org chart structure (functional, divisional, matrix, flat)
  • Number of management layers (CEO to front line)
  • Average spans of control by level
  • Benchmark against peers of similar size

Efficiency Metrics:

  • Revenue per employee (vs. peers)
  • Management overhead ratio (managers / total headcount)
  • Support function ratio (support FTEs / total FTEs)
  • Duplicate roles or functions across business units

Decision-Making:

  • Where do key decisions get made? (centralized vs. decentralized)
  • Average decision cycle time for key processes
  • Escalation patterns (how many levels for common decisions?)

2. Gap Identification

Spans & Layers Issues:

  • Layers that are too deep (>7 for companies <10K employees)
  • Spans that are too narrow (<4 direct reports) — management bloat
  • Single-report managers ("totem poles")

Structural Misalignments:

  • Strategy says X but the org is designed for Y
  • Functions that should be centralized but aren't (or vice versa)
  • Missing capabilities or functions
  • Unclear RACI for key processes

3. Design Options

Present 2-3 structural alternatives with trade-offs:

Design Option Pros Cons Best For

4. Recommended Design

  • Proposed org structure (describe the changes)
  • Target spans and layers
  • RACI clarifications for key processes
  • Shared services opportunities
  • Expected headcount impact and cost savings

5. Implementation Approach

  • Phased transition plan
  • Change management requirements
  • Communication plan outline
  • Risks and mitigation strategies
Changes

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.

  1. 8d ago First seen · 62 lines · 7 tokens per session scan A a8b71b03434e

Subscribe to this mod's changes

org-design is a command published in the GitHub repository abinauv/business-consulting (28 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 408 once invoked, about $0.0000 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-08-30.

Related

Other commands, from other repositories

diagnose-underperformer

Diagnose why a specific Google Ads or Meta Ads campaign / ad set / ad is underperforming and prescribe the next concrete action. Use when the user says something like "why is X not converting?", "this campaign is wasting money", or "why are impressions so low?". Read-only — no changes are made.

markifact/markifact-mcp · 64 tokens

edit-meta-creative

Edit a Meta ad's creative content — landing page URL, primary text, headline, description, CTA, link description — across one ad or many. Use when the user says "change the URL on my ads", "update the copy", "swap the CTA", or anything that changes what an existing Meta ad shows. Meta does not allow in-place creative…

markifact/markifact-mcp · 88 tokens

launch-google-search

Launch a complete Google Ads Search campaign — campaign, ad group, responsive search ads, keywords, sitelinks, callouts, and negatives — built paused and ready to review. Use when the user wants to spin up a new Search campaign on Google Ads.

markifact/markifact-mcp · 52 tokens

launch-meta-campaign

Launch a complete Meta Ads campaign — campaign, ad set, and ad(s) — built paused and ready to review. Use when the user wants a new Facebook/Instagram campaign.

markifact/markifact-mcp · 36 tokens

launch-pmax

Launch a Google Ads Performance Max campaign with a complete asset group, audience signals, and (for ecom) listing groups. Built paused for review. Use when the user wants a new PMax campaign.

markifact/markifact-mcp · 41 tokens

negative-keyword-sweep

Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.

markifact/markifact-mcp · 50 tokens