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.
npx agentmods add skills/buzzer-re/rikugan/driver-analysisnpx skills add buzzer-re/Rikugan --skill driver-analysisgit clone --depth 1 https://github.com/buzzer-re/RikuganWrote 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.
[](https://agentmods.dev/skills/buzzer-re/rikugan/driver-analysis)<a href="https://agentmods.dev/skills/buzzer-re/rikugan/driver-analysis"><img src="https://agentmods.dev/badge/skills/buzzer-re/rikugan/driver-analysis.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00020 | $0.00509 |
| Opus 5 | $0.00010 | $0.00254 |
| Sonnet 5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
Driver Analysis 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 6d 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.
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.
Task: Windows Kernel Driver Analysis. You are analyzing a kernel-mode driver binary.
Mandatory First Steps
- Find DriverEntry — usually the binary entry point
- Signature:
NTSTATUS DriverEntry(DRIVER_OBJECT*, UNICODE_STRING*) - Use
decompile_functionon the entry point
- Signature:
- From DriverEntry, extract:
- MajorFunction dispatch table assignments
- DriverUnload pointer
- DeviceName and SymbolicLinkName
- Identify IOCTL handlers — look for IRP_MJ_DEVICE_CONTROL dispatch entry
Key Data Structures
Use create_struct and set_type early — these appear in virtually every driver:
- DRIVER_OBJECT, DEVICE_OBJECT
- IRP, IO_STACK_LOCATION
- UNICODE_STRING
Apply types with set_function_prototype and apply_type_to_variable to make decompiled code readable immediately.
IOCTL Analysis
For each IRP_MJ_DEVICE_CONTROL handler:
decompile_functionon the dispatch function- Find the switch statement on IoControlCode
- For each IOCTL code, document:
- IOCTL value and decoded method/access
- Expected input/output buffer sizes
- Operation performed
- Check for dangerous patterns:
- Kernel memory read/write gadgets
- Process token manipulation
- Arbitrary code execution paths
Common Vulnerabilities to Flag
- KeSetEvent with user-controlled address — kernel write primitive
- Missing ProbeForRead/ProbeForWrite before kernel-mode buffer copy
- Unchecked buffer sizes in METHOD_NEITHER IOCTLs — pool overflow
- MmMapIoSpace with user-supplied physical address — arbitrary physical memory access
- Direct stack buffer reads without size validation — kernel stack overflow
- ObReferenceObjectByHandle without proper access checks
Analysis Workflow
- Map the dispatch table → understand all supported IRPs
- Deep-dive each IOCTL handler → document input/output
- Trace data flow from usermode input to kernel operations
- Flag every path where user-controlled data reaches a sensitive kernel API
- Rename functions as you understand them:
DispatchDeviceControl,HandleIoctlReadPhysMem, etc.
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.
- 6d ago First seen · 58 lines · 20 tokens per session scan A 26222ca41d9b
Driver Analysis is a skill published in the GitHub repository buzzer-re/Rikugan (672 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 509 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-30.
Other skills, from other repositories
procmon
Capture and analyze Windows process / file / registry / network activity with OpenProcMon (procmon-cli). Use when investigating what a program does — files it writes, registry keys it touches, network it makes, its process tree and call stacks — or when analyzing a Procmon-compatible .PML capture. The model: a capture…
graphics-api-hooking
Guide for graphics API interception, overlay rendering, and render-pipeline analysis across DirectX, OpenGL, and Vulkan. Use this skill when working with Present or SwapBuffers hooks, DXGI swap chains, shader or draw-call interception, screenshot-sensitive overlays, or graphics debugging in game security research.
wispterm-diagnostics
Use when a user wants to report, troubleshoot, or collect context for a WispTerm issue, including crashes, rendering/DPI glitches, high CPU, keyboard/input bugs, selection/copy/scrolling, SSH/SCP failures, SSH image preview failures, HTML preview/browser panel failures, SSH disconnects such as…
repo-gotchas
Use before trusting CONTRIBUTING.md/Makefile/pre-commit claims literally, or when something documented doesn't behave as expected — "why doesn't X work", "is this hook actually active", "make help is missing stuff". Documents known drift between this repo's docs and its actual behavior.
windows-dev-process-cleanup
Audit and safely clean Windows dev-process trees and UWP app background-task pileups, including orphan npm/npx, leaked Playwright MCP workers, workspace dev servers, IDE services, Phone Link, Dolby Access, and backgroundTaskHost.exe. Use for Task Manager node/npm noise, Windows process buildup, 进程堆积, 清理残留开发进程, 泄漏的…
network-diagnostics
Windows net diag: ping, traceroute, DNS, port scan (PowerShell).