- Home
- Skills
- Web3 & Crypto
- Smart Contract Reentrancy Fuzzer
Works with the AI Agents you already use
Smart Contract Reentrancy Fuzzer
Audit Solidity smart contracts for reentrancy, CEI violations, and integer overflows through static analysis.
Free
Smart Contract Reentrancy Fuzzer
Example session with this skill installed
Audit the Vault.sol contract for reentrancy vulnerabilities and check if the withdraw function follows the CEI pattern.
- Read your context and instructions
- Compiled the smart contract reentrancy
I have completed a static security audit of Vault.sol focusing on reentrancy and Checks-Effects-Interactions (CEI) compliance.
Smart Contract Security Audit: Vault.sol
| Function | Vulnerability | Type | Status | Recommendation |
|---|---|---|---|---|
withdraw(uint256) | Reentrancy | High | CRITICAL | State update happens after call.value(). Move balances[msg.sender] = 0 before the transfer. |
emergencyExit() | Missing Modifier | Medium | WARNING | Function lacks nonReentrant modifier despite interacting with external addresses. |
deposit() | Integer Overflow | Low | SAFE | Uses Solidity 0.8.x built-in overflow checks. |
getBalance() | Read-only Reentrancy | Medium | POTENTIAL | External contracts may rely on this state during a mid-transaction callback. |
Analysis Details
CEI Violation: The withdraw function sends Ether to msg.sender before resetting their balance. An attacker can trigger a fallback function to re-enter the withdraw call and drain the vault.
- Guardrail Check: OpenZeppelin
ReentrancyGuardis imported but not inherited by the main contract.
Next steps
- Update
Vault.solto inherit fromReentrancyGuard. - Refactor the
withdrawfunction to follow the Checks-Effects-Interactions pattern by updating state before the external call. - Apply the
nonReentrantmodifier to all external-facing functions that transfer value.
Connects securely to your tools. The creator never sees your data.
About this skill
Smart contracts with reentrancy bugs lead to catastrophic fund drainage and protocol failure. This skill performs static source code inspection to identify state-altering vulnerabilities before you deploy to mainnet. ## What it does - **State Mutation Analysis** verifies that variables are updated before any external Ether transfers or `call.value()` invocations occur. - **Pattern Validation** checks for the correct implementation of OpenZeppelin `ReentrancyGuard` and the application of `nonReentrant` modifiers. - **Attack Vector Identification** flags potential flash loan exploits and complex read-only reentrancy vulnerabilities. - **CEI Enforcement** audits code against the Checks-Effects-Interactions pattern to prevent mid-execution state manipulation. ## How it works 1. **Source Scanning** parses Solidity (.sol) files within the active project workspace to map out external calls. 2. **Logic Mapping** traces state variable mutations relative to external call triggers. 3. **Vulnerability Assessment** compares findings against known reentrancy and overflow/underflow patterns. 4. **Mitigation Reporting** generates a structured audit report detailing the flaw locations and recommended fixes. ## Frameworks & tools This skill is designed for Solidity development environments using the Ethereum Virtual Machine (EVM) architecture. It specifically supports OpenZeppelin security libraries and standard static analysis patterns. ## Why this beats prompting it yourself Generic prompts often miss the nuances of state mutation order and read-only reentrancy which are hard to detect without a dedicated security workflow. This skill uses a deterministic audit path focused on CEI violations that standard LLM coding assistants frequently overlook. ## Use cases - Auditing new DeFi protocol contracts for external call safety. - Verifying `nonReentrant` modifier coverage across complex inheritance trees. - Detecting integer overflow risks in legacy Solidity versions. - Reviewing cross-contract state dependencies for read-only reentrancy. ## Known limitations Limited to static source code inspection only. It does not perform dynamic analysis, symbolic execution, or live blockchain node interactions.
Static analysis only. No blockchain node interaction or dynamic fuzzing. Restricted to workspace files.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 4 days ago
- Free with an Agensi account
Requires
Permissions
Target Use Cases: - Audit this Solidity contract for reentrancy vulnerabilities. - Check my smart contract for checks-effects-interactions violations. - Review token vault code for flash loan reentrancy.