defi-amm-security
- Use it when:
- You're writing or auditing an AMM, liquidity pool, LP vault or swap function in Solidity.
- It does:
- Pairs each vulnerability with vulnerable and hardened code, using OpenZeppelin's ReentrancyGuard, SafeERC20 and Ownable2Step, a Uniswap V3 TWAP read and FullMath.
- You get:
- Code checked against an 11-item checklist, plus Slither static analysis and Echidna and Foundry fuzzing commands to run before production.
- Unlike solidity-security:
- That one, wshobson's, covers smart contracts broadly; this one targets pool share math, reserves and swap paths.
TL;DR
A checklist and pattern library from ECC for DeFi pool contracts. The agent reviews every user entrypoint against six areas, each with vulnerable and safe code. Reentrancy: follow checks-effects-interactions order and use OpenZeppelin's nonReentrant rather than a hand-rolled guard. Donation or inflation attacks: don't base share math on the contract's raw token balance, which anyone can inflate by sending tokens to it; track assets internally and measure what a deposit actually received. Oracle manipulation: spot prices can be moved with a flash loan, so read a time-weighted average price (TWAP) instead. Slippage: every swap takes a caller-set minimum output and a deadline. Reserve math: use mulDiv instead of a naive multiply-then-divide where overflow is possible. Admin controls: two-step ownership transfer and access control on every privileged path, such as fee setters and pausers. It ends with Slither, Echidna and forge fuzz commands, and says to run them only in a trusted checkout, ask before long or costly runs, and keep private keys and secrets out of commands and reports.
Summarizes the skill at d2ef268.
npx skills add https://github.com/affaan-m/ecc --skill defi-amm-security More weekly downloads than 57% of skills
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 254 |
| Sep 28 | 159 |
| Oct 5 | 138 |
| Oct 12 | 230 |
| Oct 19 | 408 |
| Oct 26 | 399 |
| Nov 2 | 468 |
| Nov 9 | 442 |
Fewer downloads than 91% of skills
More stars than 97% of repos
Newer than 66% of skills
| Category |
Compliance, guardrails, skill vetting and browser fingerprinting. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
Knowledge and rules the agent applies while it works: best practices, design principles, API references. |
| Effect |
Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics | |
| Stack |
SKILL.md
From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: defi-amm-security
description: Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math. Use when auditing or writing Solidity AMM, liquidity pool, or swap code.
metadata:
version: "1.0.0"
origin: ECC direct-port adaptationDeFi AMM Security
Critical vulnerability patterns and hardened implementations for Solidity AMM contracts, LP vaults, and swap functions.
When to Use
- Writing or auditing a Solidity AMM or liquidity-pool contract
- Implementing swap, deposit, withdraw, mint, or burn flows that hold token balances
- Reviewing any contract that uses
token.balanceOf(address(this))in share or reserve math - Adding fee setters, pausers, oracle updates, or other admin functions to a DeFi protocol
How It Works
Use this as a checklist-plus-pattern library. Review every user entrypoint against the categories below and prefer the hardened examples over hand-rolled variants.
Execution Safety
The shell commands in this skill are local audit examples. Run them only in a trusted checkout or disposable sandbox, and do not splice untrusted contract names, paths, RPC URLs, private keys, or user-supplied flags into shell commands. Ask before installing tools or running long fuzzing/static-analysis jobs that may consume significant local or paid resources.
Never include secrets, private keys, seed phrases, API tokens, or mainnet signing credentials in command examples, logs, or reports.
Examples
Reentrancy: enforce CEI order
Vulnerable:
function withdraw(uint256 amount) external {
require(balances[msg.sender] >= amount);
token.transfer(msg.sender, amount);
balances[msg.sender] -= amount;
}
Safe:
import {ReentrancyGuard} from "@openzeppelin/contracts/utils/ReentrancyGuard.sol";
import {SafeERC20} from "@openzeppelin/contracts/token/ERC20/utils/SafeERC20.sol";
using SafeERC20 for IERC20;
function withdraw(uint256 amount) external nonReentrant {
require(balances[msg.sender] >= amount, "Insufficient");
balances[msg.sender] -= amount;
token.safeTransfer(msg.sender, amount);
}
Do not write your own guard when a hardened library exists.
Donation or inflation attacks
Using token.balanceOf(address(this)) directly for share math lets attackers manipulate the denominator by sending tokens to the contract outside the intended path.
// Vulnerable
function deposit(uint256 assets) external returns (uint256 shares) {
shares = (assets * totalShares) / token.balanceOf(address(this));
}
// Safe
uint256 private _totalAssets;
function deposit(uint256 assets) external nonReentrant returns (uint256 shares) {
uint256 balBefore = token.balanceOf(address(this));
token.safeTransferFrom(msg.sender, address(this), assets);
uint256 received = token.balanceOf(address(this)) - balBefore;
shares = totalShares == 0 ? received : (received * totalShares) / _totalAssets;
_totalAssets += received;
totalShares += shares;
}
Track internal accounting and measure actual tokens received.
Oracle manipulation
Spot prices are flash-loan manipulable. Prefer TWAP.
uint32[] memory secondsAgos = new uint32[](2);
secondsAgos[0] = 1800;
secondsAgos[1] = 0;
(int56[] memory tickCumulatives,) = IUniswapV3Pool(pool).observe(secondsAgos);
int24 twapTick = int24(
(tickCumulatives[1] - tickCumulatives[0]) / int56(uint56(30 minutes))
);
uint160 sqrtPriceX96 = TickMath.getSqrtRatioAtTick(twapTick);
Slippage protection
Every swap path needs caller-provided slippage and a deadline.
function swap(
uint256 amountIn,
uint256 amountOutMin,
uint256 deadline
) external returns (uint256 amountOut) {
require(block.timestamp <= deadline, "Expired");
amountOut = _calculateOut(amountIn);
require(amountOut >= amountOutMin, "Slippage exceeded");
_executeSwap(amountIn, amountOut);
}
Safe reserve math
import {FullMath} from "@uniswap/v3-core/contracts/libraries/FullMath.sol";
uint256 result = FullMath.mulDiv(a, b, c);
For large reserve math, avoid naive a * b / c when overflow risk exists.
Admin controls
import {Ownable2Step} from "@openzeppelin/contracts/access/Ownable2Step.sol";
contract MyAMM is Ownable2Step {
function setFee(uint256 fee) external onlyOwner { ... }
function pause() external onlyOwner { ... }
}
Prefer explicit acceptance for ownership transfer and gate every privileged path.
Security Checklist
- Reentrancy-exposed entrypoints use
nonReentrant - CEI ordering is respected
- Share math does not depend on raw
balanceOf(address(this)) - ERC-20 transfers use
SafeERC20 - Deposits measure actual tokens received
- Oracle reads use TWAP or another manipulation-resistant source
- Swaps require
amountOutMinanddeadline - Overflow-sensitive reserve math uses safe primitives like
mulDiv - Admin functions are access-controlled
- Emergency pause exists and is tested
- Static analysis and fuzzing are run before production
Audit Tools
pip install slither-analyzer
slither . --exclude-dependencies
echidna-test . --contract YourAMM --config echidna.yaml
forge test --fuzz-runs 10000