Skip to content

aomi-labs/skills / plugins/aomi/skills/transact

aomi-transact

Verified

Build natural-language crypto agents, web3 assistants, and trading bots that read and write EVM chain state. Aomi turns prompts ("swap 1 ETH for USDC", "open a 3x GMX long", "bet $100 on Polymarket") into wallet-signed transactions on Ethereum, Base, Arbitrum, Optimism, Polygon, Linea — non-custodial, fork-simulated. Use when the user wants a crypto/DeFi agent, AI trading/wallet assistant, or on-chain execution against Uniswap, Aave, Lido, GMX, Hyperliquid, Polymarket, Binance, OKX, or 40+ other protocols. Trigger with prompts about swaps, lending, bridging, staking, perps, prediction markets, or any DeFi/CEX action needing a wallet signature. Supports durable Commit review and backend-prepared EVM or AA signing. MUST NOT fabricate or echo credentials; values reach the CLI only when the user explicitly supplied them.

Aomi Transact

Use the TypeScript aomi CLI to prepare, review and execute user-authorized transactions. The Rust aomi-cli in product-mono has a different interface.

Procedure

  1. Establish capabilities. Read commands.md first. Check package availability and installed help; a source test or SDK migration message does not prove a working published CLI. Stop a missing capability branch with its release requirement; keep a working older binary.
  2. Resolve funding. Identify the requested recipient, amount, destination chain ID and token contract. Read the user's wallet catalog for operational addresses and known funded chains. Check live token and native gas balances across those positions before preparing a payment. A zero Ethereum USDC balance is not a wallet-wide shortfall. Use tx preflight when available; follow funding checks otherwise. Keep a treasury/Safe refill as a separately authorized source choice.
  3. Bind the intent. Show the selected sender, source asset/chain, destination asset/chain, amount, recipient, estimated fees and shortfall. For conversion or bridging, obtain a fresh quote with minimum destination output, gas on each leg and route fees. USDC and USDG are different contracts/assets. Finish this step with unambiguous, funded terms before building a payment.
  4. Prepare once. On a new task use aomi chat "<exact intent>" --new-session --public-key <sender> --chain <chain-id>. Continue its original session on follow-ups. Read aomi tx list --json, retain the full Commit ID and export that exact Commit with aomi tx export <commit-id> --format commit.
  5. Review. Match the durable review to the approved intent, including sender, chain, token, amount, recipient, calldata, fees and simulation. Check all legs and approval limits. Simulation for a Commit lives in its review; tx simulate is a separate legacy Action tool. Require passed simulation for execution.
  6. Execute the reviewed Commit. Use aomi tx sign <commit-id> only within the user's authorization and an available designated signer. For an external signer, preserve the exact export and report the signed payloads or prepared broadcast hash through tx submit; see workflows.md. Inspect prepared AA payloads before choosing the signing path; see account-abstraction.md.
  7. Reconcile the same payment. Retain original session, full Commit ID, approved intent and transaction hash together. Refresh that Commit with aomi tx list --json before retrying; the backend observes the receipt and moves it to confirmed. A known hash or outstanding wallet attempt calls for reconciliation, not a new signing attempt. Report preparation, simulation, signature, submission and confirmation separately. Bridge completion also needs the destination receipt and spendable output token.

Credentials and state

Use the existing authorized signer without exposing key material. Credential setup is a separate user-directed operation; values stay opaque and out of chat, logs, fixtures and exported payment records. ~/.aomi may contain signing keys, bearers and secret handles. Its permission manifest expresses intended scope; actual enforcement depends on the host. For credential handling, local state and recovery, read gotchas.md and session.md.

Branch references

  • 404, missing package, timeout or retry: troubleshooting.md.
  • Commands, installation and flags: commands.md.
  • Funding, execution and secret ingestion: workflows.md.
  • Direct payment or bridge walkthrough: examples.md.
  • Protocol field/recipient warnings: drain-vectors.md.
  • App discovery and prompt examples: apps.md; runtime capabilities and this procedure take precedence over historical app examples.

Source: https://github.com/aomi-labs/skills/tree/main/aomi-transact

Hosted MCP

Use https://aomi.chat as the production origin. If your CLI still targets the retired host, run aomi config set-backend https://aomi.chat and update any AOMI_BACKEND_URL or --backend-url override. For an existing MCP connection, change its URL and authorize again; old-origin OAuth grants do not carry over.

For hosted tools, connect Agent and Pipeline separately with OAuth:

codex mcp add aomi-agent --url https://aomi.chat/v1/agent/mcp
codex mcp add aomi-pipeline --url https://aomi.chat/v1/pipeline/mcp

Codex derives the resource from each URL; omit --oauth-resource to avoid a second resource parameter. If the authorization page reports a CIMD metadata fetch error, retry that server's login with --oauth-client-registration dcr. Use a fresh client session to discover both tool sets, then perform a read-only session-list or catalog call. Enabled configuration alone is not a successful smoke.

Each grant must have the exact connected resource URL as its audience. Agent, Pipeline, REST and guest credentials are not interchangeable. OAuth grants tool access; wallet execution still follows the approved Commit and designated signer. A browser GET can return 404 because these resources accept POST and OPTIONS.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall