use-wsl

use-wsl is a skill for Claude Code, Codex from Yuyu123fish/codex-win-to-wsl. It costs 40 tokens per session (511 once invoked), scanned A, original, MIT.

A workflow for running one requested non-interactive Linux command through Windows Subsystem for Linux, which lets Windows run Linux tools in a project directory.

In plain words
What is it for?
Use it when a Windows-native coding agent must execute a specified Linux command or a group of independent development checks in WSL.
Why use it?
It preserves the working directory and prevents silent retries or switching to an unrelated environment.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Good fit Use it when a Windows-native coding agent must execute a specified Linux command or a group of independent development checks in WSL.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yuyu123fish/codex-win-to-wsl/use-wsl
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 Yuyu123fish/codex-win-to-wsl --skill use-wsl
Clone the repo
git clone --depth 1 https://github.com/Yuyu123fish/codex-win-to-wsl

Made for: Claude Code, 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.

agentmods badge for use-wsl

README.md
[![agentmods](https://agentmods.dev/badge/skills/yuyu123fish/codex-win-to-wsl/use-wsl/github.svg)](https://agentmods.dev/skills/yuyu123fish/codex-win-to-wsl/use-wsl)
Your own site
<a href="https://agentmods.dev/skills/yuyu123fish/codex-win-to-wsl/use-wsl"><img src="https://agentmods.dev/badge/skills/yuyu123fish/codex-win-to-wsl/use-wsl/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.

agentmods 80×15 button for use-wsl

Your own site · 80×15
<a href="https://agentmods.dev/skills/yuyu123fish/codex-win-to-wsl/use-wsl"><img src="https://agentmods.dev/badge/skills/yuyu123fish/codex-win-to-wsl/use-wsl.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 511 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00511
Opus 5 $0.00020 $0.00255
Sonnet 5 $0.00008 $0.00102
Haiku 4.5 $0.00004 $0.00051

Measured 11d ago against content hash f621c97d25af, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

use-wsl 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 11d 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.

plugins/codex-win-to-wsl/skills/use-wsl/SKILL.md · 19 lines

What it actually says

Use WSL

Use wsl_exec only when the user explicitly asks to run a command in WSL or the task clearly requires Linux tooling.

When using the tool:

  1. Determine the current task workspace path before calling the tool. Pass that absolute path as cwd. Never omit cwd, use the plugin installation directory, or silently fall back to a home directory.
  2. Pass the exact non-interactive command when the user supplies one. When the user instead requests multiple independent development gates, such as format, typecheck, lint, test, and build, compose one shell invocation that runs every independent gate, prints a clear label and exit status for each gate, and exits nonzero at the end if any gate failed. Do not join independent gates with &&; reserve short-circuiting for steps that genuinely depend on an earlier step.
  3. Prefer an explicit distribution when the user names one. Set timeoutSeconds to match the expected work: 30 seconds for quick checks, 60 to 120 seconds for normal tests, and up to 1800 seconds for long builds or full test suites. Omit it only when the 60-second default is appropriate.
  4. Make one wsl_exec call per user-requested execution. Do not call it first as a probe and do not retry automatically. If the result is ambiguous or fails, report it first. A corrective call is allowed only after the user explicitly approves or requests it.
  5. Do not claim success unless the returned exitCode is zero and resolvedCwd is the intended project directory. For a multi-gate execution, report every gate as passed, failed, or not run; do not describe a gate as failed when it was skipped because of a real dependency.
  6. Report stdout, stderr, hostDiagnostics, warnings, exitCode, durationMs, requestedCwd, resolvedCwd, timedOut, cancelled, recoveredOrphans, and windowsUser when diagnosing behavior. When cleanup is non-null, also report cleanup.success; when it is null, say that no timeout or cancellation cleanup was required.
  7. Treat the tool as arbitrary command execution and preserve Codex approval requirements.
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.

  1. 11d ago First seen · 19 lines · 40 tokens per session scan A f621c97d25af

Subscribe to this mod's changes

use-wsl is a skill published in the GitHub repository Yuyu123fish/codex-win-to-wsl (2 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 511 once invoked, about $0.0002 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.