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 skills add liqiongyu/lenny_skills_plus --skill organizational-designgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/skills/liqiongyu/lenny_skills_plus/organizational-design)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/organizational-design"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/organizational-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/organizational-design"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/organizational-design.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00023 | $0.02090 |
| Opus 5 | $0.00012 | $0.01045 |
| Sonnet 5 | $0.00005 | $0.00418 |
| Haiku 4.5 | $0.00002 | $0.00209 |
Grade A, and why
organizational-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 13d 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organizational Design
Scope
Covers
- Designing or redesigning an organization's structure + operating model to improve speed, accountability, and customer outcomes
- Choosing between centralized vs decentralized models (Apple ↔ Amazon spectrum) and functional vs divisional/value-stream orientations
- Reducing coordination tax by minimizing dependencies and clarifying decision rights
- Setting management roles/layers so leaders know the work and can drive craft, not just process
When to use
- "Propose a reorg / org design for my product + engineering organization."
- "We're slow due to dependencies—redesign teams so we can run in parallel."
- "Our UX is fragmented—should we centralize decisions or strengthen functional leadership?"
- "We grew fast and added layers—help us simplify and get back to startup speed."
When NOT to use
- You need product strategy/vision first (use
defining-product-visionorworking-backwards). - This is mainly a people-performance issue (use coaching/feedback workflows, not a reorg).
- You need compensation bands, leveling, hiring plans, or legal/HR guidance (involve HR/legal).
- You need a single high-stakes decision process (use
running-decision-processes). - You need a full organizational transformation program with change management, pilots, and culture change (use
organizational-transformation; this skill produces the structural blueprint that transformation executes). - You need to improve engineering practices, norms, or technical culture (use
engineering-culture). - You need to build team culture (values, rituals, norms) within existing teams (use
building-team-culture). - You need cross-team coordination processes without changing the org chart (use
cross-functional-collaboration).
Inputs
Minimum required
- Org context: company stage, domain, size, and which functions are in-scope (e.g., Product/Eng/Design/Data)
- Current structure: teams, reporting lines (rough is fine), and how work is currently organized
- Primary goals: what must improve (e.g., speed, quality, integrated UX, ownership, cost)
- Key symptoms with examples (e.g., slow decisions, rework, unclear ownership, fragmented UX)
- Constraints/non-negotiables (headcount, timeline, critical launches, regulatory/compliance, leadership preferences)
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- eval/eval_config.json 1.9 KB
- eval/SHOWCASE.md 5.1 KB
- eval/with_skill.md 45 KB
- eval/without_skill.md 22 KB
- README.md 1.8 KB
- references/CHECKLISTS.md 2.2 KB
- references/EXAMPLES.md 2.4 KB
- references/INTAKE.md 1.6 KB
- references/RUBRIC.md 3.1 KB
- references/SOURCE_SUMMARY.md 1.7 KB
- references/TEMPLATES.md 4.3 KB
- references/WORKFLOW.md 3.6 KB
- skillpack.json 379 B
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.
- 13d ago First seen · 127 lines · 23 tokens per session scan A d4a4573f7033
organizational-design is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 2,090 once invoked, about $0.0001 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.
Other skills, from other repositories
exec-weekly-agenda-generator
Synthesize the past week across meetings, chat, email, and calendar to generate a ranked list of 5-10 topics for the weekly leadership team meeting. Use when the user asks to prep for their leadership meeting, generate meeting topics, build the agenda, or says "prep me for Monday.".
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.