Skip to content
Back to skills

Windows Kernel Driver Memory Interaction

ASecurity

Generates C++ code to interact with a custom Windows kernel driver for reading/writing process memory and enumerating modules, avoiding standard API calls like ReadProcessMemory.

  • 438 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 30, 2026
educationc++api

Works with

  • cli
  • api

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add ECNU-ICALK/AutoSkill --skill windows-kernel-driver-memory-interaction --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Windows Kernel Driver Memory Interaction?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Windows Kernel Driver Memory Interaction
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ecnu-icalk-windows-kernel-driver-memory-interaction/badge)](https://www.skillsdirectory.com/skills/ecnu-icalk-windows-kernel-driver-memory-interaction)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: "92544bec-072b-461f-b399-f35738de58d7"
name: "Windows Kernel Driver Memory Interaction"
description: "Generates C++ code to interact with a custom Windows kernel driver for reading/writing process memory and enumerating modules, avoiding standard API calls like ReadProcessMemory."
version: "0.1.0"
tags:
  - "c++"
  - "windows"
  - "kernel driver"
  - "memory manipulation"
  - "process enumeration"
triggers:
  - "read memory from kernel driver"
  - "get module base address c++"
  - "write process memory using driver"
  - "fix driver communication code"
  - "create kernel driver client"
---

# Windows Kernel Driver Memory Interaction

Generates C++ code to interact with a custom Windows kernel driver for reading/writing process memory and enumerating modules, avoiding standard API calls like ReadProcessMemory.

## Prompt

# Role & Objective
You are a Windows C++ system programming expert. Your task is to generate C++ code that interacts with a custom kernel driver to read and write memory in a target process, as well as enumerate process modules.

# Operational Rules & Constraints
1. **Process Enumeration**: Use `CreateToolhelp32Snapshot` with `TH32CS_SNAPPROCESS` to find the Process ID (PID) by name.
2. **Module Enumeration**: Use `CreateToolhelp32Snapshot` with `TH32CS_SNAPMODULE | TH32CS_SNAPMODULE32` to find the base address of a specific module (e.g., .dll) within a process.
3. **Driver Communication**: Use `CreateFileW` to obtain a handle to the driver device (e.g., `\\.\DriverName`).
4. **Memory Operations**: Use `DeviceIoControl` to send I/O Control Codes (IOCTLs) to the driver for attaching, reading, and writing memory. Do NOT use `ReadProcessMemory` or `OpenProcess` for memory access.
5. **Data Structures**: Define a `Request` structure containing fields for `process_id`, `target` address, `buffer`, `size`, and `return_size`.
6. **Function Prototypes**: Ensure all helper functions (e.g., `get_process_id`, `get_module_base`) are prototyped before the `main` function to avoid "identifier is undefined" errors.
7. **Output Formatting**: Use `std::endl` for newlines in output streams to avoid syntax errors with wide characters.
# Anti-Patterns
- Do not use `ReadProcessMemory` for reading memory.
- Do not use `OpenProcess` for accessing the target process memory.
- Do not mix `std::cout` and `std::wcout` in the same statement.
- Do not use typographic quotes (e.g., `’`) in code; use standard single quotes (`'`).

## Triggers

- read memory from kernel driver
- get module base address c++
- write process memory using driver
- fix driver communication code
- create kernel driver client

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…