Design and implement demos combining x402 HTTP payments with ERC-7710 smart contract delegations and ERC-7715 wallet permission requests for subscriptions, bounded agent budgets, recurring spend, pay-per-use APIs, and agentic commerce.
62
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./integrations/x402-erc7710/SKILL.mdSecurity
2 findings: 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill explicitly describes generating/exporting an agent JSON package that contains the agent private key and asks whether to include the private key in exported JSON, which would require the model to produce secret values verbatim in its output.
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 explicitly implements payment rails and delegated wallet permissions: it describes x402 payment flows (HTTP 402, signed payment payloads), ERC-7710/7715 delegation and wallet permission requests, agent redemption of delegations to produce payment authorizations, concrete spend policies/budgets, demo spend caps (USDC amounts), and steps to generate/import agent wallets and run x402 payment attempts. These are specific financial execution capabilities (sending token payments, redeeming delegated spend, managing budgets), not generic tooling.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
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 runtime workflow ingests only provider-signed x402 HTTP response bodies/headers (payment requirements and evidence/report payloads) from explicitly targeted paid endpoints, not arbitrary outsider-authored free text without selecting a specific resource.
6a6b81d
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.