runpod-deployment
Pass
Audited by Gen Agent Trust Hub on Sep 17, 2026
Risk Level: SAFEEXTERNAL_DOWNLOADSCOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTIONDYNAMIC_EXECUTION
Full Analysis
- [EXTERNAL_DOWNLOADS]: The skill provides instructions to download the
runpodctlbinary from the official RunPod GitHub repository (github.com/runpod/runpodctl). This is a well-known and trusted source for this infrastructure-related tool. - [COMMAND_EXECUTION]: The deployment workflows involve executing shell commands for tool installation and project deployment, including the use of
sudoto move the CLI binary into the system's executable path (/usr/local/bin/). This represents standard developer-level environment setup. - [INDIRECT_PROMPT_INJECTION]: The provided Python worker templates ingest untrusted data from the
job["input"]object, which is then passed to an LLM. - Ingestion points: External input enters the system through the
promptandmessagesfields intemplates/runpod-worker.pyand various code snippets inSKILL.md. - Boundary markers: No explicit delimiters or boundary markers are used in the provided template code to separate user input from system instructions.
- Capability inventory: The worker handlers possess capabilities for network communication (via the
runpodSDK andrequests) and filesystem operations (for logging and model checkpointing). - Sanitization: Input validation is performed via
pydanticfor schema correctness, but no natural language sanitization is applied to the content of the prompts themselves. - [DYNAMIC_EXECUTION]: The skill references the use of
torch.loadinreference/pod-management.mdfor managing model checkpoints. Whiletorch.loaduses unpickling which can execute arbitrary code, it is a standard practice in machine learning for loading user-generated state dictionaries.
Audit Metadata