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 habits-quarterly-rotationgit 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/habits-quarterly-rotation)<a href="https://agentmods.dev/skills/ace3000chao/book2startup/habits-quarterly-rotation"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/habits-quarterly-rotation/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/habits-quarterly-rotation"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/habits-quarterly-rotation.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.00158 | $0.03319 |
| Opus 5 | $0.00079 | $0.01659 |
| Sonnet 5 | $0.00032 | $0.00664 |
| Haiku 4.5 | $0.00016 | $0.00332 |
Grade A, and why
habits-quarterly-rotation 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Habits Quarterly Rotation(习惯季度轮换)
R — 原文 (Reading)
"You'll drive everyone crazy if you implement all these habits at one time. The key is focusing on one or two each quarter, giving everyone roughly 24 to 36 months to install these simple routines."
— Verne Harnish, Scaling Up, 第1章
I — 方法论骨架 (Interpretation)
核心原则:少即是多,慢即是快
Scaling Up的Rockefeller Habits有几十个(从日站会、周例会、一对一、季度主题到年度BHAG),但Verne Harnish最核心的执行警告是:永远不要同时推行超过2个新习惯。
为什么季度轮换是正确节奏?
组织学习新行为如同个人学习新习惯——需要认知(理解为什么)、行为(刻意练习)、强化(看到正反馈)三个阶段。Verne Harnish给的时间是每个习惯24-36个月才能真正"安装"进组织血液。这不是夸张:麻省理工的研究表明,一个新的神经回路形成并固化为自动行为至少需要66天,组织层面需要更长时间。
季度轮换的机制:
- 每季度选择1-2个Rockefeller Habits作为焦点
- 给予团队完整的一个季度去"习惯"这1-2个习惯——不是完美执行,而是让它成为默认选项
- 季度末复盘:习惯是否已经成为团队DNA?如果是,进入下一组;如果否,延长或调整
- 24-36个月后,组织将拥有一整套Rockefeller Habits而不感到任何单次冲击
与"敏捷迭代"的区别: 敏捷强调快速短周期(2周Sprint),但这是任务执行层面的迭代;习惯季度轮换是组织文化层面的慢变量。两者的节奏不能混淆。
A1 — 书中的应用 (Past Application)
案例 1: 赛仕软件的"会议节食"
- 问题: 赛仕软件(SAS Institute,全球最大私有软件公司)在成长过程中积累了大量低效会议——周例会、月度汇报、季度规划,名目繁多,管理者和员工每周花费超过20小时在会议上,实际执行时间被压缩。
- 方法论的使用: CEO Jim Goodnight决定推行"会议节食"(Meeting Diet)——每季度只解决一个问题:减少15%的会议时间。第一个季度只做一件事:取消所有不足30分钟的一对一 "status update" 会议(保留充分时长的一对一辅导会议)。其他会议制度暂时不动。
- 结论: 季度轮换让团队有时间消化每一个改变,而不是在多个变革中迷失方向。
- 结果: 18个月内,SAS将每周平均会议时间从22小时降至8小时,员工满意度显著提升,同时产品交付速度加快。
案例 2: 某连锁餐饮的"日站会"失败与成功
- 问题: 一家30家门店的连锁餐饮企业,CEO读到Rockefeller Habits后,决定一个月内在所有门店推行"日站会"——每天早上9点用10分钟视频同步昨日数据、当日重点和突发问题。一个月后,80%的门店站会名存实亡,要么5分钟结束没有任何实质内容,要么直接跳过。
- 方法论的使用: CEO重新启动,但这次采用季度轮换——Q1只做一件事:总部高管每天早上9点(全国统一时间)开15分钟站会,CEO亲自参加,30天后高管习惯建立。Q2将站会扩展到区域经理,总部高管退到观察员角色。Q3才扩展到门店店长。只有当上一层级完全习惯后,才往下推进一层。
- 结论: 习惯推行速度太快会让团队产生"变革疲劳"(change fatigue),最终所有习惯一起抵制。
- 结果: 两年的时间,全公司所有门店实现了真正的日站会文化,门店间信息同步时间从平均3天缩短到实时。
案例 3: Intuit的"季度主题"
- 问题: Intuit在90年代快速增长期,产品线增多(Quicken、TurboTax、QuickBooks),每个产品团队各自为政,战略优先级互相冲突。公司需要统一焦点但又不能扼杀创新。
- 方法论的使用: CEO Scott Cook引入"季度主题"(Quarterly Theme)制度——每个季度公司只确定一个核心主题(如"本季度主题:客户满意度"),所有产品路线图、营销活动、招聘目标都围绕这个主题对齐。其他重要的initiatives暂时搁置或降级。每个季度末,主题自动"过期",除非重新被选为下一个季度主题。
- 结论: 季度主题本质上是习惯季度轮换在战略优先级的应用——让组织在每个季度只专注1个核心议题,不是什么都重要,而是"这个季度最重要"。
- 结果: Intuit的收入从1993年的100万美元增长到2000年的10亿美元。
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 · 153 lines · 158 tokens per session scan A e0ca679a7c89
habits-quarterly-rotation is a skill published in the GitHub repository ace3000chao/book2startup (80 stars, last pushed 4mo ago), licensed MIT. It adds 158 tokens to every session and 3,319 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.
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).
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…