token-integration-analyzer

Analyzes ERC20 and ERC721 token implementations and integrations for security risks and non-standard patterns.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill token-integration-analyzer-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-integration-analyzer
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/token-integration-analyzer
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill token-integration-analyzer-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Smart contract developers integrating or building tokens face hidden risks from non-standard ERC20/ERC721 behavior, such as missing return values, fee-on-transfer mechanics, and reentrancy hooks, which can silently break protocol accounting or enable exploits. ## Core Features & Use Cases - Weird Token Pattern Detection: Checks for 24 known non-standard token behaviors including missing return values (USDT), fee-on-transfer (STA, PAXG), rebasing, blocklists, and flash minting. - ERC Conformity & Slither Integration: Runs slither-check-erc, human-summary, contract-summary, and slither-prop to verify standard compliance and contract complexity. - On-chain Scarcity Analysis: Queries deployed contracts for holder distribution, supply concentration, exchange listings, and admin configuration. - Use Case: Before launching a vault that accepts USDT, DAI, and UNI, run this analysis to discover that USDT's missing return value is not handled in your transferFrom call, then fix it with SafeERC20 before mainnet deployment. ## Quick Start Analyze my Solidity codebase for token integration security risks, checking ERC20 conformity and weird token patterns for the external tokens my protocol accepts.

Frequently Asked Questions about token-integration-analyzer

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

FAQPage Schema
How do I check if my protocol handles weird ERC20 tokens safely?

Run a systematic check against the 24 known weird token patterns, including missing return values, fee-on-transfer, rebasing, and blocklists. Verify SafeERC20 usage, balance-before-and-after accounting, and return value validation on every external token call.

How to verify ERC20 conformity with Slither?

Use slither-check-erc with the --erc erc20 flag to automatically verify transfer return values, metadata functions, decimals type, and race condition mitigations. Complement it with slither-prop to generate testable properties for Echidna fuzzing.

Does this analysis work for tokens already deployed on-chain?

Yes, if you provide a contract address and RPC endpoint, the analysis queries on-chain data including total supply, holder concentration, exchange distribution, pause status, and upgrade configuration using web3 or ethers.

Why does my token integration fail with USDT transfers?

USDT does not return a boolean from transfer and transferFrom, so standard IERC20 calls silently fail or revert depending on the compiler version. Wrap all external token calls with OpenZeppelin SafeERC20 to handle missing return values.

What are the limitations of automated token security analysis?

Slither detects ERC non-conformity but misses integration logic flaws like fee-on-transfer accounting errors. Manual review of all integration criteria is required, and on-chain analysis is only possible when a deployed address and RPC endpoint are provided.