token

Detect token-related smart contract vulnerabilities and provide mitigation strategies.

60|18|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/PurpleAILAB/Vigilo --skill token-purpleailab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token
Source: https://github.com/PurpleAILAB/Vigilo/tree/main/packages/claude/skills/vulnerability-patterns/token
Command: npx skills add https://github.com/PurpleAILAB/Vigilo --skill token-purpleailab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and mitigate risks associated with various types of non-standard ERC20 tokens, preventing potential exploits and financial loss in smart contract audits.

Core Features & Use Cases

  • Vulnerability Detection: Identifies common pitfalls like fee-on-transfer, rebasing tokens, ERC777/721/1155 callback issues, missing return values, blacklisting/pausable tokens, low decimals, and approval race conditions.
  • Secure Coding Patterns: Provides examples of how to securely interact with these token types.
  • Use Case: When auditing a DeFi protocol that accepts user deposits of various tokens, this Skill can flag potential issues if the protocol doesn't correctly handle a fee-on-transfer token, leading to incorrect balance calculations.

Quick Start

Analyze the provided Solidity code for potential vulnerabilities related to fee-on-transfer tokens.

Frequently Asked Questions about token

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

FAQPage Schema
How do I audit smart contracts for fee-on-transfer token vulnerabilities?

This Skill detects fee-on-transfer vulnerabilities by analyzing Solidity code to ensure balance checks account for transfer deductions, preventing incorrect accounting and potential exploits in DeFi protocols.

What are common ERC20 token vulnerabilities in DeFi protocols?

Common ERC20 token vulnerabilities include missing return values, rebasing mechanisms, blacklisting, low decimals, and approval race conditions, all of which can cause unexpected contract failures or exploits.

How do ERC777 and ERC721 callbacks create security risks in smart contracts?

ERC777 and ERC721 callbacks create security risks by allowing attackers to re-enter contract functions during token transfers, potentially bypassing state updates and draining funds before execution completes.

Can I use this to check Solidity code for rebasing token issues?

Yes, you can use this to check Solidity code for rebasing token issues by identifying if the protocol correctly handles dynamic supply changes that can break balance ratios and liquidity pool math.

How do I prevent approval race condition exploits in ERC20 tokens?

Prevent approval race condition exploits in ERC20 tokens by implementing secure coding patterns that require setting allowances to zero before setting a new value, mitigating front-running risks during transaction submission.

Does this Skill provide secure coding patterns for interacting with non-standard tokens?

Yes, this Skill provides secure coding patterns for interacting with non-standard tokens, offering specific mitigation strategies and a Token Compatibility Matrix to safely handle pausable or blacklisted assets.