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 ace3000chao/book2startup --skill 10-rockefeller-habitsgit 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/10-rockefeller-habits)<a href="https://agentmods.dev/skills/ace3000chao/book2startup/10-rockefeller-habits"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/10-rockefeller-habits/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/ace3000chao/book2startup/10-rockefeller-habits"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/10-rockefeller-habits.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.00166 | $0.02659 |
| Opus 5 | $0.00083 | $0.01329 |
| Sonnet 5 | $0.00033 | $0.00532 |
| Haiku 4.5 | $0.00017 | $0.00266 |
Grade A, and why
10-rockefeller-habits 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 11d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
10 Rockefeller Habits（洛克菲勒10大习惯）
R — 原文 (Reading)
"There are 10 fundamental habits that support the successful execution of your strategy — habits that haven't changed for 100 years since John D. Rockefeller implemented them."
— Vern Harnish, Scaling Up, 第1章
I — 方法论骨架 (Interpretation)
洛克菲勒10大习惯是一套经过百年验证的企业执行基础设施清单。 不是"建议"，而是"做过的人证明有效"的硬核习惯。
底层逻辑：企业做不大，往往不是因为战略不对，而是因为执行系统不行。 执行系统靠习惯，不靠英雄。创始人亢奋时不缺执行力，难的是把这种状态 固化成不依赖个人状态的团队节奏。
十大习惯分三类：
一、高管团队对齐（1-2条）
- 核心是让"那几个人"（3-5个核心高管）始终在一个节奏上， 减少组织内的"信息不对称损耗"
二、节奏与透明度（3-6条）
- 核心是把"优先级"、"进展"、"问题"变成可见的物理节奏， 而不是靠个人自觉或临时拉会
三、输入与迭代（7-10条）
- 核心是从员工、客户、价值观中持续获取真实信号， 防止组织在"内部叙事"中自我麻痹
执行的关键：不是"知道这10条"，而是"每个季度专注落地1-2条"， 贪多嚼不烂。这不是一次性工程，而是持续迭代。
A1 — 书中的应用 (Past Application)
案例 1: 洛克菲勒本人的验证
- 问题: 19世纪末标准石油已经是世界上最大的公司之一， 如何在规模和复杂度爆炸的情况下依然保持执行效率？
- 方法论的使用: 洛克菲勒建立了这套习惯体系——固定会议节奏、 季度优先事项、员工匿名反馈、量化评分等——在150年前就实践了
- 结论: 这些习惯不是"现代管理发明"，而是穿越百年的有效实践
- 结果: 标准石油在超大规模下仍保持惊人的运营效率
案例 2: 季度单一主题（Hoshin Kanri的雏形）
- 问题: 企业同时推进太多战略主题，导致资源分散， 每一项都推进不彻底
- 方法论的使用: 洛克菲勒习惯中的"季度单一优先事项"—— 每个季度只选一个核心主题全公司聚焦，其他一切服从这个主题
- 结论: "少即是多"——季度内集中全部资源攻一个山头， 比同时推三个山头效率高得多
- 结果: 大幅提升战略主题的完成率，增强团队信心
案例 3: 员工输入与客户反馈闭环
- 问题: 组织大了之后，一线员工和客户的真实声音传不到决策层， 高层在"内部叙事"中做决策
- 方法论的使用: 洛克菲勒习惯中的匿名员工调查和客户满意度系统—— 定期强制收集、量化、追踪，形成反馈闭环
- 结论: "没有测量就没有管理"——感觉到的文化问题 用数据验证，感觉到的客户不满用NPS验证
- 结果: 及时发现文化退化和客户满意度下滑，避免"后知后觉"
A2 — 触发场景 (Future Trigger) ★
用户会在什么情境下需要这个 skill?
- 高管团队开会效率低、议而不决——每次开会都是 "重新讨论上次的问题"，没有积累，决策质量靠个人而非机制
- 战略和执行两张皮——年度战略大会开完了， 战略停在PPT上，日常运营还是按惯性走
- 员工不知道公司现在最重要的事是什么—— 每个人都有自己的理解，没有统一的优先级框架
- 团队规模超过15人，出现"信息衰减"问题—— 创始人的意图往下传三层就走样了
- 需要建立一套"不用创始人盯"的运营节奏—— 创始人不在公司的时候，团队依然按节奏运转
语言信号 (用户的话里出现这些就应激活)
- "战略定了，但执行总是打折扣"
- "开会挺多的，但好像没什么用"
- "员工好像不知道公司在忙什么"
- "我们需要一个方法来让团队聚焦"
- "老板不在，项目就停了"
- "客户投诉很多，但我们好像改不上去"
- "团队感觉没有合力，各干各的"
- "有什么方法可以让运营更系统化？"
与相邻 skill 的区分
- 与
PACe（流程问责表）的区别: PACe解决"谁对哪个流程负责"的问题； Rockefeller Habits解决"高管团队用什么节奏来驱动整个组织运转"的问题。 PACe是执行层的分工，Habits是高层的节奏设计 - 与
4D Framework的区别: 4D是"想什么"的元框架； Rockefeller Habits是"Disciplines维度"的具体落地清单 - 与
OPSP（一页战略计划）的区别: OPSP是战略输出工具； Rockefeller Habits是战略执行的基础设施。
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.
- 11d ago First seen · 202 lines · 166 tokens per session scan A 43ab5ad05bb1
10-rockefeller-habits is a skill published in the GitHub repository ace3000chao/book2startup (80 stars, last pushed 4mo ago), licensed MIT. It adds 166 tokens to every session and 2,659 once invoked, about $0.0008 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
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
flow-next
Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for planning or executing (use the plan and work skills).