Edvisage B2a Commerce

v1.0.0

Enables OpenClaw agents to transact autonomously and securely using the x402 open payment protocol with configurable spending limits and safety checks.

1· 40·0 current·0 all-time
byEdvisage Global@edvisage
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description match the content: the SKILL.md is a protocol and safety framework for x402 payments. It does not request unrelated credentials or binaries. However, the skill assumes the agent has a wallet capable of signing payments but declares no integration or credential surface for that wallet — this is reasonable for a guidance-only skill but should be verified in your agent environment.
Instruction Scope
Instructions stay within payment-safety scope (verification checks, spending limits, logging, attack patterns). They do not instruct reading arbitrary files or exfiltrating data, but they leave unspecified where configuration (DAILY_SPEND_LIMIT, wallet storage, human-approval channel, logging destination) is stored and how signing is performed securely. The SKILL.md warns not to expose private keys but does not define a secure key-storage or signing mechanism.
Install Mechanism
Instruction-only skill with no install spec and no code to write to disk; lowest install risk.
Credentials
The skill requests no environment variables or credentials, consistent with being a guidance-only skill. Because it deals with signing payments, you must verify separately how your agent will provide a wallet/private key and ensure that the key storage and signing capability are appropriately constrained (the skill itself does not request or manage secrets).
Persistence & Privilege
Does not request always:true and is user-invocable only. It can be invoked autonomously per platform defaults (normal), so ensure your agent's autonomous signing capability and approval thresholds are enforced elsewhere.
Assessment
This skill is a safety and protocol guide for enabling agent payments and appears coherent, but take these precautions before installing or enabling autonomous payments: - Verify publisher/source: registry metadata shows 'source: unknown' and 'homepage: none' while package.json/README reference edvisageglobal.com and a GitHub repo. Confirm the skill's origin (official Edvisage resources) before trusting it. - Confirm wallet integration: the skill assumes your agent can sign USDC micropayments. Determine where the agent's wallet/private key is stored and how signing is performed; do not allow the skill to access private keys directly. Use an isolated, funded-only-for-operations wallet. - Configure limits and approvals first: set DAILY_SPEND_LIMIT, PER_TRANSACTION_LIMIT, and HUMAN_AUTH_THRESHOLD before enabling autonomous transactions, and test with very low limits or in a sandbox environment. - Enforce human approval for non-trivial amounts: rely on platform controls or agent policies to require explicit human confirmation for transactions above a conservative threshold. - Audit logging and monitoring: ensure transaction logs (timestamps, domains, tx hashes) are sent to a secure location and weekly summaries go to a human you trust. - Sandbox test: run the agent in a controlled environment with minimal funds to verify the flow and that it never exposes keys in logs or messages. If you want higher assurance, request the skill provider's source repository and an implementation example showing how signing is delegated to a secure key manager or hardware-backed wallet; that will raise confidence from medium to high.

Like a lobster shell, security has layers — review code before you run it.

latestvk978zcqtg4p26ftjfsbycap0gh840fbn

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments