AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Opencrow Pwn Toolbox

skill-02loveslollipop-opencrow-opencrow-pwn-toolbox · by 02loveslollipop

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.

— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-02loveslollipop-opencrow-opencrow-pwn-toolbox

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-02loveslollipop-opencrow-opencrow-pwn-toolbox)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Opencrow Pwn Toolbox? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

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:

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

Run an exploit or helper script:

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

Verify the mapped stack:

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.

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

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.