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/funiq-lab/your-mind/daily-workflownpx skills add funiq-lab/your-mind --skill daily-workflowgit clone --depth 1 https://github.com/funiq-lab/your-mindWrote 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/funiq-lab/your-mind/daily-workflow)<a href="https://agentmods.dev/skills/funiq-lab/your-mind/daily-workflow"><img src="https://agentmods.dev/badge/skills/funiq-lab/your-mind/daily-workflow.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.00057 | $0.00481 |
| Opus 5 | $0.00028 | $0.00241 |
| Sonnet 5 | $0.00011 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
daily-workflow 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 5d 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.
What it actually says
每日工作流
适用范围：life-os/ 目录
晨间流程 (5-10 分钟)
自动步骤
- 创建今日笔记（如不存在）
- 拉取昨日未完成任务
- 回顾周目标
提问
- "今天的 ONE Thing 是什么？"
- "可能会有什么阻碍？"
清单
- 每日笔记已创建
- ONE Thing 已确定
- 时间块已设置
午间检查 (2-3 分钟)
快速回顾
- 上午任务完成情况
- 当前能量水平
- 下午优先事项
提问
- "现在能量状态如何？"
- "下午最重要的事是什么？"
晚间收尾 (5 分钟)
记录
- 标记已完成任务
- 记录能量水平 (1-10)
- 记录感恩事项
反思
- 今天什么做得好？
- 什么可以改进？
- 学到了什么？
准备
- 预览明天优先事项
- 移动未完成任务
- 提交变更
每日笔记结构
# {{date}}
## Focus
> ONE Thing
## 时间块
- 🌅 上午:
- ☀️ 下午:
- 🌙 晚间:
## 任务
### 必须完成
- [ ]
### 工作
- [ ]
### 个人
- [ ]
## 笔记
## 反思
- **亮点:**
- **挑战:**
- **学到:**
- **感恩:**
- **能量:** /10
相关规范
→ docs/references/life-os/productivity-workflow.md
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.
- 5d ago First seen · 91 lines · 57 tokens per session scan A 0fbfdaf5a02c
daily-workflow is a skill published in the GitHub repository funiq-lab/your-mind (11 stars, last pushed 8mo ago), licensed MIT. It adds 57 tokens to every session and 481 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…