What is wezdeck-runtime-ops?

A set of checks and synchronization procedures for the WezDeck runtime, including WezTerm, tmux, Lua configuration, dependencies, and agent tools.

Use it to run read-only environment checks, find or confirm a target installation, synchronize runtime configuration, and perform post-sync diagnostics.

It provides a defined way to diagnose the environment and sync runtime files while reusing a valid target when possible.

wezdeck-runtime-ops — Skill for Codex by yunsii/wezdeck

Install

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.

Any agent

npx skills add yunsii/wezdeck --skill wezdeck-runtime-ops

Clone the repo

git clone --depth 1 https://github.com/yunsii/wezdeck

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yunsii/wezdeck/wezdeck-runtime-ops/github.svg)](https://agentmods.dev/skills/yunsii/wezdeck/wezdeck-runtime-ops)

Your own site

<a href="https://agentmods.dev/skills/yunsii/wezdeck/wezdeck-runtime-ops"><img src="https://agentmods.dev/badge/skills/yunsii/wezdeck/wezdeck-runtime-ops/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yunsii/wezdeck/wezdeck-runtime-ops"><img src="https://agentmods.dev/badge/skills/yunsii/wezdeck/wezdeck-runtime-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,592 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.01592
Opus 5.5	$0.00000	$0.00637
Sonnet 5.5	$0.00000	$0.00318
Haiku 4.5	$0.00000	$0.00159

Measured 17d ago against content hash fb36d7d03278, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wezdeck-runtime-ops 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 17d ago.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/check-runtime.sh, scripts/sync-helper-windows-lib.sh, scripts/sync-prompt-lib.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/wezdeck-runtime-ops/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

WezDeck Runtime Ops

Use this skill for WezDeck environment checks and runtime sync. The check path is read-only and does not need a target home. The sync path writes the selected runtime target and owns canary publication, helper ensure, Lua prechecks, tmux reload, and post-sync diagnostics.

The scripts under skills/wezdeck-runtime-ops/scripts/ are the source of truth for sync prompting, target discovery, and prompt-format regression checks.

Workflow

Run from the repository root, or set WEZDECK_REPO=/absolute/path/to/repo (legacy WEZTERM_CONFIG_REPO still accepted) before invoking the skill scripts.
Run the read-only environment check when diagnosing or closing a runtime round:
```
skills/wezdeck-runtime-ops/scripts/check-runtime.sh
```
Use --advisory for a non-blocking report and --skip-deps when the network is unavailable. This check owns the aggregate view of Lua source syntax and managed config precheck, the configured agent CLI binary, agent hooks, the WSL agent-tools.env capability marker, launcher permission overlays, resume-command/workspace-agent-map lockstep, Node/fnm runtime state, interactive shell-env.d injection (wezdeck-env.env + the wezdeck:shell-env.d zsh snippet + grok as the focus-filter function), the WSL bridge binary (scripts/dev/check-wezdeck-wsl.sh: native/wezdeck-wsl/bin/wezdeck-wsl + local socket smoke, and live GET /api/v1/wsl when the Runtime HTTP surface is up), the optional Rime commit counter, and WezTerm/tmux/Go dependency floors. The Rime check is advisory: when a Windows Rime user directory is present but the counter is not installed, it prints the install command without blocking the base runtime check. The shell-env and wezdeck-wsl checks are gates here; shell-env is only an advisory warning during sync (WEZTERM_SYNC_SKIP_SHELL_ENV_CHECK=1 skips that warning).
Default sync stages a canary tree, auto-launches an isolated WezTerm probe, and promotes to live only if healthy.stamp appears (otherwise live is untouched and sync exits 1). Skip probe with WEZTERM_SYNC_SKIP_CANARY_AUTO=1. Use --live to publish straight to the running GUI. Details: docs/daily-workflow.md. Windows targets are preflighted with a real powershell.exe probe before any canary files are written; if WSL interop is disabled, sync exits with the /etc/wsl.conf and wsl --shutdown repair steps.
If repo-root .sync-target or WEZTERM_SYNC_TARGET already points at an existing directory, run skills/wezdeck-runtime-ops/scripts/sync-runtime.sh with no extra arguments.
If there is no valid cached target, run skills/wezdeck-runtime-ops/scripts/sync-runtime.sh --list-targets to print candidate user home directories.
Present the candidates to the user and ask which path should be used. Accept either one of the listed paths or another absolute path the user explicitly provides.
After the user confirms a target, run skills/wezdeck-runtime-ops/scripts/sync-runtime.sh --target-home /absolute/path.
Summarize the check and sync results, including warnings, canary outcome, and the chosen target path.

Read the full file on GitHub · 82 lines

Files

What ships with it

8 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.

Changes

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.

17d ago Changed fb36d7d03278
19d ago Changed 510ac85be117
20d ago First seen · 82 lines · 0 tokens per session scan A 5961e02e0762

Subscribe to this mod's changes

wezdeck-runtime-ops is a skill published in the GitHub repository yunsii/wezdeck (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,592 tokens. 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-26.

Claude Code DevOps and cloud agent-orchestration ai-agents codex developer-tools git-worktree

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…

xxxoooxoxo/wiff · 70 tokens

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.

odysseus0/claude-orchestrate · 54 tokens

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…

workstream-labs/workstreams · 80 tokens

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.

workstream-labs/workstreams · 54 tokens

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.

workstream-labs/workstreams · 45 tokens

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.

workstream-labs/workstreams · 47 tokens