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 skills/ace3000chao/book2startup/complexity-enemynpx skills add ace3000chao/book2startup --skill complexity-enemygit clone --depth 1 https://github.com/ace3000chao/book2startupWrote 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/ace3000chao/book2startup/complexity-enemy)<a href="https://agentmods.dev/skills/ace3000chao/book2startup/complexity-enemy"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/complexity-enemy.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.00131 | $0.02527 |
| Opus 5 | $0.00066 | $0.01264 |
| Sonnet 5 | $0.00026 | $0.00505 |
| Haiku 4.5 | $0.00013 | $0.00253 |
Grade A, and why
complexity-enemy 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 4d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complexity Enemy（复杂度是Scaling的敌人）
R — 原文 (Reading)
"The complexity just keeps growing exponentially. It's why many business owners often long for the day when the company was just them and an assistant."
— Verne Harnish, Scaling Up, 第2章 Barriers
I — 方法论骨架 (Interpretation)
Scaling的最大内部障碍不是竞争，不是资金，而是组织复杂度的指数增长。
复杂度的第一定律：每增加一个员工，复杂度不是线性增加，而是指数增加。
原因：每个新成员与现有成员之间的连接数呈组合增长（n×(n-1)/2）。10人团队有45对人际连接，50人有1225对。管理层级和流程的引入是为了"管理复杂度"，但往往反过来加剧了复杂度——你加了一层审批，同时加了N个人的等待时间和N种规避方式。
复杂度爆发的典型症状：
- 决策链条越来越长（从"CEO一句话"到"需要三层审批"）
- 会议越来越多（每加一个部门就多一批会）
- 流程越来越厚（打勾文化取代了真正的思考）
- 信息衰减越来越严重（基层听到的版本和CEO想说的完全不同）
Harnish的核心洞察： 很多企业主"怀念创业初期只有自己和一个助理的日子"——这不是怀旧，这是对简单执行力的本能渴望。复杂度每增加一分，你的组织离心力就增加十分。
反复杂度策略：
- 自动化替代流程化：用工具（软件/系统）替代人工流程，用规则替代判断
- 扁平化替代层级化：扩大管理幅度，减少中间层级
- 少规则替代多规则：Core Values三条比三十条更易执行
A1 — 书中的应用 (Past Application)
案例 1: 某科技公司"流程海啸"的自我毁灭
- 问题: 融资后引入VC要求的全套治理流程（董事会委员会、预算审批链、OKR、KPIs、MBO），员工从30人增至80人后开始集体反弹
- 方法论的使用: CEO意识到"投资人要求的流程"和"组织真正需要的流程"是两回事，开始"流程断舍离"——废除季度OKR调整为双周简报，砍掉6个委员会保留2个
- 结论: 不是不要流程，而是要最小化必要流程——每加一条规则必须同时问"能删哪条旧的？"
- 结果: 核心员工流失率从32%降至11%，决策速度提升3倍
案例 2: Basecamp 的"小团队"哲学
- 问题: 很多SaaS公司扩张后出现"功能团队"（按产品线设完整团队），导致资源重复和信息孤岛
- 方法论的使用: Basecamp坚持"全栈小团队"——每个团队都是小而全的独立单元（≤10人），用异步通信替代大量会议
- 结论: 小团队天然抗复杂度——不是因为人少，而是因为连接数少
- 结果: Basecamp在保持≤50人规模时营收突破1亿美元，人均产出远超同类公司
案例 3: 某传统企业"部门墙"的拆除
- 问题: 大企业病严重，市场部门抱怨研发不了解客户，研发抱怨市场乱承诺，销售说产品不行，产品说销售不会卖
- 方法论的使用: 引入"客户触点负责人"（Customer Touchpoint Owner）角色，打破部门墙——每个关键客户旅程节点有一个跨职能负责人，而不是每个部门各自负责
- 结论: 复杂度的根源是"部门边界"，打破边界比增加跨部门协调人员更有效
- 结果: 客户问题响应时间从5天缩短至18小时
A2 — 触发场景 (Future Trigger) ★
用户会在什么情境下需要这个 skill?
- 本能地想通过"加"来解决问题 — 遇到问题第一反应是"加个流程/加个人/加个部门"，而不是"能不能简化现有的"
- 公司扩张后反而效率下降 — 人多了、开会多了、审批多了，但产出没相应增加
- 新员工入职培训成本越来越高 — 因为需要了解的流程、制度、内部关系越来越复杂
- 核心员工开始离职/抱怨官僚 — "在公司做事太难了，流程走完机会都没了"
- 管理者发现自己越来越忙但团队效率低 — 管理者的忙是因为在协调复杂度而不是在创造价值
语言信号 (用户的话里出现这些就应激活)
- "我们需要加一个审批流程"
- "能不能再设一个管理层级"
- "公司大了感觉比创业还累"
- "流程越来越多效率越来越低"
- "每次定战略都要先走一堆内部流程"
- "新员工上手太慢了"
- "开会越来越多"
What ships with it
1 file 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.
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.
- 4d ago First seen · 162 lines · 131 tokens per session scan A fe1f961f5939
complexity-enemy is a skill published in the GitHub repository ace3000chao/book2startup (75 stars, last pushed 4mo ago), licensed MIT. It adds 131 tokens to every session and 2,527 once invoked, about $0.0007 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
reducing-entropy
Minimize total codebase size through ruthless simplification. Measure success by final code amount, not effort. Bias toward deletion.
software-code-review
Evaluate source code for correctness, quality, security, style conformance, and maintainability, producing a structured review report with findings and recommendations. Use when the user wants to review, critique, audit, evaluate, or inspect source code — checking for bugs, logic errors, unhandled error paths…
absolute-simplify
Use when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path. Reduces complexity, flattens nesting, removes redundancy and dead code, scores each change by value (holding low-value churn), then runs tests to prove nothing broke. Invoke on…
cognitive-accessibility
Improve content and workflows for users with varied attention, memory, and executive function profiles. Use when user asks to 'simplify content', 'reduce cognitive load', 'improve readability', 'chunk content', 'make accessible for ADHD', 'help with focus'.
code-simplification
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
refactor-agent
Safe, systematic code refactoring — extract functions, reduce complexity, eliminate duplication, improve naming. Use when improving code structure without changing behavior.