Run any Skill in Manus with one click

maxtac-dast-debugger

Stars12

Forks0

UpdatedJune 28, 2026 at 23:09

Use this skill when binary or systems dynamic analysis requires debugger, instrumentation, crash replay, or runtime tooling such as Radare2 DBG, LLDB, GDB, x64dbg, WinDbg, or Frida.

Installation

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.

Run Skill in Manus

Source

philo-groves

philo-groves/MaxTAC

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

8 files

SKILL.md

readonly

name	maxtac-dast-debugger
description	Use this skill when binary or systems dynamic analysis requires debugger, instrumentation, crash replay, or runtime tooling such as Radare2 DBG, LLDB, GDB, x64dbg, WinDbg, or Frida.

MaxTAC DAST Debugger

Evidence Helper

Use python3 <skill-dir>/scripts/debug-evidence.py to collect debugger, instrumentation, replay, or crash evidence into <workspace-root>/proof/<case-id>/.

Initialize a debug evidence case:

python3 <skill-dir>/scripts/debug-evidence.py init \
  --tool lldb \
  --version-command "lldb --version" \
  --target "local parser harness" \
  --target-version "1.2.3 build 456" \
  --target-file ./harness \
  --scope "authorized local test target" \
  --environment "local macOS test host" \
  --command-line "lldb -- ./harness crash.min"

Capture command output:

python3 <skill-dir>/scripts/debug-evidence.py capture debug-20260616T000000Z-abc123 \
  --label replay \
  --command "lldb --batch -o run -o bt -- ./harness crash.min"

Attach artifacts such as crash logs, traces, bugreports, screenshots, recordings, or core dumps:

python3 <skill-dir>/scripts/debug-evidence.py add-artifact debug-20260616T000000Z-abc123 \
  --category crash-log \
  --artifact ./crash.log

Before proof or report handoff, run:

python3 <skill-dir>/scripts/debug-evidence.py lint debug-20260616T000000Z-abc123 --strict
python3 <skill-dir>/scripts/debug-evidence.py summary debug-20260616T000000Z-abc123

Tool Selection

Read only the reference for the selected runtime or evidence source.

Need	Prefer	Reference
macOS native binaries, Linux native binaries with LLDB support, or LLVM-centered crash replay	LLDB	`<skill-dir>/references/lldb-debugger.md`
Linux native binaries or portable ELF crash replay	GDB	`<skill-dir>/references/gdb-debugger.md`
Windows user-mode binary debugging	x64dbg	`<skill-dir>/references/x64dbg-debugger.md`
Windows kernel-mode, crash dump, or deep OS-component debugging	WinDbg	`<skill-dir>/references/windbg-debugger.md`
Fallback binary debugging inside an r2 workflow	Radare2 DBG	`<plugin-root>/skills/maxtac-re-radare2/references/radare2-debugging.md`
Runtime instrumentation, native hooks, or API tracing	Frida	`<skill-dir>/references/frida-instrumentation.md`

More from this repository

same repository

maxtac-source-codebase-memory

philo-groves/MaxTAC

Use this skill when MaxTAC Source should use the plugin-bundled codebase-memory-mcp MCP integration or CLI fallback for repository indexing, architecture overview, structural search, call-path tracing, diff impact mapping, ADR lookup, or code graph evidence before SAST triage, CFG work, OpenGrep authoring, or source scans.

2026-07-0112

maxtac-android-input-loop

philo-groves/MaxTAC

Use this skill when MaxTAC Android needs a loop that models an Android app's user-facing resources and systematically walks activities, deep links, forms, WebViews, share targets, notifications, and other user-facing inputs for security auditing while respecting scope and safety constraints.

2026-07-0112

maxtac-asb-ipsw-cve-history-loop

philo-groves/MaxTAC

Use this skill when Apple Systems research needs a loop over IPSW or OTA firmware diffs, Apple security advisories, CVEs, build provenance, and binary/source patch archaeology to identify patched Apple components, infer why they changed, and enrich an ASB threat model.

2026-07-0112

maxtac-binary-decompile-loop

philo-groves/MaxTAC

Use this skill when MaxTAC Binary needs a loop to model how a binary was compiled and loaded, preserve reverse-engineering provenance, prioritize executable functions by reachability or call frequency, systematically decompile or parse functions and data structures, and produce durable functionality and security evidence.

2026-07-0112

maxtac-core-modeling

philo-groves/MaxTAC

Use this skill when MaxTAC research needs a durable security model, invariant dictionary, invariant receipts with proof obligations and refutation conditions, architecture understanding, first-order-logic-style assertions, unknown tracking, contradiction tracking, or model-backed auditor handoffs across source, web, cloud, binary, supply-chain, Android, Apple, or Microsoft targets.

2026-07-0112

maxtac-core-subagents

philo-groves/MaxTAC

Use this skill when MaxTAC research needs goal-bounded auditor subagents, verifier debate subagents, specialist bug-class review, mitigation review, or independent votes on a vulnerability hypothesis or PoV.

2026-07-0112

name	maxtac-dast-debugger
description	Use this skill when binary or systems dynamic analysis requires debugger, instrumentation, crash replay, or runtime tooling such as Radare2 DBG, LLDB, GDB, x64dbg, WinDbg, or Frida.

MaxTAC DAST Debugger

Evidence Helper

Use python3 <skill-dir>/scripts/debug-evidence.py to collect debugger, instrumentation, replay, or crash evidence into <workspace-root>/proof/<case-id>/.

Initialize a debug evidence case:

python3 <skill-dir>/scripts/debug-evidence.py init \
  --tool lldb \
  --version-command "lldb --version" \
  --target "local parser harness" \
  --target-version "1.2.3 build 456" \
  --target-file ./harness \
  --scope "authorized local test target" \
  --environment "local macOS test host" \
  --command-line "lldb -- ./harness crash.min"

Capture command output:

python3 <skill-dir>/scripts/debug-evidence.py capture debug-20260616T000000Z-abc123 \
  --label replay \
  --command "lldb --batch -o run -o bt -- ./harness crash.min"

Attach artifacts such as crash logs, traces, bugreports, screenshots, recordings, or core dumps:

python3 <skill-dir>/scripts/debug-evidence.py add-artifact debug-20260616T000000Z-abc123 \
  --category crash-log \
  --artifact ./crash.log

Before proof or report handoff, run:

python3 <skill-dir>/scripts/debug-evidence.py lint debug-20260616T000000Z-abc123 --strict
python3 <skill-dir>/scripts/debug-evidence.py summary debug-20260616T000000Z-abc123

Tool Selection

Read only the reference for the selected runtime or evidence source.

Need	Prefer	Reference
macOS native binaries, Linux native binaries with LLDB support, or LLVM-centered crash replay	LLDB	`<skill-dir>/references/lldb-debugger.md`
Linux native binaries or portable ELF crash replay	GDB	`<skill-dir>/references/gdb-debugger.md`
Windows user-mode binary debugging	x64dbg	`<skill-dir>/references/x64dbg-debugger.md`
Windows kernel-mode, crash dump, or deep OS-component debugging	WinDbg	`<skill-dir>/references/windbg-debugger.md`
Fallback binary debugging inside an r2 workflow	Radare2 DBG	`<plugin-root>/skills/maxtac-re-radare2/references/radare2-debugging.md`
Runtime instrumentation, native hooks, or API tracing	Frida	`<skill-dir>/references/frida-instrumentation.md`