running-cli-in-wsl-portable

running-cli-in-wsl-portable is a skill for Claude Code, Codex from Muriel-Salvan/x_aeon_agents. It costs 53 tokens per session (610 once invoked), scanned A, original, BSD-3-Clause.

A skill for running Bash command lines inside a portable Bash installation under Windows Subsystem for Linux, which is a way to run Linux tools on Windows.

In plain words
What is it for?
Use it when a command must execute inside a Portable Bash installation running under WSL.
Why use it?
It ensures commands run in the specified portable WSL environment when the normal shell is not the intended one.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for cline. Also seen: built for cline.

Good fit Use it when a command must execute inside a Portable Bash installation running under WSL.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/muriel-salvan/x_aeon_agents/running-cli-in-wsl-portable
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 Muriel-Salvan/x_aeon_agents --skill running-cli-in-wsl-portable
Clone the repo
git clone --depth 1 https://github.com/Muriel-Salvan/x_aeon_agents

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 running-cli-in-wsl-portable

README.md
[![agentmods](https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/running-cli-in-wsl-portable/github.svg)](https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/running-cli-in-wsl-portable)
Your own site
<a href="https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/running-cli-in-wsl-portable"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/running-cli-in-wsl-portable/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 running-cli-in-wsl-portable

Your own site · 80×15
<a href="https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/running-cli-in-wsl-portable"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/running-cli-in-wsl-portable.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 610 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.00053 $0.00610
Opus 5.5 $0.00021 $0.00244
Sonnet 5.5 $0.00011 $0.00122
Haiku 4.5 $0.00005 $0.00061

Measured 2mo ago against content hash 8e326ab4729e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

running-cli-in-wsl-portable 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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/wsl_portable_bash.cmd), 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/running-cli-in-wsl-portable/SKILL.md · 58 lines

How it starts

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

Running CLI in WSL Portable

Sequential steps to be followed when using this skill

When running a bash command under a WSL portable environment, follow those steps. The original bash command to be run is later referenced as {original_cli}.

1. Inform the user

  • Always tell the user "SKILL: I am running CLI in WSL Portable" to inform the user that you are running this skill.

2. Run the command line with the right prefix

  • Find this skill directory absolute path, later referenced as {skill_absolute_path}.
  • Always use cli: {skill_absolute_path}\scripts\wsl_portable_bash.cmd "{original_cli}".
  • Be careful that the path to the script should be absolute and using anti-slashes (\). However the argument will be executed under WSL, so it should follow Linux conventions, with file paths using slashes (/).

Example:

C:\my-repo\.cline\skills\running-cli-in-wsl-portable\scripts\wsl_portable_bash.cmd "mkdir linux-path/to/my-files"

Example with Linux file patterns that don't need to be escaped:

C:\my-repo\.cline\skills\running-cli-in-wsl-portable\scripts\wsl_portable_bash.cmd "ls *.md"

When to use it

  • Always use it every time another skill specifically mentions skill: running-cli-in-wsl-portable.
  • Always use it every time the user asks you to run a CLI command using the WSL Portable environment.
  • Always use it every time you need to run a CLI command that needs a WSL Portable environment.
  • Never use this skill when you are under a Linux environment.

Usage and code examples

Those examples are given for a Windows environment.

Running a Hello World prompt under a WSL Portable environment, with example of the output

Note that the WSL Portable environment may output some lines on stderr. You can safely ignore them.

C:\my-repo\.cline\skills\running-cli-in-wsl-portable\scripts\wsl_portable_bash.cmd "echo 'Hello World'"
# Setting $HOME to /mnt/i/Env/Linux/Programs/bash/bash.home
# Setting $XDG_CONFIG_HOME to /mnt/i/Env/Linux/Programs/bash/bash.config
# Hello World

Read the full file on GitHub · 58 lines

Files

What ships with it

1 file 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.

  1. 2mo ago First seen · 58 lines · 53 tokens per session scan A 8e326ab4729e

Subscribe to this mod's changes

running-cli-in-wsl-portable is a skill published in the GitHub repository Muriel-Salvan/x_aeon_agents (2 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 53 tokens to every session and 610 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens