Agent Metaverse
PassAudited by ClawScan on May 1, 2026.
Overview
This looks like a coherent virtual crypto-trading client, but installing it lets the agent use an API key to make trades in the virtual exchange account.
Install only if you want an agent to interact with this virtual exchange. Keep the AGENT_METAVERSE_API_KEY private, use a trusted AGENT_METAVERSE_BASE_URL, and supervise trading actions if the virtual account balance or leaderboard outcome matters to you.
Findings (4)
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.
The agent could place spot, futures, or AMM trades in the virtual exchange account if invoked with the API key.
The skill exposes authenticated commands that open leveraged futures positions, which is expected for a virtual trading skill but can change the user's virtual account state.
resp = c.post("/api/futures/open", json={"pair": args.pair, "side": "long", "leverage": args.leverage, "quantity": args.quantity})Only provide the API key if you are comfortable with the agent changing this virtual portfolio, and supervise trading commands if you care about the account outcome.
Anyone or any process with this API key may be able to view balances and make virtual trades for that account.
The script reads an exchange API key from the environment and sends it as an authentication header; this is purpose-aligned but gives the skill access to the virtual exchange account.
API_KEY = os.environ.get("AGENT_METAVERSE_API_KEY", "") ... headers["X-API-Key"] = API_KEYTreat the API key as a secret, avoid sharing it, and rotate or revoke it if it is exposed.
A future dependency version could behave differently from the version the author tested.
The dependency is specified with a lower-bound version rather than a pinned exact version, which is common but gives less reproducible dependency provenance.
httpx>=0.28.0
If you install dependencies yourself, prefer a pinned and reviewed dependency set in a controlled environment.
The registry may not clearly warn users during installation that an API key is needed.
The registry metadata does not declare the credential requirement, while the skill documentation and code use AGENT_METAVERSE_API_KEY. This appears under-declared rather than hidden because SKILL.md discloses it.
Required env vars: none ... Primary credential: none
Expect to provide AGENT_METAVERSE_API_KEY for authenticated commands and verify the skill metadata before relying on automated permission prompts.