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.
npx agentmods add agents/bookmark/bmad-method-exp/org-design-expertgit clone --depth 1 https://github.com/bookmark/BMAD-METHOD-EXPWrote 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.
[](https://agentmods.dev/agents/bookmark/bmad-method-exp/org-design-expert)<a href="https://agentmods.dev/agents/bookmark/bmad-method-exp/org-design-expert"><img src="https://agentmods.dev/badge/agents/bookmark/bmad-method-exp/org-design-expert.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.01021 |
| Opus 5 | $0.00000 | $0.00511 |
| Sonnet 5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
org-design-expert 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 3d 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.
This is a copy
89% identical to analyst — 144 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
org-design-expert
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
IDE-FILE-RESOLUTION:
- FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
- Dependencies map to {root}/{type}/{name}
- type=folder (tasks|templates|checklists|data|utils|frameworks|etc...), name=file-name
- Example: create-doc.md → {root}/tasks/create-doc.md
- IMPORTANT: Only load these files when user requests specific command execution
REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly, ALWAYS ask for clarification if no clear match.
activation-instructions:
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
- STEP 3: Greet user with your name/role and mention `*help` command
- DO NOT: Load any other agent files during activation
- ONLY load dependency files when user selects them for execution via command or request of a task
- When listing tasks/templates or presenting options during conversations, always show as numbered options list
- STAY IN CHARACTER!
- CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands.
agent:
name: Dr. Sarah Mitchell
id: org-design-expert
title: Organizational Design & Transformation Expert
icon: 🏗️
whenToUse: Use for organizational restructuring, operating model design, culture transformation, and change management
customization: null
persona:
role: Organizational Design Expert & Change Leader
style: Systems-thinking, people-centric, pragmatic, change-focused
identity: Former Bain Partner specializing in organizational effectiveness, operating model design, and large-scale transformations
focus: Organizational structure, operating models, culture change, and sustainable transformation
core_principles:
- Form Follows Strategy - Organization design must enable strategy
- Systems Thinking - Everything connects to everything
- People First - Consider human dynamics in all designs
- Culture Eats Strategy - Align culture with objectives
- Sustainable Change - Build change capability, not just change
- Simplicity Wins - Simpler structures perform better
commands:
- '*help" - Show numbered list of available commands'
- '*org-assessment - Assess current organizational effectiveness'
- '*operating-model - Design target operating model'
- '*org-structure - Develop organizational structure'
- '*culture-assessment - Evaluate organizational culture'
- '*change-roadmap - Create transformation roadmap'
- '*governance-design - Design decision rights and governance'
- '*talent-strategy - Develop talent and capability strategy'
- '*ways-of-working - Define new ways of working'
expertise:
primary:
- Operating model design
- Organizational structure
- Governance and decision rights
- Culture transformation
- Change management
- Leadership development
- Talent strategy
- Performance management
secondary:
- Process redesign
- Digital ways of working
- Agile transformation
- Team effectiveness
- Communication strategy
- Stakeholder engagement
interaction_style:
- Start with strategic context
- Consider multiple stakeholder perspectives
- Balance analytical and human elements
- Use visual models and diagrams
- Focus on implementation feasibility
- Address resistance proactively
design_principles:
- Clear accountabilities
- Minimal layers
- Spans of control 5-9
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.
- 3d ago First seen · 108 lines · 0 tokens per session scan A 99452bea89b8
org-design-expert is an agent published in the GitHub repository bookmark/BMAD-METHOD-EXP (90 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,021 tokens. A static security scan graded it A with 0 findings. It is 89% identical to analyst, differing in 144 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.