# Opencrow Pwn Toolbox

> Use the best available portable Python runtime and installed exploit tooling for binary exploitation and runtime-debugging tasks. Prefer a detected `ctf` environment. Use when an agent needs `pwntools`, `pwndbg`, `gdb`, `checksec`, `patchelf`, `qemu-user`, `pwninit`, or other pwn-focused helpers.

- **Type:** Skill
- **Install:** `agentstack add skill-02loveslollipop-opencrow-opencrow-pwn-toolbox`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [02loveslollipop](https://agentstack.voostack.com/s/02loveslollipop)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [02loveslollipop](https://github.com/02loveslollipop)
- **Source:** https://github.com/02loveslollipop/OpenCROW/tree/main/skills/opencrow-pwn-toolbox

## Install

```sh
agentstack add skill-02loveslollipop-opencrow-opencrow-pwn-toolbox
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# OpenCROW Pwn Toolbox

## Runtime preflight

Probe required commands with `command -v` and Python modules with `importlib.util.find_spec` before use. Prefer a PATH-resolved OpenCROW MCP helper or the `ctf`/`sage` environment when available, then the managed helper or system Python. If a capability is missing, stop that path safely and report the exact missing command or module.

Prefer the `opencrow-pwn-mcp` server for typed ELF triage, cyclic work, patching, and one-gadget search. Fall back to the direct scripts only when you need to debug the underlying `ctf`-environment execution path.

## MCP First

- Use `toolbox_info`, `toolbox_verify`, and `toolbox_capabilities` first.
- Use the typed pwn operations:
  - `pwn_python`
  - `pwn_checksec`
  - `pwn_cyclic`
  - `pwn_patch_binary`
  - `pwn_one_gadget`
- Treat the existing helper scripts as the implementation fallback, not the primary interface.

Use this skill for exploit development, ELF triage, debugger-heavy workflows, loader/libc patching, one-gadget hunting, and architecture-emulated pwn work in the `ctf` environment.

## Quick Start

Run inline Python in `ctf`:

```bash
python3 scripts/run_pwn_python.py --code 'from pwn import *; print(cyclic(32))'
```

Run an exploit or helper script:

```bash
python3 scripts/run_pwn_python.py --file /absolute/path/to/exploit.py
```

Verify the mapped stack:

```bash
python3 scripts/verify_toolkit.py
```

## Workflow

1. Start here when the task is "get code execution" rather than "understand the binary."
2. Triage the target with `checksec`, `file`, and libc/loader metadata.
3. Use `pwntools` for scripting, local process control, remote sockets, packing, cyclic patterns, and ROP helpers.
4. Move into `gdb` or `pwndbg` once the exploit depends on runtime state.
5. Read [references/tooling.md](references/tooling.md) when choosing between the debugger, patching, or emulation tools.

## Tool Selection

- Use `pwntools` for exploit scripts, process or remote I/O, ELF inspection, cyclic patterns, and ROP chain construction.
- Use `checksec`, `patchelf`, and `pwninit` early to understand or normalize the challenge runtime.
- Use `gdb` and `pwndbg` for breakpoints, heap inspection, and exploit debugging.
- Use `seccomp-tools` when syscall filtering or sandboxing matters.
- Use `one_gadget` when the libc version is known and you want fast candidate constraints for shell-spawning gadgets.
- Use `qemu-user` and `qemu-user-static` when the shipped challenge binary is not native to the host architecture.
- Use `gcc` and `nasm` for shellcode stubs, helper binaries, or local harnesses.

## Resources

- `scripts/run_pwn_python.py`: execute inline code or a `.py` file inside the `ctf` environment.
- `scripts/verify_toolkit.py`: confirm that the mapped Python and native pwn tools are installed.
- `references/tooling.md`: quick selection notes for exploit workflows.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [02loveslollipop](https://github.com/02loveslollipop)
- **Source:** [02loveslollipop/OpenCROW](https://github.com/02loveslollipop/OpenCROW)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-02loveslollipop-opencrow-opencrow-pwn-toolbox
- Seller: https://agentstack.voostack.com/s/02loveslollipop
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.