reap-19-kernel-and-driver-exploitation-research SKILL.md skillA
reap-19-kernel-and-driver-exploitation-research from joasasantos/rea-prompts is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add joasasantos/rea-prompts/reap-19-kernel-and-driver-exploitation-research@git:20261025.9bd45a8Pins git:20261025.9bd45a8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- joasasantos/rea-prompts
- Path
Skills/reap-19-kernel-and-driver-exploitation-research/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261025.9bd45a8, committed Oct 25, 2026
- Size
- 4,462 bytes
- Repository stars
- 3,713
- License
- MIT
REA prompt pack: Kernel & driver exploitation research (7 ready-to-paste prompts). Use when doing reverse-engineering investigation of kernel & driver exploitation research with REA (rea.tools) via an AI coding agent.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# REAP — 19. Kernel & driver exploitation research Part of REAP (REA Investigation Prompts). Replace everything in <angle brackets>; keep each request focused on one feature. Demand file/function/address evidence and separate facts from hypotheses. > Authorized contexts only: your own vulnerable driver, a CVE you are validating > for a bug bounty, a CTF kernel challenge, or defensive hardening review. > "Exploitation research" here means proving reachability of a flaw and > documenting the primitive — not building public weaponized exploits. ### Vulnerable-driver primitive analysis (BYOVD-style, own driver) ```text Use REA on <driver .sys> that I own/am authorized to assess (e.g. a known vulnerable driver used in my lab). Document the read/write primitive: which IOCTL gives arbitrary physical or virtual memory R/W, exactly how the handler validates (or fails to validate) the input buffer, the struct layout the driver expects, and the shortest reproducible sequence that demonstrates the primitive against my own test buffer. Give handler addresses and the missing check that makes it possible. ``` ### CVE reachability validation on a patched build ```text …
Read the whole file at its exact version.
How to install
mdr add joasasantos/rea-prompts/reap-19-kernel-and-driver-exploitation-research@sha256:6e0d96628e3f2636The line at the top of this page pins the label git:20261025.9bd45a8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_smfjbcnvhpeobdgs)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 25, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4462 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
joasasantos/rea-prompts · 3,713 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_smfjbcnvhpeobdgs GET https://markdownregistry.com/api/v1/resolve?ref=joasasantos/rea-prompts/reap-19-kernel-and-driver-exploitation-research GET https://markdownregistry.com/api/v1/blob/6e0d96628e3f26367d65edafb28b14a18deac222e2b97938d7eb16b9f1430a03
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.