rust-debugging

Fail

Audited by Gen Agent Trust Hub on Sep 15, 2026

Risk Level: CRITICALCOMMAND_EXECUTIONDYNAMIC_EXECUTIONINDIRECT_PROMPT_INJECTION
Full Analysis
  • [COMMAND_EXECUTION]: The skill utilizes standard system and development tools for Rust compilation and debugging.
  • Includes usage of cargo build, cargo run, rust-gdb, rust-lldb, and rustfilt for managing the development lifecycle.
  • Employs binary utilities objcopy and strip to manage debug symbols and create separate debug info files, which is standard practice for production Rust binaries.
  • [DYNAMIC_EXECUTION]: The instructions for GDB setup involve dynamic path resolution and loading.
  • A Python snippet for ~/.gdbinit uses subprocess.check_output to call rustc and locate the sysroot path at runtime.
  • The script dynamically modifies the Python path (sys.path.insert) to load the gdb_lookup module from the discovered sysroot.
  • [INDIRECT_PROMPT_INJECTION]: The skill is designed to ingest and interpret data from various external tool outputs, creating a potential injection surface.
  • Ingestion points: Agent reads and interprets outputs from gdb, lldb, cargo run, and tokio-console (in SKILL.md).
  • Boundary markers: No explicit instructions to treat tool output as untrusted or to use delimiters are included.
  • Capability inventory: The agent has the capability to execute shell commands (cargo, gdb) and modify files (objcopy).
  • Sanitization: There are no documented steps for sanitizing or validating the data returned by these debugging tools before further processing.
Recommendations
  • CRITICAL: 1 file(s) identified as malware by FileRep - DO NOT USE
Audit Metadata
Risk Level
CRITICAL
Analyzed
Sep 15, 2026, 01:50 AM