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-reflectiongit 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-reflection)<a href="https://agentmods.dev/skills/rexchengm/fios-skills/notion-life-reflection"><img src="https://agentmods.dev/badge/skills/rexchengm/fios-skills/notion-life-reflection/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-reflection"><img src="https://agentmods.dev/badge/skills/rexchengm/fios-skills/notion-life-reflection.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.00172 | $0.03346 |
| Opus 5.5 | $0.00069 | $0.01338 |
| Sonnet 5.5 | $0.00034 | $0.00669 |
| Haiku 4.5 | $0.00017 | $0.00335 |
Grade A, and why
notion-life-reflection 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notion 生活复盘（Life Reflection）
概述
为用户的 每日复盘 / 每周复盘 / 每月复盘 页面起草复盘叙述，并追加到页面正文（不写入字段，依用户偏好）。复盘页面已经通过 rollup 和公式聚合了指标；用户的自动流水线保持每日的关联字段连通。本 skill 把那些数字转成可读、扎根于用户真实数据的中文散文。
三个复盘数据库：
- 每日复盘 —— 有
洞察内容（rich_text）、情绪（select）、已归档（checkbox）、日期，以及 7 个 rollup（任务, 收入, 支出, 学习笔记, 专注时长, 资源）。 - 每周复盘 —— 没有手写字段；13 个 rollup + 10 个公式（周报显示, 周健康分析报告, 日复盘概览, 稳定性分析, 等）。
- 每月复盘 ——
状态（status）、复盘日期、9 个 rollup + 31 个公式（综合复盘报告, 财务与消费, 健康和娱乐, 任务与管理, 知识与记录, 稳定性分析, 每周复盘详情）。
所有草稿都通过 scripts/notion_page_io.zsh append 写到页面正文。绝不写入字段。
REQUIRED BACKGROUND（必备前置）： notion-life-system —— 提供 ntn CLI、scripts/notion_query.zsh、scripts/notion_page_io.zsh、references/notion-intake-rules.json。
何时使用
当用户明确发起复盘时使用：
- 今日复盘 / 写日记 / 今天怎么样 / 今日洞察 / 想反思一下今天
- 周复盘 / 周报 / 本周怎么样 / 本周总结
- 月复盘 / 月报 / 这个月怎么样 / 月度总结
- 反思一下（含糊 → 反问是哪个范围）
不要用于：
- 设定目标或拆解规划 → notion-life-cascade
- 一次性记录（花钱了, 跑步了）→ notion-life-system 入库
- "本周对比上周 / 看监管数据 / 元气值如何" → notion-life-insights
- 直接编辑复盘页面字段（那些由用户的流水线管理）
核心循环 —— 4 步
每次复盘，按顺序执行。
-
Locate（定位） —— 按日期找到目标复盘页面。
- 每日:
scripts/notion_query.zsh 每日复盘 5，匹配日期= 今天（默认）或用户指定的日期。若无对应行，新建一条并设好日期；汇报后继续。 - 每周:
scripts/notion_query.zsh 每周复盘 5，匹配落在本 ISO 周（周一到周日）内的生成日期。没有就新建。 - 每月:
scripts/notion_query.zsh 每月复盘 5，匹配落在本自然月内的复盘日期。没有就新建。 - 把解析到的
page_id保留，供第 2、4 步用。
- 每日:
-
Read State（读状态） —— 拉取页面当前内容和渲染后的公式报告。
scripts/notion_page_io.zsh get <page_id>返回页面的 Markdown，包含公式渲染出的单元格（进度条、"周报显示" 散文等）。- 每日: 提取 任务已完成 / 总数, 收入金额, 支出金额, 学习笔记个数, 专注时长, 资源总数, 以及
情绪值。 - 每周: 提取 周报显示, 周健康分析报告, 日复盘概览, 稳定性分析, 加上 13 个 rollup 数字。
- 每月: 提取 综合复盘报告, 财务与消费, 健康和娱乐, 任务与管理, 知识与记录, 稳定性分析, 每周复盘详情。
- 留意已有的正文内容 —— 不要重复主题。
-
Draft（起草） —— 用用户的第一人称口吻写平实的中文散文。
- 起草前问用户少量问题（见下方分类小节）。可选项答案用 AskUserQuestion；开放题自由回答即可。每日: 1–3 个问题。每周: 0–1 个。每月: 0–1 个。
- 引用具体数字但要解读。"5 个任务完成 4 个，唯一没动的是 X" 胜过 "任务完成率 80%"。
- 平实段落，空行分隔。散文里不用 markdown 标题。不要 emoji 刷屏。
- 篇幅指引：
- 每日: 100–300 字（1 个亮点 + 1 个卡点 + 可选 takeaway）。
- 每周: 300–500 字（3 个主题: 执行 / 输入 / 状态; 收尾一句下周意图）。
- 每月: 500–1000 字（逐维度: 财务 / 任务 / 学习 / 健康 / 人际 / 内容; 收尾给下月一个优先项）。
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 · 167 lines · 172 tokens per session scan A b4c063071699
notion-life-reflection is a skill published in the GitHub repository rexchengm/fios-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 172 tokens to every session and 3,346 once invoked, about $0.0007 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…