Agent Market
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill appears purpose-aligned for Base Sepolia prediction markets, but it uses a raw wallet private key and can sign spending/resolution transactions while the registry metadata does not declare any credential or environment requirement.
Install only if you are comfortable giving the skill a dedicated Base Sepolia wallet private key and manually approving each transaction. Do not use a wallet key that controls real assets on any chain, verify the factory/USDC contract addresses, and treat market resolution actions as public, persistent decisions.
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.
If configured with a reused or funded private key, the skill can sign transactions from that wallet; users may not receive normal credential warnings because the metadata under-declares it.
The code turns WALLET_PRIVATE_KEY into a signing wallet client. This is expected for blockchain transactions, but it is high-impact credential authority and the registry metadata declares no env vars or primary credential.
const PRIVATE_KEY = process.env.WALLET_PRIVATE_KEY as `0x${string}`; ... const account = PRIVATE_KEY ? privateKeyToAccount(PRIVATE_KEY) : undefined; ... createWalletClient({ account, chain: baseSepoliaUse only a dedicated Base Sepolia test wallet with minimal funds, never reuse a main wallet key, and require the skill/registry metadata to declare WALLET_PRIVATE_KEY and its transaction-signing scope.
A mistaken or overly broad agent instruction could place unintended trades, provide liquidity, or post oracle bonds.
The documented tools place bets and post bonds. This is central to the skill's purpose and disclosed, but each invocation can spend or lock USDC and pay gas.
market_buy_yes({ marketAddress, amount: 5 }) — Bet 5 USDC on YES ... market_propose_outcome({ marketAddress, outcome: true }) — Propose YES won (posts bond)Review the market address, amount, outcome, and expected costs before every transaction; prefer explicit per-transaction confirmation and spending limits.
A wrong proposed or finalized outcome can change payouts for the market, not just the installing user's wallet.
Resolution actions can affect the public market state and other participants' payouts if an incorrect proposal is finalized.
If unchallenged, the proposal finalizes ... winners split the entire USDC pool proportional to their token holdings. Losers get nothing.
Only propose or finalize outcomes after verifying the real-world result and the dispute window; avoid letting the agent infer outcomes from uncertain information.
It is harder to verify that the installed code and dependencies match the intended AgentMarket project.
The registry provenance and install context are incomplete even though code files are present and the SKILL.md links to an external GitHub project.
Source: unknown; Homepage: none ... Install specifications: No install spec — this is an instruction-only skill.
Review the linked source repository, verify contract addresses, and use pinned/reviewed dependencies before configuring a wallet key.