skills.rest
naruto11eth
naruto11ethCOMMUNITY
Explore all skills by this author →
Website𝕏@naruto11ethGitHub

mythril

Detect exploitable Solidity vulnerabilities via symbolic execution and multi-transaction analysis.

1|1|Updated May 21, 2026
Search Tags:#reentrancy#evm#smart contract audit#swc#symbolic execution#mythril#solidity security
One-click install
npx skills add https://github.com/naruto11eth/cryptoskills --skill mythril-naruto11eth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mythril
Source: https://github.com/naruto11eth/cryptoskills/tree/main/skills/mythril
Command: npx skills add https://github.com/naruto11eth/cryptoskills --skill mythril-naruto11eth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Static analyzers match code patterns but cannot prove whether a vulnerability is actually exploitable, and LLMs frequently generate incorrect Mythril commands with missing timeouts, wrong solc versions, and shallow analysis depth. This Skill provides accurate, production-ready guidance for running Mythril symbolic execution against Solidity contracts without hanging CI pipelines or missing multi-transaction exploits. ## Core Features & Use Cases - Symbolic Execution Analysis: Run Mythril with correct transaction depth (-t), execution timeouts, solver timeouts, and module selection to find reentrancy, unprotected withdrawals, delegatecall exploits, and integer overflows mapped to SWC identifiers. - CI/CD Integration: GitHub Actions workflows with Docker resource limits, multi-contract scanning, JSON/JSONV2 report generation, and artifact uploads. - Troubleshooting & Error Resolution: Fixes for Z3 build failures, solc version mismatches, import resolution in Foundry/Hardhat projects, OOM errors, and false positive triage. - Use Case: Before a smart contract audit, run a deep -t 3 scan on a vault contract to prove whether a suspected reentrancy bug is exploitable, then compare results against a Slither scan to separate style issues from proven attack paths. ## Quick Start Ask the agent to analyze your Solidity contract with Mythril using Docker, transaction depth 2, a 300-second execution timeout, and JSON output.

Frequently Asked Questions about mythril

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

FAQPage Schema
How do I run Mythril on a Solidity contract?▼

Run myth analyze Contract.sol with an explicit solc version, transaction depth, and execution timeout, for example myth analyze Vault.sol --solv 0.8.28 -t 2 --execution-timeout 300. Docker via the mythril/myth image avoids Z3 installation issues.

Mythril vs Slither: which smart contract analyzer should I use?▼

Slither uses fast static pattern matching and finishes in seconds, catching style issues and known patterns. Mythril uses symbolic execution to prove exploitability with concrete transaction sequences but takes minutes to hours. Use both: Slither on every PR, Mythril before audits.

Why does Mythril fail with a solc compilation error?▼

The installed solc version does not match the contract's pragma, or imports cannot be resolved. Specify the exact version with --solv 0.8.28 and pass include paths via --solc-args such as --base-path . --include-path node_modules or lib for Foundry.

How do I prevent Mythril from running out of memory or hanging?▼

Always set --execution-timeout and --solver-timeout, keep transaction depth at -t 2 for routine scans, and reduce --max-depth or --loop-bound for large contracts. In Docker, add --memory=4g and --cpus=2 to cap resource usage.

Can Mythril analyze deployed contracts on-chain?▼

Yes, use myth analyze --address 0x... --rpc-url with any EVM RPC endpoint to pull and analyze deployed bytecode. On-chain analysis is slower because Mythril resolves storage and external contract dependencies through RPC calls.

Why does Mythril report false positives on Solidity 0.8 contracts?▼

The integer overflow module (SWC-101) rarely applies to Solidity 0.8+ because the compiler inserts overflow checks, and the exceptions module flags defensive assert statements. Exclude them with --exclude-modules integer,exceptions to reduce noise.

Related Skills

Explore More Software Engineering Skills→
0xinit0xinit

slither

Analyzes Solana smart contracts for vulnerabilities, code quality, and gas inefficiencies.

Community
Advanced
Mjlike123Mjlike123

design-improve

Implements prioritized design fixes from audit findings with verification and reporting.

Community
Intermediate
Ramprasad4121Ramprasad4121
1

audit-prep-assistant

Prepare codebases for security review with static analysis and documentation.

Community
Advanced
kaynetikkaynetik
1

web3-testing

Generate Foundry and Hardhat test harnesses for Solidity smart contracts.

Community
Advanced