x402

The skill automatically executes cryptocurrency payments when encountering 402 Payment Required responses, without explicit user confirmation for each transaction. The x402Client and wrapFetch functions handle payments transparently in the background. This creates risks: (1) Malicious APIs could drain wallet funds by returning 402 responses with inflated amounts. (2) Users may not be aware transactions are being executed. (3) No spending limits, transaction caps, or approval workflows are mentioned. (4) Compromised or malicious API endpoints could exploit automatic payment behavior. (5) The 'automatic 402 handling' feature removes user control over fund transfers.

SKILL.md

const client = x402Client({
  privateKey: process.env.WALLET_PRIVATE_KEY,
  network: 'base',
});

// Automatic 402 handling
const response = await client.fetch('https://api.example.com/paid-endpoint');

The skill manifest does not declare 'allowed-tools', which means the agent has unrestricted access to all tools (Read, Write, Grep, Glob, Bash, Python). Given that this skill executes cryptocurrency transactions and handles private keys, unrestricted tool access creates significant risks: (1) Bash tool access allows arbitrary command execution including network calls. (2) Write tool access could modify system files or create malicious scripts. (3) Read tool access could exfiltrate sensitive data including the private key itself. (4) The skill's legitimate functionality only requires Bash for executing the check-balance.sh script, but gets full system access.

SKILL.md

Manifest shows: 'allowed-tools: Not specified'. The skill includes bash scripts and requires environment variable access, but no tool restrictions are declared.