unity-device-testing
Pass
Audited by Gen Agent Trust Hub on Nov 6, 2026
Risk Level: SAFECOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTIONDYNAMIC_EXECUTION
Full Analysis
- [COMMAND_EXECUTION]: The skill's driver scripts (
device-acceptance.sh,ios-acceptance.sh) and documentation (reference/android-driver.md,reference/ios-driver.md) make extensive use ofadbandxcrun devicectlto automate device tasks. This includes waking the device, dismissing keyguards, installing packages, launching processes, and simulating touch events. - [INDIRECT_PROMPT_INJECTION]: The driver scripts ingest and process untrusted data from the device log stream to drive the test logic.
- Ingestion points:
adb logcat -dintemplates/device-acceptance.shandxcrun devicectl device process launch --consoleintemplates/ios-acceptance.shingest the full log output from the connected device. - Boundary markers: No explicit delimiters or warnings to ignore embedded instructions are used when parsing the logs.
- Capability inventory: The driver scripts have the capability to execute shell commands (via
adb shell), pull files from the device, and terminate processes. - Sanitization: No sanitization is performed on the log data; the scripts use
grep -Eto match patterns within the raw log stream. - [DYNAMIC_EXECUTION]: The documentation in
reference/device-probe.mddescribes using C# Reflection (typeof(Facade).GetField("_inner", ... )) within the UnityDeviceProbe.cstemplate. This is used to access internal SDK states for testing purposes, representing a form of dynamic runtime inspection.
Audit Metadata