ton-vulnerability-scanner
About
This skill scans TON smart contracts written in FunC for three critical security vulnerabilities: integer-as-boolean misuse, fake Jetton contracts, and unprotected TON forwarding. Use it during smart contract audits to automatically detect these common flaws. It's designed for developers building or reviewing secure contracts on The Open Network.
Quick Install
Claude Code
Recommendednpx skills add plurigrid/asi -a claude-code/plugin add https://github.com/plurigrid/asigit clone https://github.com/plurigrid/asi.git ~/.claude/skills/ton-vulnerability-scannerCopy and paste this command in Claude Code to install this skill
GitHub Repository
Related Skills
code-maturity-assessor
OtherThis skill systematically assesses smart contract code maturity using Trail of Bits' 9-category security framework. It analyzes critical areas like arithmetic safety, access controls, and MEV risks to generate an evidence-based scorecard. Use it to get actionable security recommendations and a professional maturity assessment for your codebase.
secure-workflow-guide
OtherThis skill guides developers through Trail of Bits' 5-step security workflow for smart contracts. It automates Slither analysis, checks for specific features like upgradeability, and generates security diagrams. Use it to systematically document security properties and review critical areas in your Solidity project.
substrate-vulnerability-scanner
OtherThis skill scans Substrate/Polkadot blockchain pallets for seven critical security vulnerabilities like arithmetic overflows and bad origin checks. Use it when auditing Substrate runtimes or FRAME pallets to automatically detect common security issues. It's ideal for developers building or reviewing secure smart contracts on Polkadot.
audit-prep-assistant
OtherThis skill helps developers prepare smart contracts for security audits by automating Trail of Bits' checklist. It runs static analysis, improves test coverage, removes dead code, and generates documentation like flowcharts and user stories. Use it to systematically harden your codebase before a formal review.
