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 yunsii/wezdeck --skill habit-weeklygit clone --depth 1 https://github.com/yunsii/wezdeckWrote 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/yunsii/wezdeck/habit-weekly)<a href="https://agentmods.dev/skills/yunsii/wezdeck/habit-weekly"><img src="https://agentmods.dev/badge/skills/yunsii/wezdeck/habit-weekly/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/yunsii/wezdeck/habit-weekly"><img src="https://agentmods.dev/badge/skills/yunsii/wezdeck/habit-weekly.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.00140 | $0.02232 |
| Opus 5.5 | $0.00056 | $0.00893 |
| Sonnet 5.5 | $0.00028 | $0.00446 |
| Haiku 4.5 | $0.00014 | $0.00223 |
Grade A, and why
habit-weekly 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 2d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Habit weekly(仓库内 skill — 开发习惯周报)
Who runs: the coding agent, not the human.
Never ask the human to paste habit-report.sh as the primary path — load this skill and run the co-located runner.
Scope: WezDeck 仓库内 skill(skills/habit-weekly/)。由 AGENTS.md 路由加载;不经 link-platform-skills.sh 同步到 ~/.agents/skills / ~/.claude/skills(依赖本仓 habit-report.sh,用户级软链会把 repo_root 算错)。
数据收集器是 scripts/dev/habit-report.sh(插件化 Claude / Grok / Codex + 可选 WakaTime)。本 skill 负责:定窗口 → 拉 JSON → 按固定模板渲染周报 →(可选)落盘 →(显式)推送到习惯归档仓。
When to load / run
| 用户意图 | 你做 |
|---|---|
| 开发习惯周报 / 习惯周报 / habit weekly | run.sh(默认上一完整 Mon–Sun;若归档仓落后则 catch-up 接到上次 until+1;默认含 WakaTime) |
| 上周习惯 / last week | run.sh 或 run.sh --week last(与默认相同,含 catch-up) |
| 只要单周、不要接假期缺口 | run.sh --no-catch-up |
| 本周迄今 / this week | run.sh --week this(Mon→today,未完结周;不做 catch-up) |
| 自定义区间 | run.sh --since YYYY-MM-DD --until YYYY-MM-DD(显式窗口,跳过 catch-up) |
| 只要原始 JSON | run.sh --json-only |
| 落盘归档(本机) | run.sh --write(再 --stdout 可同时打印正文) |
| 落盘并推送到私有习惯仓 | run.sh --write --push(--push 隐含 --write) |
Skip / redirect:
- 团队业务周报(commit / TAPD / 飞书)→ coco-weekly-report(不是本 skill)
- 只要某一天的时间线事件流 →
workflow-timeline.sh - 只要热键表、不要 Agent 段 →
habit-report.sh --no-hotkeys的反义词是--providers裁剪;仍可用本 skill 再口头删段
Resolve TOOL_HOME
1. $HABIT_WEEKLY_HOME(显式覆盖)
2. $WEZDECK_REPO/skills/habit-weekly(本机主仓)
3. 本 SKILL.md 同目录(skills/habit-weekly,run.sh 共存)
4. $WEZDECK_ROOT/skills/habit-weekly
TOOL_HOME="${HABIT_WEEKLY_HOME:-$WEZDECK_REPO/skills/habit-weekly}"
R="$TOOL_HOME/run.sh"
run.sh 用 pwd -P 解析自身目录,并以 $WEZDECK_REPO(若含 scripts/dev/habit-report.sh)优先定仓库根。不要从 ~/.agents/skills/habit-weekly 启动。
Agent procedure
- 定窗口(用户没说则默认上一完整 Mon–Sun;未完结周须显式
--week this):- 默认 / 上周完整周 → 不传或
--week last - Catch-up(默认开):读归档仓最新
habit-weekly-*_to_<until>.md;若until+1早于默认窗口起点(假期 / 漏跑),把since前移到until+1,until仍为上完整周日——一份报告接缺口,不要再问用户切不切开。--no-catch-up可关;显式--since/--until与--week this不做 catch-up。 - 本周迄今(未完结)→
--week this - 点名日期 →
--since/--until,或--week YYYY-MM-DD(取该日所在周 Mon–Sun)
- 默认 / 上周完整周 → 不传或
- 跑收集 + 渲染(优先
--write落盘;用户要远端归档时再加--push):
仅本机落盘:"$R" --write --push
未完结本周(少用):"$R" --write"$R" --week this --write - 读
references/REPORT_STYLE.md,核对渲染稿是否需补一句人话结论(数字已被模板写好;只在环路归纳与分工上可加 1–2 句,禁止改数字)。窗口若因 catch-up 超过 7 天,结论里可点一句「含假期/空档」。 - 汇报:把 markdown 正文(或落盘路径 + 摘要)用简体中文交给用户。披露数据窗口、
max_running口径(pane+TTL)、WakaTime 是否成功、是否发生了 catch-up。
What ships with it
4 files 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.
- 2d ago Changed · +3 lines 9044dc999e42
- 20d ago Changed eab84c956e37
- 24d ago Changed · -4 lines 6603971c588a
- 27d ago Changed · +7 lines · +16 tokens per session 4bf6c9eabc80
- 28d ago First seen · 126 lines · 124 tokens per session scan A 177bb497de08
habit-weekly is a skill published in the GitHub repository yunsii/wezdeck (5 stars, last pushed yesterday), licensed MIT. It adds 140 tokens to every session and 2,232 once invoked, about $0.0006 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-09-18.
Other skills, from other repositories
workflow
Create, run, monitor, cancel, or resume deterministic JavaScript workflows that orchestrate multiple Codex, Claude, Cursor, or Kimi agents. Use for parallel investigation or review, staged agent pipelines, resumable long-running work, or when the user explicitly asks for a workflow, orchestration, fan-out, or several…
orchestrate
Use only when the user explicitly types /orchestrate:orchestrate to decompose a large task, spawn a tree of parallel worker/subplanner/verifier subagents, and collect structured handoffs. Do not invoke autonomously.
launch
Launch and automate VS Code (Code OSS) using agent-browser via Chrome DevTools Protocol. Use when you need to interact with the VS Code UI, automate the chat panel, test UI features, or take screenshots of VS Code. Triggers include 'automate VS Code', 'interact with chat', 'test the UI', 'take a screenshot', 'launch…
accessibility
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
sessions
Agent Sessions window architecture — covers the sessions-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agent Sessions window.
component-fixtures
Use when creating or updating component fixtures for screenshot testing, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, and common pitfalls.