atomic-exploit SKILL.md skillA
atomic-exploit from grisuno/lazyown is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add grisuno/lazyown/atomic-exploit@git:20261016.87c0ac4Pins git:20261016.87c0ac4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- grisuno/lazyown
- Path
skills/atomic-exploit/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261016.87c0ac4, committed Oct 16, 2026
- Size
- 5,746 bytes
- Repository stars
- 300
- License
- AGPL-3.0
Extend the autonomous loop's arsenal without touching Python: add one exploits/<id>.yaml per exploit (service triggers, CVE, MITRE ID, real commands). Knows the schema, validation, lab testing, ranking, and every surface each run feeds.
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
# /atomic-exploit The exploit engine is administered by YAML, not by code. To give the autonomous loop a new exploit, you write one file. The engine, the `atomic_exploit` addon, the auto-sweep, and MCP pick it up with zero Python changes. Hardcoded engine entries are a safety net for an empty catalogue only — a YAML twin always wins on strategy-id collision. ## Usage ``` /atomic-exploit add unrealircd backdoor CVE-2010-2075 /atomic-exploit validate /atomic-exploit rank 172.17.0.2 ``` ## Step 1 — Gather facts (no guessing) You need all of these before writing: 1. nmap service name, product, version (from a real scan: `sessions/scan_<ip>.nmap.xml`). 2. CVE or empty string (no CVE invented — use `cve: ""` for logic bugs). 3. MITRE technique the exploit demonstrates (`T1190`, `T1210`, ...). 4. A working command chain PROVEN against the lab (paste real output). 5. A shell indicator string present in success output (`uid=0`, `root@`, ...). 6. Required binaries on the operator host (`nc`, `msfconsole`, `curl`). `confidence` above 0.7 requires a proven run. Unproven entries stay at 0.5 or below so the ranker tries proven options first. ## Step 2 — Write exploits/<id>.yaml …
Read the whole file at its exact version.
How to install
mdr add grisuno/lazyown/atomic-exploit@sha256:721f6feac76a69beThe line at the top of this page pins the label git:20261016.87c0ac4, 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_sad25l365dux4jqa)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 16, 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 (5746 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
grisuno/lazyown · 300 stars · license AGPL-3.0 · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sad25l365dux4jqa GET https://markdownregistry.com/api/v1/resolve?ref=grisuno/lazyown/atomic-exploit GET https://markdownregistry.com/api/v1/blob/721f6feac76a69be742832b6494eeb877970ae48ed1144981d79c59882fc4b56
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.