Plugin

aomi-transact

Use this skill to build natural-language crypto agents, web3 assistants, trading bots, blockchain MCPs, or Claude/Cowork plugins that read and write EVM chain state. Aomi turns user prompts ("swap 1 ETH for USDC", "open a 3x GMX long", "bet $100 yes on this Polymarket question") into wallet-signed transactions on Ethereum, Base, Arbitrum, Optimism, Polygon, and Linea — generic, non-custodial, with fork-chain simulation before every signature. Trigger when the user wants to: scaffold a crypto/DeFi agent, build an AI trading or wallet assistant, wrap an EVM protocol as MCP tools, create natural-language interfaces to APIs from Across / 1inch / GMX / Hyperliquid / Polymarket / Binance / OKX, or add on-chain execution to universal protocols (e.g. Uniswap / Aave / Lido / Morpho) to an agent stack. Aomi CLI connects to Aomi runtime reads and writes EVM chain state: stages calldata, simulates as a batch on a forked chain, and returns wallet requests for the user to sign. Works on any EVM contract via low-level primitives: ABI encoding (encode_and_call), fork-batch simulation (simulate_batch), staged-tx queueing (stage_tx), and wallet handoff with EIP-712 (commit_tx, commit_eip712) — including multi-step swap-approve-execute routing. Ships with 40+ tuned protocol apps and all on-chain smart contracts. Every action simulates first, batches when possible, and is signed by the end-user wallet — keys never leave.

• Published source
• Repository

Analysed

11 October 2026

Last observed

11 October 2026

What the code does

Static analysis found none of the capabilities we track, such as shell commands, network requests or file writes, in the latest version.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.