Menu
Build natural-language crypto/DeFi agents and EVM MCP plugins (Claude Code, Cursor, Codex, Gemini). Aomi turns prompts into wallet-signed txs on Ethereum, Base, Arbitrum, Optimism, Polygon, Linea — non-custodial, fork-simulated. 40+ apps: Uniswap, Aave, Lido, Morpho, GMX, Hyperliquid, Polymarket.
| name | aomi-transact |
| description | Build natural-language crypto/DeFi agents and EVM MCP plugins (Claude Code, Cursor, Codex, Gemini). Aomi turns prompts into wallet-signed txs on Ethereum, Base, Arbitrum, Optimism, Polygon, Linea — non-custodial, fork-simulated. 40+ apps: Uniswap, Aave, Lido, Morpho, GMX, Hyperliquid, Polymarket. |
| risk | critical |
| source | aomi-labs/skills (MIT) |
| source_repo | aomi-labs/skills |
| license | MIT |
| license_source | https://github.com/aomi-labs/skills/blob/main/LICENSE |
| date_added | 2026-05-06 |
| tags | ["defi","wallet","account-abstraction","cli","eip-712","onchain","agent","intent"] |
Authorized use only. This skill signs and broadcasts on-chain transactions on the user's behalf. The user must explicitly request each signing step. The skill will not run
aomi tx signwithout an explicit user request and a correspondingtx-Nqueued byaomi tx list.Signing gate. Do not include
aomi tx signin a copied or runnable multi-command block. Stop after listing or simulating queued transactions, summarize the tx ids, chain, value, recipient, calldata purpose, and simulation result, then ask the user for an explicit signing instruction such assign tx-1. Only run the exact signing command after that separate approval.
aomi-transact is a procedure for driving the Aomi CLI (@aomi-labs/client) from natural-language prompts. The user types something like "swap 1 ETH for USDC on Uniswap"; the agent picks the right protocol and contract, stages the approve+swap as a batch, simulates it on a forked chain, and returns a queued wallet request for the user to sign. The wallet only ever sees calldata that already passed simulation.
The CLI is account-abstraction-first: by default it signs through a zero-config Alchemy proxy (no provider credentials needed), using EIP-7702 on Ethereum mainnet and ERC-4337 on L2s. Each aomi <subcommand> invocation starts, runs, and exits — there is no long-running process.
The full skill including references (account-abstraction.md, apps.md, examples.md, session.md, troubleshooting.md, drain-vectors.md), templates (aomi-workflow.sh), and per-host metadata (agents/openai.yaml) lives upstream at aomi-labs/skills. This entry is the canonical SKILL.md only — clone the upstream for the full bundle.
aomi --prompt "what is the price of ETH?" --new-session
Returns a quote with no wallet request queued. Use aomi tx list to confirm there's nothing pending.
aomi chat "Stake 0.01 ETH with Lido to get stETH" \
--public-key 0xUserAddress --chain 1 --new-session
aomi tx list
submit(address(0)) on Lido stETH 0xae7ab96520DE3A18E5e111B5EaAb095312D7fE84, value = 0.01 ETH. No approve, single tx. Stop here, show the queued transaction details, and wait for the user's explicit instruction before signing.
aomi chat "swap 1 USDC for WETH on Uniswap V3, send to my wallet" \
--public-key 0xUserAddress --chain 1 --new-session
aomi tx list # tx-1 = approve, tx-2 = swap
aomi tx simulate tx-1 tx-2 # mandatory for multi-step
The simulator runs each tx sequentially on a forked chain so the swap step sees the approve's state changes. Don't sign step 2 independently — it would revert. Stop after simulation, summarize the batch, and wait for an explicit user instruction naming both tx ids before signing.
aomi chat "Bridge 50 USDC from Ethereum to Base via CCTP. Recipient is my wallet." \
--public-key 0xUserAddress --chain 1 --new-session
aomi tx list
aomi tx simulate tx-1 tx-2
Stop after simulation and wait for the user to explicitly approve signing the named tx ids. After signing, source-chain burn confirms in 1-2 blocks; destination mint requires Circle's off-chain attestation (~13-19 minutes).
@aomi-labs/client v0.1.30 or newer. Older versions lack --aa, --aa-provider, --aa-mode and the simulation gate. Install with npm install -g @aomi-labs/client or run on demand via npx @aomi-labs/client@0.1.30 ....api.aomi.dev. Without network access, only local read commands (aomi tx list, aomi session log) work.aomi tx sign returns viem's insufficient funds for transfer. Either fund the EOA with a small amount of native gas, or configure a real BYOK Alchemy/Pimlico provider with a sponsorship policy. Do not retry with --eoa — that path also needs gas.binance, polymarket, dune, etc.) must have credentials configured by the user in their own shell or via aomi secret add NAME=<value>. The skill never sets credentials on its own initiative.recipient/onBehalfOf/mintRecipient ≠ msg.sender. This is a security feature, not a bug — surface the block to the user rather than reformulating the prompt.429) or fail auth (401). The user must supply a reliable chain-matching RPC via --rpc-url for production signing.aomi tx list for the latest passing batch.--new-session on the first command of a new task. Reusing it mid-task starts a fresh conversation and the agent loses the quote it just gave you.aomi tx list before aomi tx sign. Never assume a chat response queued a transaction.aomi tx simulate tx-1 tx-2 ... before signing a multi-step batch. Single-tx flows are simulation-optional but never wrong to simulate.aomi tx sign only after the user gives a separate, explicit approval naming the exact queued tx-N ids.Batch [...] passed txs. Skip orphans from earlier failed attempts (failed at step N: 0x...).--rpc-url to the queued tx's chain, not the session chain (--chain) — they are independent controls.This skill can sign and broadcast on-chain transactions worth real value. Use only on accounts you own and on networks you trust. The skill does not custody funds; the user retains full control of signing keys via --public-key and the underlying wallet. Review every queued tx-N before running aomi tx sign.
@aomi-labs/client on npmFor the full skill including per-flow examples (CCTP bridge, Aave supply, Lido stake, Uniswap swap), AA mode reference, drain-vector table, troubleshooting guide, and the bash workflow template, see the upstream repo:
Use when CrossFrame Suite routes explicit Chinese casebook work: turning materials into reusable cases, anonymized entries, mechanisms, and retrieval indexes.
Use only when the user explicitly names crossframe-critical for a Chinese structural critique dossier, article plan, or long-form critical essay.
Use when CrossFrame Suite routes explicit Chinese proposition testing, debate analysis, hidden-premise review, rebuttal design, or withdrawal condition checks.
Use when CrossFrame Suite routes explicit Chinese reader replies, editor responses, consultation-style short answers, or boundary-aware structural advice.
Use when explicit CrossFrame work needs a Chinese critical insight essay, commentary, concept essay, public piece, or structure-to-article draft after diagnosis.
Use when CrossFrame Suite routes explicit Chinese notes for books, theories, articles, excerpts, bidirectional reading, absorption, or conflict mapping.