ntwarden-windows-analysis-toolkit — Claude Code skill: Windows
A skill for digging into Windows internals: processes, services, network, ETW, kernel. Useful when you need to break down what a suspicious process is doing.
npx skills add reason-machines/trending-skills --skill ntwarden-windows-analysis-toolkit -a claude-codeWhat ntwarden-windows-analysis-toolkit does
The skill covers NtWarden, a GUI app built on ImGui and DirectX 11 for inspecting Windows. Four pieces sit inside: the GUI itself, the WinSys static library for enumerating processes, services and network connections, the KWinSys kernel driver, and the headless WinSysServer for remote TCP connections.
Build it in Visual Studio 2022 with Windows SDK 10.0.26100.0 or newer. WDK is only needed for the KWinSys driver. Output lands in x64/Release/: NtWarden.exe, WinSysServer.exe and KWinSys/KWinSys.sys. Run the app as Administrator or some features drop out.
The driver installs after bcdedit /set testsigning on and a reboot; on a VM you may also need bcdedit /set nointegritychecks on. The remote server speaks a custom binary protocol with no authentication, so keep it on an isolated lab machine or VM rather than a production network.
What it helps with
- list kernel modules and trace where each one came from
- find unbacked executable memory regions inside a process
- check a process for hollowing by comparing PEB and PE header image bases
- spot direct syscalls that bypass ntdll
- pull TCP connections and map them back to PIDs
Example prompts for the agent
- list processes with NtWarden and sort them by memory use
- check process 1234 for inline user-mode hooks
- start WinSysServer on the VM and connect to it from NtWarden
How to install ntwarden-windows-analysis-toolkit
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill ntwarden-windows-analysis-toolkit -a claude-code2Manually: put the files in place
~/.claude/skills/ntwarden-windows-analysis-toolkit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ntwarden-windows-analysis-toolkit/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill ntwarden-windows-analysis-toolkit -a codex2Manually: put the files in place
.agents/skills/ntwarden-windows-analysis-toolkit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill ntwarden-windows-analysis-toolkit -a cursor2Manually: put the files in place
.cursor/skills/ntwarden-windows-analysis-toolkit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/trending-skills ntwarden-windows-analysis-toolkit2Manually: put the files in place
.github/skills/ntwarden-windows-analysis-toolkit/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill ntwarden-windows-analysis-toolkit -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/trending-skills --path skills/ntwarden-windows-analysis-toolkitManually: put the files in place
.devin/skills/ntwarden-windows-analysis-toolkit/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill ntwarden-windows-analysis-toolkit -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ntwarden-windows-analysis-toolkit
How do I install ntwarden-windows-analysis-toolkit in Claude?
Run npx skills add reason-machines/trending-skills --skill ntwarden-windows-analysis-toolkit -a claude-code. The skill file then lands at ~/.claude/skills/ntwarden-windows-analysis-toolkit/SKILL.md.
What does ntwarden-windows-analysis-toolkit do?
It documents how to build and run NtWarden, a Windows inspection tool. You use it to look at processes, services, network, ETW, registry, the object manager and kernel internals.
Do I need the KWinSys driver for NtWarden?
No. Processes, services, network, ETW, registry and the object manager all work in user mode. KWinSys is only required for the kernel tabs: SSDT hooks, callbacks, modules and pool.