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/yunsii/wezdeck/dev-tasknpx skills add yunsii/wezdeck --skill dev-taskgit clone --depth 1 https://github.com/yunsii/wezdeckWhat 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.00069 | $0.02148 |
| Opus 5 | $0.00034 | $0.01074 |
| Sonnet 5 | $0.00014 | $0.00430 |
| Haiku 4.5 | $0.00007 | $0.00215 |
Grade A, and why
dev-task 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 yesterday.
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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev task (allowlisted repos)
When
Write work only under allowlist (see AGENTS.md). Pure Q&A: skip. Other repos: refuse.
| Logical | Roots |
|---|---|
| 团队仓 | $HOME/work/team-repo, $HOME/work/.worktrees/team-repo |
| wezdeck | $HOME/github/wezterm-config (primary), optional .worktrees |
cwd policy (L0-12/13)
Core: personal projects → default mainline. wezdeck is the local instance.
| Repo | Default | Worktree when |
|---|---|---|
| wezdeck (personal) | primary master |
parallel, long experiment, isolated agent cwd, user asks |
| 团队仓 (team-ish) | claw-* under dirname(primary)/.worktrees/<repo>/ |
default isolation unless user overrides |
Path formula (when used): dirname(realpath(primary))/.worktrees/<basename(primary)>/<slug>/.
Architecture: openclaw/docs/agent-architecture.md.
Checklist
Same steps as AGENTS.md Write-task checklist (wezdeck may skip assess/create).
Scripts: dev-task-ledger.sh, claw-worktree.sh, claw-run.sh.
Assess → create (only when isolation/parallel needed)
./openclaw/scripts/claw-worktree.sh assess \
--title "<subject>" --domain "<area>" --scope "<hint>" [--days N] \
--cwd "$HOME/github/wezterm-config"
./openclaw/scripts/claw-worktree.sh create \
--title "…" --lifecycle task|dev|hotfix --domain "…" \
--cwd "$HOME/github/wezterm-config"
- Prefer-reuse same domain; never human
dev-*/task-*as write targets. - Reclaim never automatic after close (only if a worktree was used).
Rails & modes (user-facing)
| 轨 | 方式 | 旧 | Who codes | Main does |
|---|---|---|---|---|
| 人工 | H1 人直接 | A | User IDE | Ledger/验收 only |
| 人工 | H2 原生 Agent | A | Host grok/claude/codex | Assist only |
| Claw | C1 Main 自写 | B | Main (Main-Grok) | Implement + verify |
| Claw | C2 Handoff | C | Host CLI after handoff | Stop coding that cwd |
| Claw | C3 ACP 后端 | E | ACP → claude | codex | Spawn/close; single writer |
| — | D | D | — | Forbidden |
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.
- yesterday First seen · 186 lines · 69 tokens per session scan A f7a65346e0b8
dev-task is a skill published in the GitHub repository yunsii/wezdeck (5 stars, last pushed 5d ago), licensed MIT. It adds 69 tokens to every session and 2,148 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-31.
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.
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.
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.