token-integration-analyzer

Analyze Solidity smart contracts for token integration security risks.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/keremtoker468-dotcom/restoran --skill token-integration-analyzer-keremtoker468-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-integration-analyzer
Source: https://github.com/keremtoker468-dotcom/restoran/tree/main/.claude/skills/token-integration-analyzer
Command: npx skills add https://github.com/keremtoker468-dotcom/restoran --skill token-integration-analyzer-keremtoker468-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill systematically analyzes smart contracts for security vulnerabilities and non-standard behaviors related to token implementations and integrations, preventing costly exploits.

Core Features & Use Cases

  • Token Implementation Analysis: Checks ERC20/ERC721 conformity and identifies risky patterns.
  • Token Integration Safety: Assesses how protocols handle external tokens, including non-standard ones.
  • On-chain Scarcity Analysis: Evaluates token distribution and supply risks.
  • Use Case: A DeFi protocol integrating multiple ERC20 tokens can use this Skill to ensure it safely handles tokens with unexpected behaviors like fees on transfer or missing return values, preventing loss of user funds.

Quick Start

Analyze the provided Solidity smart contract for token integration risks.

Frequently Asked Questions about token-integration-analyzer

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

FAQPage Schema
How do I audit smart contracts for token integration security risks?

To audit smart contracts for token integration security risks, you analyze ERC20/ERC721 conformity, contract composition, and owner privileges using Trail of Bits' checklist and Slither to identify known weird token patterns.

What are weird token patterns in DeFi security and how do they affect protocols?

Weird token patterns in DeFi security are non-standard ERC20/ERC721 behaviors like fees on transfer or missing return values that can cause protocols to miscount balances and lose user funds if not handled safely.

How do I check ERC20 and ERC721 conformity for smart contract vulnerabilities?

You check ERC20 and ERC721 conformity by running Solidity analysis with Slither and using web3 libraries for on-chain queries to assess contract implementation, on-chain scarcity, and integration safety with external tokens.

Does this smart contract analysis require Slither and web3 libraries?

Yes, analyzing smart contracts for token integration safety requires Slither for static Solidity analysis and web3 libraries for on-chain queries to evaluate token distribution, supply risks, and protocol handling of external tokens.

What is the best way to secure a DeFi protocol integrating multiple external tokens?

The best way to secure a DeFi protocol integrating external tokens is to systematically assess how the protocol handles non-standard behaviors, evaluating contract composition, owner privileges, and on-chain scarcity using established security checklists.

When should I analyze on-chain scarcity and token distribution for DeFi security?

You should analyze on-chain scarcity and token distribution during smart contract audits when evaluating token implementations, as supply risks and non-standard behaviors can impact the safety of protocol integrations.