secrets-management
Pass
Audited by Gen Agent Trust Hub on Feb 17, 2026
Risk Level: SAFEEXTERNAL_DOWNLOADS
Full Analysis
- [EXTERNAL_DOWNLOADS] (LOW): The skill references external GitHub Actions and Docker images for security scanning.
- Evidence: References
hashicorp/vault-action@v2andaws-actions/configure-aws-credentials@v4inSKILL.md. Since HashiCorp and AWS are in the [TRUST-SCOPE-RULE] list, these findings are downgraded to LOW. - Evidence: Uses
trufflesecurity/trufflehog:latestfrom Docker Hub for secret scanning. While not on the specific trusted list, it is a standard security tool and used as intended for the skill's purpose. - [CREDENTIALS_UNSAFE] (SAFE): Includes example credentials and tokens.
- Evidence:
VAULT_TOKEN='root'andpassword=secretare used within a 'dev server' setup context inSKILL.md. These are functional defaults for local development environments and are not real-world credentials. - [INDIRECT_PROMPT_INJECTION] (LOW): The skill describes processes that ingest data from external secret managers which could theoretically contain malicious instructions.
- Evidence Chain:
- Ingestion points:
vault kv getandaws secretsmanager get-secret-valueinSKILL.mdexamples. - Boundary markers: Absent in shell examples, though documentation recommends best practices.
- Capability inventory: Shell command execution and GitHub Action workflow steps.
- Sanitization: Includes specific instructions to use
::add-mask::in GitHub Actions to prevent secret leakage in logs.
Audit Metadata