What happens when AI agents can trade on Sui without ever holding your private keys? @CetusProtocol just launched Cetus Skills, an open set of Claude Code skills that let AI agents plug directly into Cetus infrastructure on @SuiNetwork. Install is one line through the GitHub repo: npx skills add CetusProtocol/cetus-skills Each skill comes with 3 layers: → README.md for humans → SKILL.md, a short reference written for agents → Reference files with detailed schemas, payloads and edge cases So the docs are written for two readers at once for the developer and the agent. Here's what each skill does 👇 🔵 cetus-aggregator (REST API) → Finds the best swap routes across Sui DEXs and builds the swap transaction → The SDK snapshot lists 37 liquidity providers, including Cetus CLMM and DLMM, DeepBook V3, Aftermath, Turbos, FlowX, Bluefin, Haedal, Kriya, Scallop, Suilend, Momentum, Magma and more → Orders can be split up to 50 ways, with up to 3 hops per route → No API key needed The flow is simple: 1. The agent asks the user for the token pair, amount and slippage 2. It gets a quote and shows it to the user 3. Once the user confirms, it builds the transaction 4. The user's wallet signs and submits it 🔵 cetus-clmm (TypeScript SDK + Move) → Create pools, open and close positions with custom tick ranges → Add or remove liquidity with both coins or just one side → Single-pool swaps, plus a way to calculate the swap result before executing → Flash loans: borrow either coin and repay in the same transaction → Collect LP fees and rewards Built for stable pairs and passive LPs. 🔵 cetus-dlmm (TypeScript SDK + Move) → Liquidity sits in discrete price bins instead of continuous ranges → 3 distribution strategies: Spot (even), Curve (concentrated near price), BidAsk (weighted to the edges) → Dynamic fees: a base fee plus a variable fee that rises with volatility → Positions are NFTs that hold shares across multiple bins This is suitable for volatile pairs and active market making. So what actually caught my attention? It's not the "AI era" branding. It's the security design underneath it. 1. Agents never touch private keys Every skill returns an unsigned transaction. The only setting the aggregator needs is a wallet address. → The agent finds the route and builds the transaction → The user's wallet or signer approves it As @suidevelopers put it, an agent that trades shouldn't need to sign its own swaps. 2. Slippage rules are written into the skill → The default is 0.5% → Recommended: 0.5% for stablecoins, 1% for volatile pairs → Anything above 50% gets rejected → The agent is told to always warn the user about slippage risk before building a swap 3. Confirmation is built into the flow The agent shows the quote first and only builds the transaction after the user confirms. Why this matters? Most of the fear around AI agents in DeFi comes down to one thing: handing a bot full control of your funds. Cetus's approach keeps the agent as the one that plans and builds the trade, and the user as the one who approves it. That doesn't remove the risk, but it adds a clear checkpoint between "the agent decided" and "the money moved." But there are still open questions for this 👇 @ZealynxSecurity asked a fair one is that are slippage limits and token allowlists enforced inside the skill, or left to each agent's wallet policy? → The slippage rules are instructions to the agent, not limits enforced on-chain → There's no built-in token allowlist → On-chain, protection comes from the minimum-output and maximum-input limits in each swap So a compromised or prompt-injected agent could still build a bad transaction. The last line of defense is still the signer. That's why the wallet layer matters as much as Cetus itself. Cetus called out @t2000ai, @LoquaApp, @Sup_Wallet and @WaaPxyz as builders working on agent-ready wallets, intent-based interfaces and AI strategies on Sui. If those wallets can enforce spending limits, allowlists and approval rules, the stack gets much safer. So what about the business side? Both CLMM and DLMM include partner versions of their swap functions, and the aggregator accepts a partner ID for referral fee sharing. → Agent builders who route volume through Cetus can get a share of the fees → That gives them a direct reason to integrate, beyond just convenience If agent volume grows, this could become a real distribution channel for Cetus liquidity. How does this fit? → Oct 19: CLMM package upgraded to v15. Integrators had to update, and Epoch had brief downtime before shipping a fix plus a version-check system. No funds were at risk. → Oct 20: Bug bounty on HackenProof raised to $1M for critical findings, with a wider scope → Oct 21: Cetus Skills goes live → Oct 22: Cetus confirmed it doesn't use PHP anywhere and isn't affected by the PHP vulnerability concerns A few notes for builders: → Swap transactions can only be built from a fixed input amount. Fixed-output quotes are for price checks only. → Flash loans are CLMM-only. DLMM doesn't have them. → SDK versions are pinned in the repo as of Oct 21, and it requires Sui SDK 2.x → After the v15 upgrade, the repo recommends reading contract addresses from the SDK config instead of hardcoding them I think this is a smart move tbh. Agents need deep markets to trade in. On Sui, Cetus is already the main liquidity and routing layer. Making that layer easy for agents to use is a natural next step. But it's still very early. The repo has only been public for a few days, and the real test is whether agents bring real volume and fees, not just demos. As one community member pointed out under the announcement, what matters next is the impact on trading volume and protocol revenue. The bigger question for me is whether agent-driven flow becomes a real source of revenue for Cetus, or stays a developer experiment for now. That's what I'll be watching for now. NFA. DYOR.