opensea

Pass

Audited by Gen Agent Trust Hub on Jun 20, 2026

Risk Level: SAFE
Full Analysis
  • [SAFE]: The skill implements a secure communication pattern by wrapping all external API responses in explicit boundary markers (--- BEGIN OPENSEA API RESPONSE ---). This design explicitly informs the consuming agent that the enclosed content is untrusted user-generated metadata, effectively mitigating Indirect Prompt Injection risks.
  • [SAFE]: Administrative workflows for wallet policy management (e.g., spending caps and allowlists) are strategically placed in separate documentation (docs/policy-administration.md) outside the agent's skill mount path. This architectural choice prevents the agent from accessing or executing instructions to weaken its own security constraints.
  • [SAFE]: The skill provides detailed security guidance recommending managed providers such as Privy, Turnkey, and Fireblocks, which offer TEE-enforced policies and HSM-backed signing. It explicitly warns against using raw private keys in shared or production environments.
  • [SAFE]: Analysis of all shell scripts (e.g., opensea-get.sh, opensea-post.sh) and SDK references confirms that network operations are restricted to official vendor-controlled domains (OpenSea, Privy, Turnkey, etc.) and well-known blockchain RPC endpoints.
Audit Metadata
Risk Level
SAFE
Analyzed
Jun 20, 2026, 08:58 AM
Security Audit — agent-trust-hub — opensea