mev-protection-guide

Identify MEV attack patterns and recommend transaction-protection strategies for DEX swaps.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/nirholas/three-ui --skill mev-protection-guide-nirholas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mev-protection-guide
Source: https://github.com/nirholas/three-ui/tree/main/data/skills/security/mev-protection-guide
Command: npx skills add https://github.com/nirholas/three-ui --skill mev-protection-guide-nirholas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MEV (Maximal Extractable Value) attacks reorder, include, or exclude blockchain transactions to extract profit at the expense of traders, causing worse execution prices than expected.

Core Features & Use Cases

  • Explain MEV attack types: Covers sandwich attacks, frontrunning, backrunning, JIT liquidity, and time-bandit attacks in clear, user-facing terms.
  • Recommend practical defenses: Guides users toward low slippage, private transaction submission (e.g., Flashbots Protect), DEX aggregators, and gasless limit orders to reduce or eliminate MEV exposure.
  • Help detect suspicious patterns: Identifies likely sandwich/arbitrage behavior by examining transaction timing, price impact, and repeated addresses around the target swap.
  • Use Case: A user planning a large token swap can follow the guide to reduce sandwich risk by lowering slippage, using a private relay, and/or routing through an aggregator, then validating the outcome against expected vs actual received amounts.

Quick Start

Ask the agent to generate a MEV protection plan for my DEX swap, including recommended slippage settings, private relay options, and how to detect sandwich indicators after execution.

Frequently Asked Questions about mev-protection-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a sandwich attack in DEX swaps and how does MEV extraction work?

MEV extraction reorders or includes blockchain transactions to profit at a trader's expense. A sandwich attack specifically frontruns and backruns your DEX swap, causing worse execution prices and unexpected slippage.

How do I protect my DEX swaps from frontrunning and sandwich attacks?

Protect DEX swaps from frontrunning by lowering slippage settings, submitting transactions through private mempools like Flashbots Protect, routing through DEX aggregators, or using gasless limit orders to reduce MEV exposure.

How can I detect if my transaction was targeted by a sandwich attack?

Detect sandwich attacks by examining transaction timing, price impact, and repeated addresses around your target swap. Analyzing expected versus actual received amounts helps identify suspicious arbitrage behavior.

Does using a private relay like Flashbots Protect eliminate slippage on DEX swaps?

Flashbots Protect prevents MEV bots from seeing and frontrunning your transaction in the public mempool. While it eliminates sandwich risk, you must still configure low slippage settings to manage legitimate price impact.

What's the best way to execute a large token swap without losing value to MEV?

For large token swaps, combine MEV defenses by lowering slippage, routing through a DEX aggregator for better pricing, and submitting via a private relay to prevent sandwich attacks and minimize extractable value loss.