Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk, X Layer through OKX Payments / OKX Agent Payments Protocol, and Solana plus multi-network EVM through the upstream x402 packages with facilitator-based settlement. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.
65
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
The skill documents direct payment execution operations (e.g., sending payments, signing transactions, settling 402-gated API charges via `agentwallet-sdk`, OKX, and upstream x402 packages). These routes rely on private keys (`WALLET_PRIVATE_KEY`, `EVM_PRIVATE_KEY`, `SVM_PRIVATE_KEY`) managed by the configuration or runtime rather than an independent validation/authentication check enforced by the execution layer or service for the payment route itself, leaving financial execution exposed without qualifying independent access control.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The required workflow involves HTTP payment execution and API calls where responses or untrusted server content may be ingested by the agent.
affaan-m/ECC
6f1881a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.