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 rexchengm/fios-skills --skill notion-life-cascadegit clone --depth 1 https://github.com/rexchengm/fios-skillsWrote 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/rexchengm/fios-skills/notion-life-cascade)<a href="https://agentmods.dev/skills/rexchengm/fios-skills/notion-life-cascade"><img src="https://agentmods.dev/badge/skills/rexchengm/fios-skills/notion-life-cascade/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/rexchengm/fios-skills/notion-life-cascade"><img src="https://agentmods.dev/badge/skills/rexchengm/fios-skills/notion-life-cascade.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.00225 | $0.05079 |
| Opus 5.5 | $0.00090 | $0.02032 |
| Sonnet 5.5 | $0.00045 | $0.01016 |
| Haiku 4.5 | $0.00022 | $0.00508 |
Grade A, and why
notion-life-cascade 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 1mo 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notion 生活向下拆解（Life Cascade）
概述
FIOS 中自上而下逐层规划的"向导层"。四条链路：
- 执行链路：目标设定 → 规划设定 → 项目执行 → 任务执行
- 学习链路：兴趣学习/书籍阅读 → 学习笔记/书籍笔记
- 创作链路：选题收集 → 创作计划 → 任务执行
- 习惯设置：习惯分类 → 日常打卡/次数打卡
L1 目标设定 遵循 FIOS 目标管理助手方法论——严格按 ANALYZE → DESIGN → EXECUTE → FORMAT 流程。更低层级使用更轻量的循环。所有 schema 查询、读取与写入都经由 notion-life-system。
REQUIRED BACKGROUND（必备前置）： notion-life-system —— 提供 ntn CLI、scripts/notion_query.zsh、scripts/notion_page_io.zsh、references/notion-intake-rules.json。
何时使用
典型场景：
- "帮我设定 2026 目标" / "做年度规划" / "拆下半年规划" / "拆这个目标"
- "为'工作愿景'拆几个规划" / "为这个规划列项目" / "为这个项目列任务"
- "为《XXX》做笔记规划" / "为这个技术学习做笔记计划"
- "新选题 / 安排创作 / 把这个选题挂到创作计划"
- "设个新习惯，每周三次 / 每天必做"
不要用于：一次性记录（走 notion-life-system 入库）、每日复盘（走 notion-life-reflection）、跨库分析（走 notion-life-insights）。
目标方法论（仅 L1 执行链路）
以下规则来自 FIOS 目标管理助手。更低层级（L2–L4）和其他链路不需要这套。
顶层用「领域」，专项降为规划（重要约定）
FIOS 顶层目标只用「领域」年度目标（三层级）：事业精进 / 知识沉淀 / 健康基线 / 关系经营 / 财务稳健 等。具体专项（甲方项目、产品发布、认证考试…）不要建成跟领域平级的🎯目标，一律作为对应领域下的「规划」。例：必扑甲方项目 → 事业精进下规划；FIOS 公开发布 → 事业精进下规划；精力管理 → 健康基线下规划。
- 自下而上挂靠：已完成/进行中的工作要记录时，先 Survey 找对应领域目标 → 挂到它下面的规划/项目，别新开平级目标。
- 降级注意层级：FIOS 固定 4 层（领域目标→规划→项目→任务）。专项若已用满 4 层，降级时压缩（原阶段规划→项目、原项目→任务），别让最底层溢出第 5 层。
- 空壳领域（只有领域目标、还没规划）下要挂任务，必须先建规划+项目层，不能把任务直接挂到领域目标。
三层级 vs 四层级
| 三层级 | 四层级 | |
|---|---|---|
| 适用 | 人生领域年度系统化（学习/工作/健康/生活/财务等） | 具体单一目标专项（考研/认证/产品交付/活动） |
| 周期 | 年度（≈365 天） | 季度到年度 |
| 拆解 | 按子领域 / 主要方向 → 多个规划 | 按 OKR Key Results → 多个规划 |
| 预定规划数 | 3–5 | 2–4 |
标题格式
- 三层级:
🎯 [领域]-[年度成果]例如🎯 学习领域-建立系统化知识管理体系 - 四层级:
🎯 [具体目标名称]例如🎯 通过 PMP 认证考试
三阶段规划（年度目标）
| 期 | 月数 | 关键规划数 | 每规划周期 | 主要四象限 |
|---|---|---|---|---|
| 基础启动期 | 1–3 月 | 2–4 | 2–4 周 | 重要紧急 + 重要不紧急 |
| 加速发展期 | 3–6 月 | 3–5 | 1–2 月 | 重要不紧急 |
| 深化巩固期 | 6–12 月 | 2–3 | 2–3 月 | 重要不紧急的系统建设 |
预定规划数 = 三阶段合计（三层级 ≈ 7–12，四层级 ≈ 5–9；用户可手动调）。
量化指标
每个 L1 目标必须在页面正文表格中写入 3 个以上指标： 核心指标 | 具体标准（数字+单位）| 验收方式 | 达成时间
现状分析（4 个维度）
- 能力基线: 现有技能水平 / 经验积累 / 知识储备
- 优势资源: 可利用的内外部资源 / 工具 / 人脉 / 平台
- 差距识别: 现状与目标的关键差距
- 风险: 内部（能力/时间/精力/动机）+ 外部（环境/竞争/政策）+ 缓解策略
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.
- 1mo ago First seen · 289 lines · 225 tokens per session scan A d92fe43c6d75
notion-life-cascade is a skill published in the GitHub repository rexchengm/fios-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 225 tokens to every session and 5,079 once invoked, about $0.0009 per session on Opus 5.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-31.
Other skills, from other repositories
scenario-zbrush-expert
Use when an agent drives Maxon ZBrush 2026 for any task (sculpt in ZBrush, DynaMesh, ZRemesher, UVs, export, polypaint, posing, 3D print, clean up an AI mesh in ZBrush), when writing ZBrush Python (zbrush.commands) or ZScript, when the ZBrush bridge is not answering, a palette path or set() does nothing, a scripted…
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
outcome-tracker
Record the testable predictions inside a decision, then score them against reality later — so frameworks earn trust from outcomes, not vibes. Use when committing to a prioritisation, forecast, or plan (to log what it predicts), when asked to review what actually happened, or to compute how well-calibrated past RICE…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
explorer-pipeline
Use when asked to make an interactive 3D explorer of a topic from start to finish, go from a topic to a clickable 3D learning page, or run the whole 3D explorer process. Produces a staged run of explorer-interface-brief, model-prompt-pack and explorer-viewer-builder in order for one topic, with the hand-offs between…