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-transformationgit 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-transformation)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/organizational-transformation"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/organizational-transformation/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-transformation"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/organizational-transformation.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.02080 |
| Opus 5 | $0.00012 | $0.01040 |
| Sonnet 5 | $0.00005 | $0.00416 |
| Haiku 4.5 | $0.00002 | $0.00208 |
Grade A, and why
organizational-transformation 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 12d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organizational Transformation
Scope
Covers
- Designing and leading a practical transformation plan to move a company toward a modern product operating model
- "Nudging" legacy orgs: sequencing change so it's adopted, not rejected
- Avoiding the trap of treating framework adoption (Spotify, SAFe, etc.) as the end goal
- Coordinating structure + process + culture changes (teams, decision rights, discovery/delivery, incentives, rituals)
When to use
- "Help me move us from feature teams to empowered product teams."
- "We keep adopting frameworks but nothing changes—build a real transformation plan."
- "Create a 90-day pilot plan plus a roadmap for rolling out a product operating model."
- "Our leaders want transformation; teams are skeptical. Build a change + comms plan that reduces rejection."
When NOT to use
- You need strategy/vision first (use
defining-product-visionorworking-backwards). - You only need an org chart / team topology change (use
organizational-design). - You need project management for a known plan (use
managing-timelines). - You need HR/legal guidance on comp, layoffs, labor law, or sensitive people actions (involve HR/legal).
- You need to improve engineering norms, technical practices, or code quality culture (use
engineering-culture). - You need to build team culture (values, rituals, norms) within existing teams without changing the operating model (use
building-team-culture). - You need to align stakeholders on a single decision rather than drive sustained organizational change (use
stakeholder-alignment).
Inputs
Minimum required
- Org context: industry, size/stage, geography, regulated constraints (if any)
- Executive sponsor + decision maker(s) and the transformation "why now"
- Current operating model symptoms (with examples): decision bottlenecks, output-vs-outcome mismatch, discovery gaps, dependency chains
- Current team model (feature teams vs product teams), and where product decisions currently live
- Constraints: timelines, budget/headcount, must-keep processes, critical launches
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.8 KB
- eval/SHOWCASE.md 5.5 KB
- eval/with_skill.md 57 KB
- eval/without_skill.md 31 KB
- README.md 1.9 KB
- references/CHECKLISTS.md 2.1 KB
- references/EXAMPLES.md 803 B
- references/INTAKE.md 1.5 KB
- references/RUBRIC.md 3.2 KB
- references/SOURCE_SUMMARY.md 1.6 KB
- references/TEMPLATES.md 4.6 KB
- references/WORKFLOW.md 3.4 KB
- skillpack.json 403 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.
- 12d ago First seen · 133 lines · 23 tokens per session scan A 700c7d86c22a
organizational-transformation 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,080 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.