Agents may need regional egress without managing a long-term proxy subscription. This skill guides approved USDC purchases, token management, and TLS proxy verification.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "x402socks" from https://skillstore.io/skills/x402socks-x402socks.md and its manifest at https://skillstore.io/api/skills/x402socks-x402socks/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Most static matches are Markdown, local signing, private token storage, or disclosed HTTPS service requests. Confirmed transport risks expose credentials when plaintext proxy modes or insecure API overrides are enabled; newline handling also permits curl configuration injection. No evidence found of malicious exfiltration intent or prompt injection.
cfg_escape escapes quotes and backslashes but leaves line breaks intact. Environment-supplied tokens or endpoint URLs can therefore inject additional curl options through generated configuration. If attacker-controlled, these values could disable TLS checks or attach local files to requests.
The source preserves environment-token newlines and interpolates them into curl configuration without rejection. A local curl parser check accepted an injected configuration line; exploitation requires control of a token or endpoint environment value.
Capability review items (9)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
| SOCKS5 | `socks5h://<exit>.x402socks.com:1080` | Every exit |
The documented legacy transport sends proxy authentication in cleartext. Explicit opt-in and trusted-network warnings reduce exposure but do not encrypt the reusable token.
The helper exposes both under `test --plaintext` / `test --socks5` with
The documented legacy transport sends proxy authentication in cleartext. Explicit opt-in and trusted-network warnings reduce exposure but do not encrypt the reusable token.
For SOCKS5 use `socks5h://<exit>.x402socks.com:1080` so the exit resolves DNS.
The documented socks5h transport protects remote DNS placement, not proxy authentication. The reusable token remains visible on the client-to-proxy network.
The explicit insecure-API override permits credential-bearing HTTP requests. Network observers can capture tokens or recovery signatures when this override is enabled.
The explicit insecure-API override permits credential-bearing HTTP requests. Network observers can capture tokens or recovery signatures when this override is enabled.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
x402socks. (2026). x402socks security audit report (audit version 6) [Author version 1.3.0]. Skillstore. https://skillstore.io/skills/x402socks-x402socks/audits/6
BibTeX citation
@techreport{x402socks-x402socks-x402socks-2026,
author = {x402socks},
title = {x402socks security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/x402socks-x402socks/audits/6},
note = {Author version 1.3.0}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "x402socks security audit report (audit version 6)"
version: "1.3.0"
type: report
authors:
- name: "x402socks"
date-released: "2026-11-10"
url: "https://skillstore.io/skills/x402socks-x402socks/audits/6"
identifiers:
- type: other
value: "skillstore:x402socks-x402socks:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: Medium
95
Architecture
100
Maintainability
87
Content
65
Community
91
Spec Compliance
What You Can Build
Check Regional Browser Behavior
Configure a TLS proxy for Playwright tests and verify that requests leave through the selected region.
Plan an Approved Data Collection Job
Compare current proxy packages for permitted collection work and request approval before authorizing payment.
Restore Existing Proxy Access
Diagnose token validity, rotate exposed credentials, or recover a lost token using proof from the paying wallet.
Try These Prompts
Inspect Available Proxy Access
Check x402socks health, available TLS exits, and current packages. Summarize options without accessing wallet secrets or making a purchase.
Prepare a Purchase Approval
Quote [package_id] with a maximum of [amount] USDC. Record all payment terms and entitlements, then wait for explicit approval before signing.
Verify a TLS Proxy Exit
Use my existing token file to validate access and test [exit_id] through TLS CONNECT. Report the egress comparison without displaying credentials.
Integrate Guarded Proxy Purchasing
Adapt the TypeScript payment example for [application]. Pin approved terms before signing, require purchase approval, save tokens privately, and redact secrets from diagnostics.
Best Practices
Approve the full live payment terms and a spending cap before signing; stop when the challenge differs.
Use certificate-verified TLS CONNECT and private token files; reject control characters in environment credentials and endpoint overrides.
Keep settlement proof and validate existing access before retrying; use recovery instead of paying twice.
Avoid
Automatically pay from cached package prices or accept changed recipients, assets, networks, or signing domains.
Paste wallet keys or live proxy tokens into chat, command arguments, source control, or logs.
Disable certificate verification or treat SOCKS5 and plaintext CONNECT as encrypted alternatives.
Frequently Asked Questions
What is required to purchase access?
You need USDC on Base, an accessible wallet signer, and an x402 client. The helper handles discovery and token management, not payment execution.
Does the skill require approval before spending?
Yes. Its instructions require explicit approval and comparison of the live challenge against approved terms before signing.
Which proxy transport should I use?
Prefer certificate-verified TLS CONNECT on port 3129. SOCKS5 and plaintext CONNECT expose the reusable token on the client-to-proxy connection.
Which tools and clients are documented?
The helper uses Bash, curl, and Python. References cover Foundry cast, TypeScript and Python payments, Node.js, Playwright, and Chrome.
Does a different egress IP guarantee anonymity?
No. An egress check verifies routing, not anonymity. The proxy operator and destination may still observe identifying information.
What should I do after losing a token?
Use the settlement transaction hash and paying wallet to sign a recovery message. Save the replacement privately rather than purchasing again.