Okx 402 Payment

Sign an x402 payment authorization for an EXTERNAL / third-party payment-gated resource. Use only when the user explicitly mentions 'x402' (or 'sign x402 pay...

This skill implements x402 payment signing and appears to do that end-to-end, but there are important questions you should resolve before using it: - The SKILL.md calls the onchainos CLI but the skill metadata does not list onchainos as a required binary. Verify that the onchainos CLI is present, trusted, and that you understand which binary will be executed. - The instructions tell the agent to read ../okx-agentic-wallet/_shared/preflight.md (or _shared/preflight.md). Inspect that referenced file first — it could contain sensitive instructions or references to other credentials. A skill should not need to read sibling-skill files without explicit justification. - The skill supports 'local signing with a private key'. Never paste or send your raw private keys unless you fully trust the skill and the execution environment. Prefer TEE/hardware-wallet signing via a wallet session rather than providing key material directly. - Ask the publisher (or inspect the full SKILL.md) to: (a) explicitly declare required binaries (onchainos), (b) explain how wallet sessions are initiated and authorized, and (c) show the exact prompts used if the skill requests private keys or other secrets at runtime. If the publisher updates the metadata to declare onchainos as a required binary and confirms the referenced preflight file contains only benign helper text (no secret access), and if the skill never requests raw private keys (or clearly documents a secure input flow), this assessment could move toward benign. Until then, treat the skill with caution and do not supply private keys or global credentials.

Type: OpenClaw Skill Name: okx-x402-payment Version: 2.6.0 The skill bundle contains instructions in SKILL.md that direct the AI agent to perform high-risk operations, specifically reading sensitive credentials (EVM_PRIVATE_KEY) from a local configuration file (~/.onchainos/.env). Furthermore, the operational flow involves taking potentially untrusted JSON payloads from external HTTP 402 responses and passing them directly into shell commands (e.g., onchainos payment x402-pay --accepts '...'), which creates a significant risk of shell injection or command manipulation. While these capabilities are aligned with the stated purpose of facilitating x402 payments, the handling of raw private keys and the lack of explicit sanitization for shell-bound data are meaningful high-risk behaviors.