Menu
Use strace and ltrace for authorized syscall and library-call tracing of provided binaries and processes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use agent-browser-cli to perceive and control the supervised Chrome browser inside the sandbox, interact with pages, capture screenshots/PDFs, inspect cookies/CDP/network/console state, and troubleshoot only when needed.
Use OWASP Amass for authorized asset discovery, domain enumeration, and DNS intelligence on in-scope targets.
Use apktool for authorized Android APK resource decoding, manifest review, smali inspection, rebuild checks, and static mobile artifact triage.
Use file, 7z, unzip, tar-compatible tools, hashes, and bounded shell inspection for safe triage of provided archives and unknown files.
Use binwalk for authorized firmware, binary blob, archive, filesystem, and embedded-content triage with bounded extraction and evidence handling.
Use the pwntools-provided checksec CLI for authorized ELF hardening review, mitigation checks, and binary triage evidence.
| name | strace-ltrace |
| description | Use strace and ltrace for authorized syscall and library-call tracing of provided binaries and processes. |
Use strace and ltrace for syscall and library-call tracing during authorized runtime analysis.
Before constructing commands, use installed help or version output as the source of truth:
strace --help
ltrace --help
Trace a short local run and follow child processes:
strace -f -s 256 -o strace.log -- ./program arg1
Focus on file, process, and network syscalls:
strace -f -s 256 -e trace=file,process,network -o strace-focused.log -- ./program
Trace dynamic library calls when the binary is dynamically linked:
ltrace -f -o ltrace.log -- ./program arg1
Attach only to authorized processes:
strace -p 1234 -o strace-pid.log
Report traced program or PID, command used, output path, notable syscalls or library calls, and any sensitive data handling.