smart-contract-vulnerabilities

Audit Solidity and EVM smart contracts for exploitable vulnerability patterns.

11|4|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/sayseven7/frameseven --skill smart-contract-vulnerabilities-sayseven7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-contract-vulnerabilities
Source: https://github.com/sayseven7/frameseven/tree/main/internal/mcp/skills/smart-contract-vulnerabilities
Command: npx skills add https://github.com/sayseven7/frameseven --skill smart-contract-vulnerabilities-sayseven7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you audit Solidity and EVM smart contracts for the most common and most damaging vulnerability classes before they reach production or are exploited in the wild.

Core Features & Use Cases

  • Reentrancy analysis: Detect classic, cross-function, cross-contract, and read-only reentrancy in contracts that make external calls.
  • Core exploit patterns: Review logic for integer overflow and underflow, access control mistakes, delegatecall storage collisions, signature replay, randomness manipulation, force-send ETH, create2 abuse, and front-running or MEV exposure.
  • Audit workflow support: Use the decision tree, code patterns, and mitigation guidance to move from high-level triage to concrete fixes and test cases.
  • Use case: A security engineer can apply this Skill during a smart contract review to identify unsafe withdrawal flows, weak authentication, fragile proxy layouts, and oracle-dependent logic that can be manipulated by attackers.

Quick Start

Ask the Skill to audit a Solidity contract or protocol for reentrancy, access control, replay, proxy, and MEV risks, then request prioritized findings and recommended fixes.

Frequently Asked Questions about smart-contract-vulnerabilities

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

FAQPage Schema
How do I audit a Solidity contract for reentrancy and access control vulnerabilities?

To audit Solidity contracts for reentrancy and access control flaws, analyze external call paths for recursive exploitation and verify privilege enforcement. This identifies risky code paths and provides mitigations for secure remediation.

What are common smart contract exploit patterns related to proxy security and delegatecall?

Common smart contract exploit patterns involving proxy security and delegatecall include storage collisions and fragile proxy layouts. Auditing these architectures identifies unsafe patterns and insecure design assumptions before deployment.

How does signature replay and on-chain randomness manipulation affect EVM smart contracts?

Signature replay and on-chain randomness manipulation affect EVM smart contracts by allowing attackers to bypass authorization or predict outcomes. Auditing identifies these insecure assumptions and recommends verification steps for secure remediation.

Can this Skill detect flash-loan-sensitive logic and MEV exposure in smart contracts?

Yes, this Skill detects flash-loan-sensitive logic and MEV exposure by analyzing transaction-ordering attacks and oracle-dependent logic. It identifies scenarios where attackers can manipulate prices or front-run transactions.

What is the best way to find delegatecall storage collisions in proxy architectures?

The best way to find delegatecall storage collisions in proxy architectures is to review storage layouts for mismatched variable ordering. This audit process identifies fragile proxy designs and recommends mitigations.

Are there limitations when auditing token and ETH handling for force-send ETH vulnerabilities?

Limitations when auditing token and ETH handling include detecting force-send ETH vulnerabilities that bypass contract logic via selfdestruct. The audit identifies these edge cases but requires test cases to verify secure remediation.