メニュー
Use the OpenCROW utility stack for shell-heavy CTF workflows. Use when Codex needs `jq`, `yq`, `xxd`, `tmux`, `screen`, `rg`, or `fzf` to glue a larger workflow together.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use the Anaconda `ctf` environment and installed reverse-engineering tooling for binary analysis, symbolic execution, disassembly, emulation, and binary patching. Use when Codex needs `angr`, `claripy`, `capstone`, `unicorn`, `ghidra-headless`, `radare2`, `objdump`, `strace`, `ltrace`, `binwalk`, or related tools.
Manage a preinstalled local Minecraft Java client asynchronously for CTF and automation workflows. Use when Codex needs to launch Minecraft in offline mode with alternate usernames, inspect Minecraft logs, focus or type into the X11 game window, send chat or slash commands quickly, or join a multiplayer server by launching the installed client directly instead of relying on the official launcher.
Maintain bidirectional netcat-style TCP communications with persistent asynchronous input/output. Use when Codex must keep a connection open across multiple commands, send messages while receiving background output, inspect connection logs, or safely start/stop reusable sessions for protocol testing, CTF services, debugging sockets, or interactive line-based services.
Maintain persistent asynchronous SSH sessions with bidirectional input/output across multiple commands. Use when Codex must keep an SSH shell open, send commands incrementally, inspect prompts or streamed output, reuse one authenticated connection for a task, or safely start/stop a long-lived remote session for debugging, administration, deployment, log inspection, or interactive line-based workflows on remote hosts.
Use the Anaconda `ctf` environment and installed network tooling for packet- and protocol-level CTF tasks. Use when Codex needs `scapy`, `tshark`, `tcpdump`, `nmap`, `nc`, or `socat` for packet work, capture analysis, or service triage.
Use the Anaconda `ctf` environment and installed crypto tooling for CTF tasks that fit normal Python or CLI cracking rather than SageMath. Use when Codex needs `z3`, `fpylll`, `pycryptodome`, `hashcat`, `john`, or quick FactorDB lookups.
SOC 職業分類に基づく
| name | opencrow-utility-toolbox |
| description | Use the OpenCROW utility stack for shell-heavy CTF workflows. Use when Codex needs `jq`, `yq`, `xxd`, `tmux`, `screen`, `rg`, or `fzf` to glue a larger workflow together. |
Use this skill when the blocker is shell ergonomics or structured-data processing rather than a challenge-specific exploit primitive. It covers the “glue” layer that makes larger CTF workflows faster: jq, yq, xxd, tmux, screen, ripgrep, fzf, opencrow-autosetup, and opencrow-exploit.
Start the MCP server from the installed CLI:
opencrow-utility-mcp
Verify the mapped stack:
python ~/.codex/skills/opencrow-utility-toolbox/scripts/verify_toolkit.py
toolbox_info, toolbox_verify, and toolbox_capabilities.utility_search first when a workspace is large and you need to narrow the problem before opening files manually.utility_json_query or utility_yaml_query when configs, API responses, or challenge metadata need slicing before deeper analysis.utility_hexdump when you need a fast bounded hex view of a file region.tmux or screen when the task benefits from persistent panes or background sessions.opencrow-autosetup to seed a standard challenge workspace with OpenCROW reconnaissance artifacts, maintain HANDOFF.md, and launch a reconnaissance-only Codex pass that selects the final category-specific AGENTS.md.opencrow-exploit to launch the follow-up Codex solve pass from the AGENTS.md and HANDOFF.md artifacts created by autosetup.opencrow-utility-mcp: stdio MCP server for typed workspace search, jq/yq queries, and xxd hexdumps.scripts/verify_toolkit.py: confirm that the mapped workflow helpers are installed.references/tooling.md: quick guidance for common shell utility choices.