agentleFS
SperaxSperax/sperax-skills/skills/token-approval-safety/SKILL.md

token-approval-safety

Skill8 starsChanged 9 months agoMITView on GitHub

Guide to ERC-20 token approvals — how they work, why unlimited approvals are risky, how to check and revoke approvals, and best practices. Use when helping users manage approvals, audit wallet security, or understand approval-related risks.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 13 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you interact with a DeFi protocol, you must first "approve" it to spend your tokens:

    line 13
  2. Distinctive:

    If the protocol gets hacked, attackers drain your tokens via the approval

    line 26
  3. Distinctive:

    After you're done using a protocol

    line 69
  4. Distinctive:

    If a protocol announces a security incident

    line 70
  5. Distinctive:

    Before a token migration or contract upgrade

    line 72
  6. Distinctive:

    Prevention: Always verify the contract address before approving

    line 83
  7. Distinctive:

    If a protocol with your approval gets hacked:

    line 87
  8. Distinctive:

    Prevention: Use exact-amount approvals, revoke unused approvals

    line 91
  9. Distinctive:

    No on-chain transaction to alert you

    line 99
  10. Distinctive:

    Prevention: Read what you're signing carefully, use wallets that show permit details

    line 101
  11. Distinctive:

    Use exact-amount approvals: when possible

    line 107
  12. Distinctive:

    Batch revocations: when gas is low

    line 116
  13. Distinctive:

    When helping users with approvals:

    line 131

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Token Approval Safety Guide

Token approvals are one of the most overlooked security risks in DeFi. This guide helps AI agents protect users from approval-related attacks.

How Approvals Work

When you interact with a DeFi protocol, you must first "approve" it to spend your tokens:

1. You call approve(spenderAddress, amount) on the token contract
2. The spender (DEX, protocol) can now transfer up to `amount` of your tokens
3. When you swap/deposit, the protocol calls transferFrom() to move your tokens

The Problem: Unlimited Approvals

Most DeFi UIs request unlimited approval (type(uint256).max):

  • Saves gas on future interactions (no re-approval needed)
  • But: the protocol can spend ALL your tokens FOREVER
  • If the protocol gets hacked, attackers drain your tokens via the approval

Risk Levels

Approval TypeRiskWhen to Use
Exact amountLowLarge deposits, untrusted protocols
Limited amountMediumRegular use with trusted protocols
UnlimitedHighOnly with battle-tested protocols (Uniswap, Aave)
Permit (EIP-2612)MediumGasless approvals, common in modern DeFi

How to Check Approvals

On-Chain (Direct)

Query the token contract: allowance(ownerAddress, spenderAddress)

Tools

ToolURLFeatures
Revoke.cashhttps://revoke.cashMost popular, multi-chain
Etherscan Token Approvalshttps://etherscan.io/tokenapprovalcheckerEthereum-only
Arbiscanhttps://arbiscan.io/tokenapprovalcheckerArbitrum

What to Look For

  • Unlimited approvals to contracts you no longer use
  • Approvals to unknown contracts you don't recognize
  • Old approvals from months/years ago
  • Approvals for valuable tokens (USDC, USDT, WETH)

Revoking Approvals

Revoking sets the allowance to 0:

approve(spenderAddress, 0)

Cost: Small gas fee per revocation

When to revoke:

  • After you're done using a protocol
  • If a protocol announces a security incident
  • During regular security checkups (monthly recommended)
  • Before a token migration or contract upgrade

Common Attack Vectors

1. Approval Phishing

Attacker tricks you into approving a malicious contract:

  • Fake DEX frontends
  • Phishing links disguised as protocol UIs
  • "Claim airdrop" scam sites

Prevention: Always verify the contract address before approving

2. Compromised Protocol

If a protocol with your approval gets hacked:

  • Attacker can drain your approved tokens immediately
  • They don't need your private key — just the approval

Prevention: Use exact-amount approvals, revoke unused approvals

3. Permit Signature Phishing

EIP-2612 permits are signed off-chain (no gas). Attackers can trick you into signing a permit that grants them unlimited approval:

  • Looks like a harmless "sign this message" request
  • Actually authorizes token spending
  • No on-chain transaction to alert you

Prevention: Read what you're signing carefully, use wallets that show permit details

Best Practices

For Regular Users

  1. Use exact-amount approvals when possible
  2. Review approvals monthly using Revoke.cash
  3. Revoke approvals to protocols you no longer use
  4. Use a dedicated DeFi wallet — don't hold all tokens where you approve
  5. Read approval prompts — check the spender address matches the expected protocol

For Frequent DeFi Users

  1. Separate hot/cold wallets — cold wallet for storage, hot wallet for DeFi
  2. Batch revocations when gas is low
  3. Prefer EIP-2612 permits for modern protocols (single-use)
  4. Set up alerts for large approval events on your address
  5. Audit before depositing large amounts — check existing approvals first

Approval Hygiene Checklist

  • Check all active approvals at least monthly
  • Revoke any approvals to contracts you don't recognize
  • Revoke approvals to protocols you've stopped using
  • Use exact amounts for new approvals when available
  • Verify contract addresses on block explorers before approving

Agent Tips

When helping users with approvals:

  1. Always warn about unlimited approvals — suggest exact-amount when possible
  2. Before any large DeFi interaction — suggest checking existing approvals
  3. After security incidents — immediately recommend revoking approvals to affected protocol
  4. New users — explain approvals before their first DeFi transaction
  5. Gas consideration — revocations cost gas, batch them when gas is low

Links

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.