Agent Wallet
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent with the wallet token could spend wallet funds on API calls without the user reviewing every charge.
This delegates paid API access and payment signing to the AgentWallet service. The artifact documents dryRun as optional, but does not require explicit user confirmation before paid requests.
Use the ONE-STEP `/x402/fetch` endpoint (recommended) - just send target URL + body, server handles 402 detection, payment signing, and retry automatically.
Use dryRun first, require explicit approval for each payment, set low spending caps and policies, and restrict use to trusted target URLs.
Anyone or any agent process that can read the config file may be able to act through the wallet account.
The skill directs the agent to read and reuse a local wallet API token. That token is financial authority, and this credential/config dependency is under-declared in the registry metadata.
Check if already connected by reading `~/.agentwallet/config.json`. If file exists with `apiToken`, you're connected - DO NOT ask user for email.
Treat the token like a password, keep the file permission-restricted, declare the credential/config requirement clearly, and require user consent before using the token for wallet actions.
A later remote file change could make the agent follow instructions that were not part of this reviewed artifact set.
The heartbeat encourages replacing local skill instructions with remote content without pinning, signatures, or integrity checks. For a wallet skill, changed instructions could alter payment behavior.
curl -s https://frames.ag/skill.md > ~/.agentwallet/SKILL.md curl -s https://frames.ag/heartbeat.md > ~/.agentwallet/HEARTBEAT.md
Update only through verified registry releases or require signed/hash-verified downloads before replacing local skill files.
The user may not be told about routine wallet-backed activity unless something fails or the balance gets low.
In a wallet/payment context, successful operations may include financially relevant activity. Telling the agent not to report normal successes can reduce user oversight.
Keep to yourself: - Routine heartbeats - Normal successful operations - Balance checks (unless low)
Require visible logs or notifications for all financial transactions and let the user choose which routine status messages to suppress.