brightdata-prod-checklist
Pass
Audited by Gen Agent Trust Hub on Sep 13, 2026
Risk Level: SAFECOMMAND_EXECUTIONREMOTE_CODE_EXECUTIONINDIRECT_PROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The skill uses
kubectlandcurlto manage deployments and verify service status. These operations are restricted to the allowed-tools configuration and align with the skill's purpose as a production checklist. - [REMOTE_CODE_EXECUTION]: Automated detectors identified piped execution patterns involving
curlandpython3. A manual review ofSKILL.mdreveals that these patterns are used strictly for parsing and formatting JSON data from trusted sources (the Bright Data API and local deployment health checks) usingpython3 -cfor parsing andpython3 -m json.toolfor pretty-printing. They do not execute external scripts or arbitrary code. - [INDIRECT_PROMPT_INJECTION]: The skill ingests external data from Bright Data's API and local health endpoints during status verification.
- Ingestion points:
curlcalls inSKILL.mdtargetinghttps://api.brightdata.com/zone/get_active_zones,api/v2/status.json, andhttp://localhost:8080/health. - Boundary markers: None implemented in the processing logic.
- Capability inventory:
kubectlfor infrastructure management andcurlfor network requests. - Sanitization: Standard JSON parsing is used; while it doesn't provide instruction filtering, the inputs are structured status objects from the user's own infrastructure or service provider, posing minimal risk.
Audit Metadata