token-integration-analyzer

Analyze Solidity token implementations for ERC20/ERC721 non-compliance and weird behaviors.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill token-integration-analyzer-ayehiaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-integration-analyzer
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/token-integration-analyzer
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill token-integration-analyzer-ayehiaa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Token integrations often fail in subtle ways when interacting with non-standard or “weird” ERC20/ERC721 implementations, causing incorrect accounting, reverts, or security vulnerabilities.

Core Features & Use Cases

  • Token implementation & integration auditing: Evaluates whether an ERC20/ERC721 behaves per expectations and how your protocol safely handles arbitrary external tokens.
  • Weird-token pattern detection: Checks for 20+ known non-standard token behaviors (e.g., missing return values, fee-on-transfer, approvals/race quirks, hook-based reentrancy).
  • On-chain scarcity & distribution checks (optional): When provided a deployed contract address, assesses supply/holder concentration and related configuration risks.

Quick Start

Ask the assistant to analyze your token implementation or your protocol’s token integration by providing the codebase context (and, if available, the deployed token contract address).

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 ERC20 and ERC721 token integrations for non-standard behaviors?

ERC20/ERC721 token integration auditing applies a deterministic checklist to evaluate smart contract codebases, identifying non-compliance and weird token behaviors like fee-on-transfer or missing return values that risk protocol accounting failures.

What weird token patterns cause smart contract security failures?

Weird token patterns causing security failures include missing return values, fee-on-transfer mechanics, approval race quirks, and hook-based reentrancy. Evaluating these 20+ non-standard behaviors during smart contract review reveals accounting and reentrancy vulnerabilities in arbitrary third-party token integrations.

How do I check ERC20 conformity for third-party protocol integrations?

Checking ERC20 conformity involves applying a checklist-style analysis to your Solidity codebase to verify deposits, transfers, approvals, and callbacks behave safely across arbitrary external tokens. This reveals non-compliance and privilege risks before mainnet deployment.

Can I analyze deployed token contracts for supply and holder distribution risks?

Yes, you can analyze deployed token contracts for supply and holder distribution risks by providing the on-chain contract address. This optional on-chain querying assesses scarcity, holder concentration, and related configuration risks alongside the standard codebase audit.

Does token integration analysis work for Solidity codebases handling arbitrary external tokens?

Yes, token integration analysis works for Solidity codebases handling arbitrary external tokens by applying a deterministic checklist to verify safe behavior of deposits, transfers, approvals, and callbacks against 20+ weird ERC20/ERC721 patterns and owner privilege risks.