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 instructions/yunsii/wezdeck/agents-mdgit 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.04226 | $0.04226 |
| Opus 5 | $0.02113 | $0.02113 |
| Sonnet 5 | $0.00845 | $0.00845 |
| Haiku 4.5 | $0.00423 | $0.00423 |
Grade A, and why
wezdeck AGENTS.md 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 3d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
This file is the project-level agent entry point.
User-level reusable agent profiles hosted under agent-profiles/ are separate and do not override this file unless a user explicitly points an external tool at them.
Loading Rule
Read AGENTS.md first, then open only the matching file under docs/. Read additional docs only when the current doc points to them or the task crosses that boundary.
Task Routing
- Setup, local prerequisites, or machine-local config:
Read
docs/setup.md. - Sync, reload, verification, or day-to-day maintenance:
Read
docs/daily-workflow.md. - Workspace definitions or workspace behavior:
Read
docs/workspaces.md. - Keybindings:
Read
docs/keybindings.md. - tmux UI, tab titles, status rendering, copy-mode, or visible terminal behavior:
Read
docs/tmux-ui.md. - Terminal Vim inside tmux: scroll that feels like page-skips, windows full of
@rows,'termsync'/ DEC 2026 under tmux DA2, orShift+dragjumping into copy-mode while editing: Readdocs/tmux-ui.md#vim-in-tmux(install / vimrc:docs/setup.md#vim-92-optional). - Grok Build fullscreen TUI: whole-transcript flash on
Alt+o/ pane focus, FocusGainedterminal.clear(), cream#eeeeeevs panebg_base, the PATH focus-filter (grok-with-focus-filter.sh --install:~/.grok/bin/grok→ wrapper,grok.real= ELF; required because zshrc prepends~/.grok/bin), why macOS WezTerm+tmux can look fine with the same heal (sub-frame client burst, not OS-exempt), why WSL→Windows still flashes even on a tiny pane,scripts/dev/repro-grok-focus-flash.sh, mouse-wheel feel under tmux (scroll_lines/scroll_mode=wheel/scroll_speedin~/.grok/config.toml), or Grok follow ▼ click dead while a stock-tmux macOS box works (MouseDown1Panemustsend-keys -Mwhenalternate_on/mouse_any_flag): Readdocs/tmux-ui.md#grok-build-in-tmux. - Window appearance presets (
opaque/frosted), transparency / frosted-glass,win32_system_backdrop,window_background_opacity, theWEZTERM_APPEARANCE_PRESETselector,render-tmux-appearance.sh, or the tab-bar / pane / status background colors that make the frosted look cohere: Readdocs/appearance-presets.md. - Choosing or revisiting the inner multiplexer (tmux vs herdr), or planning
feature work that a tmux upgrade could absorb — the tmux 3.8 borrow list
(OSC 133 pane events, floating / modal panes,
set-hook -Bmonitors, theme reporting,#{A/count:frames}), the measured herdr 0.8.0 numbers (per-session server memory, session-level focus, sidebar limits, no#(shell)equivalent, no ad-hoc popup CLI), and why the 2026-08-18 evaluation ended with tmux staying: Readdocs/multiplexer-comparison.md. - Agent-attention pipeline: Claude hook install / upgrade, attention.json
schema and transitions, tab badges + right-status counters, focus-based
auto-ack, the
Alt+j/Alt+k/Alt+l/Alt+Shift+l/Alt+/keyboard entry points, or Codex integration: Readdocs/agent-attention.md. - Timed reminders (cron-driven tmux popups), the
reminder.sh/tmux-popup-active.shwrappers, or thewezterm-x/local/crontabinstall workflow: Readdocs/reminders.md. - Phone / Android remote work (OpenClaw only; Happy + Tailscale phone
shell retired 2026-07), tmux window-size limits, Termux IME notes:
Read
docs/mobile-access.md. - Headless Chrome debug instance, auto-start behavior,
Alt+b/Alt+Shift+b,chrome://inspectworkflow, or the right-statusCDP·…badge: Readdocs/browser-debug.md. - Cutting a Windows host-helper release, updating
release-manifest.json, forcing the release-install branch, or side-loading the release zip: Readdocs/host-helper-release.md. - Cutting a Go picker (
native/picker/) release, updating its multi-assetrelease-manifest.json, or the install-side fetcher (WEZTERM_PICKER_INSTALL_SOURCE=auto|local|release) that lets end users without Go consume the prebuilt tarball: Readdocs/picker-release.md. - Diagnostics, logs, or smoke tests (operator surface — env knobs,
file paths, troubleshooting); also guest-OOM hardening in all three of its
shapes — the whole distro vanishing / restarting on a fixed interval, the
reclaim livelock that pins every core, kills nothing, and leaves no OOM
record, and the high-order (
order:7/vmbus_alloc_ring) allocation failure that kills the vsock channel and makes Windows reboot the whole VM while swap still looks healthy (wsl-oom-guard.sh, thewezterm-oom-protect/wezterm-oom-recordunits, theM·…/S·…memory badge, the fragmentation axis with its compact-then-SIGTERM relief, andinstall-earlyoom.sh); also host disk space (host volume full,ext4.vhdxgrowing but never shrinking, why--set-sparseis a trap,fstrim→wsl --shutdown→Optimize-VHD/compact vdisk, build-artifact inventory, OEM preinstalls, and thewsl-disk-guard.shsampler +D·…headroom badge); also the standing-memory baseline for agent-side processes (per-session MCP cost, thechrome-devtools-mcpunbounded-heap leak and itsuxccontainment,uxc-session-reaper.sh, and why the Claude Code and OpenClaw sides are deliberately asymmetric); also the IDE-side TypeScript language server (tsgo/typescript.experimental.useTsgo) — whymaxTsServerMemorydoes nothing to it, howjs/ts.server.goMemLimitset below the live heap trades ~4 Gi of memory for a permanent ~1.5-core GC burn, the RSS-flat / faults-near-zero signature that identifies it, why onlyDeveloper: Reload Windowapplies a change to that key, and why the uncappedtsgothat Claude Code spawns on its own must be left uncapped: Readdocs/diagnostics.md. - Unverified claims, deferred decisions, or "what still needs following up" on
any of the above — dated, each with how to close it:
Read
docs/diagnostics.md#open-questions. Record new ones there rather than only in a commit body, which is not reviewable day to day. - Cross-host development environment failures involving Windows, WSL, DNS,
VPN/proxy software, shells, or agent CLIs; also the first-triage path when
the whole WSL distro disappears at once (distro restart vs VM reboot):
Read
docs/development-environment-troubleshooting.md. - Adding or modifying a logger callsite, choosing a category, deciding
log level / required fields, or moving a log file across the WSL
boundary (author surface):
Read
docs/logging-conventions.md. - Performance work on the Alt+/ popup, the cross-FS routing rule for
state files, the bench harnesses, or the sync-runtime hot path
(skip-if-current gates, rsync-vs-cp tradeoff, mtime-based change
detection):
Read
docs/performance.md. - IME candidate-window stability, DEC mode 2026 (synchronized output),
why tmux 3.7+ is required, or agent-CLI render flicker investigation:
Read
docs/ime-flicker-and-sync-output.md. - Sending a signal from a hook / picker / external helper into the
WezTerm Lua process, picking between OSC and file transports, adding
a new event, or migrating producers/consumers when upstream tmux or
wezterm fix popup OSC pass-through:
Read
docs/event-bus.md. - Per-workspace tmux-session focus statistics, the
tab-stats-bump.shhook chain, the on-disk<workspace>.jsonschema, weight decay / normalization formula, or planning the top-N tab bar slots / overflow tab / warm preheat layer: Readdocs/tab-visibility.md. - Ownership boundaries, runtime architecture, or entry points:
Read
docs/architecture.md. - Env loading, secret placement, the
~/.config/shell-env.d/convention,runtime-env-lib.sh::runtime_env_load_managed, or deciding whether a value belongs inwezterm-x/local/shared.envvs~/.config/shell-env.d/: Readdocs/setup.md#env-loading-model. - Agent-CLI launch chain,
agent-launcher.sh, the${WEZTERM_REPO}placeholder used inconfig/worktree-task.env, or any path that spawnsclaude/codex: Readdocs/architecture.md#startup-invariants. - Adversarial code review skill (find→refute→repro), cross-agent backend
selection, the shared
lib/provider.shlayer, per-stage reasoning effort, the no-session-resume rationale, or offline mock testing: Readdocs/adversarial-review.md. - Multi-persona brainstorm skill (diverge→challenge→converge), persona/provider
selection, per-stage effort, the no-resume design, or the offline mock harness:
Read
docs/brainstorm.md. - Host-CLI invoke layers (one-way dependency):
- Single-shot:
adversarial-review/lib/provider.sh→run_agent/agent_text→ plugin__invoke(no temp dir). - Multi-shot / parallel:
agent-fanout/lib/fanout-lib.sh(fanout_call/fanout_run/fanout_run_jobs) + CLIrun.sh. Fanout sources provider; provider never loads fanout. Do not hand-rollclaude & waitor call__invokefrom feature code. Offline smoke:scripts/dev/agent-fanout/test.sh. Notes:docs/adversarial-review.md/docs/brainstorm.md.
- Single-shot:
- Design proposal / RFC / ADR / 方案评审 (no runtime diff — not a dedicated
skill): structured 设计评审 checklist and intent routing live in the
user-level profile
agent-profiles/v1/en/validation.md(Design proposal review); also summarized underdocs/adversarial-review.md(out of scope) anddocs/brainstorm.md(when alternatives are still needed). - Host↔Claw session interop (Session Adapter Kit /
session-bridge: list/read host tmux + claw sessions, gatedpoke/host-send-keysunder lease, panic freeze,bot-send/say-as-meidentities, attention merge, tmux side-load safety): Readopenclaw/docs/session-bridge.md. - Personal OpenClaw control plane (Feishu gateway templates, main-agent
protocol, link/smoke scripts — not the WezTerm/tmux execution hot path):
Read
openclaw/README.mdandopenclaw/workspace/AGENTS.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.
- 3d ago First seen · 197 lines · 4,226 tokens per session scan A 794990bbcb96
wezdeck AGENTS.md is an instructions file published in the GitHub repository yunsii/wezdeck (5 stars, last pushed 6d ago), licensed MIT. It adds 4,226 tokens to every session, about $0.0211 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 instructions, from other repositories
wiff AGENTS.md
Instructions for xxxoooxoxo/wiff, covering agents.md, orchestrating with wiff (driving it from a harness) and working on this codebase.
workstreams ai-customization.instructions.md
Architecture documentation for VS Code AI Customization view. Use when working in src/vs/workbench/contrib/chat/browser/aiCustomization.
workstreams tree-widgets.instructions.md
Use when asked to consume workbench tree widgets in VS Code.
workstreams notebook.instructions.md
Architecture documentation for VS Code notebook and interactive window components. Use when working in src/vs/workbench/contrib/notebook/.
workstreams interactive.instructions.md
Architecture documentation for VS Code interactive window component. Use when working in src/vs/workbench/contrib/interactive.
workstreams telemetry.instructions.md
Use when asked to work on telemetry events.