Codex Hacking Plugin

codex-hacking-plugin is a Codex plugin for authorized security work. It uses LazyCodex/OMO as the planning, orchestration, subagent, LSP/codegraph, and review harness, then adds Strix-style hacking workflows and a Docker sandbox with offensive security tools.

This plugin intentionally does not vendor the full Strix Python agent runtime. Codex and LazyCodex coordinate the work; the sandbox is the isolated tool execution surface.

Prerequisites

Use this plugin's installer entrypoint first. It installs LazyCodex/OMO by default, runs lazycodex-ai doctor, and validates this plugin:

./scripts/install.sh

From npm:

npx @w1se/codex-hacking-plugin

or:

npm install -g @w1se/codex-hacking-plugin
codex-hacking-plugin

Equivalent manual prerequisite commands:

npx lazycodex-ai install
npx lazycodex-ai doctor

The plugin doctor enforces this as a runtime prerequisite:

python3 scripts/hacking_mcp.py doctor --check-lazycodex

Docker must be installed and running to use the sandbox.

Build the Sandbox

docker build -t codex-hacking-sandbox:dev sandbox

Override the image name used by tools with:

export CODEX_HACKING_IMAGE=codex-hacking-sandbox:dev

Available Skills

• $codex-hacking-plugin:hacking - main authorized assessment workflow.
• $codex-hacking-plugin:hacking-prepare - doctor/prepare checks for LazyCodex, Docker, sandbox image, smoke test, tools, and artifacts.
• $codex-hacking-plugin:source-aware-hacking - source and PR-diff security assessment.
• $codex-hacking-plugin:web-pentest - authorized black-box URL/domain/API testing.
• $codex-hacking-plugin:hacking-tooling - Strix-style CLI playbooks.
• $codex-hacking-plugin:exploit-validation - PoC and impact validation discipline.
• $codex-hacking-plugin:hacking-report - report schema and artifact workflow.

For non-trivial coordinated assessments, hacking uses LazyCodex team mode rather than plain subagents. Team members are real Codex threads split by concrete asset, component, ownership area, or testing perspective.

MCP Tools

The local MCP server exposes:

• hacking_doctor
• hacking_prepare
• hacking_install_lazycodex
• hacking_sandbox_build
• hacking_sandbox_start
• hacking_sandbox_exec
• hacking_sandbox_stop
• hacking_collect_artifacts

CLI equivalents are available through scripts/hacking_mcp.py.

python3 scripts/hacking_mcp.py install-lazycodex
python3 scripts/hacking_mcp.py prepare --workspace .
python3 scripts/hacking_mcp.py exec prepare '<command>'
python3 scripts/hacking_mcp.py stop --session-id prepare

Safety Boundary

Use this plugin only on systems you own or are explicitly authorized to test. The workflows are designed for evidence-backed vulnerability validation and defensive remediation. They should not be used for unauthorized access, destructive actions, persistence, credential theft, or evasion outside an approved rules of engagement.

Validation

python3 -m json.tool .codex-plugin/plugin.json
python3 -m json.tool .mcp.json
python3 scripts/hacking_mcp.py --self-test
python3 ~/.codex/skills/.system/plugin-creator/scripts/validate_plugin.py .

Local Installation

This repository is the plugin root. The installer intentionally does not update the personal marketplace. Install through the local workflow you use for personal plugins, then start a new Codex thread so LazyCodex hooks, team mode, new skills, and MCP tools are loaded.