entry-point-analyzer

Analyze smart contract codebases to identify state-changing entry points.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/monmacllcapp/skill-forks --skill entry-point-analyzer-monmacllcapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: entry-point-analyzer
Source: https://github.com/monmacllcapp/skill-forks/tree/main/skills/security/plugins/entry-point-analyzer/skills/entry-point-analyzer
Command: npx skills add https://github.com/monmacllcapp/skill-forks --skill entry-point-analyzer-monmacllcapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill systematically identifies all state-changing entry points in smart contract codebases, providing a clear map of the attack surface for security audits.

Core Features & Use Cases

  • State-Changing Function Identification: Detects and categorizes functions that can modify contract state, excluding read-only operations.
  • Access Control Analysis: Classifies functions by access level (Public, Role-Restricted, Contract-Only) and identifies specific restriction patterns.
  • Use Case: When starting a security audit for a new DeFi protocol, use this Skill to quickly identify all functions that can transfer tokens, change critical parameters, or pause the contract, forming the basis of your audit plan.

Quick Start

Analyze the smart contract codebase located in the current directory for state-changing entry points.

Frequently Asked Questions about entry-point-analyzer

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

FAQPage Schema
How do I find state-changing entry points in a Solidity smart contract for security auditing?

To find state-changing entry points in a Solidity smart contract, analyze the codebase to detect externally callable functions that modify state. This process categorizes functions by access level, such as public or role-restricted, while excluding view and pure read-only functions.

Does this entry point analyzer work with CosmWasm and Vyper codebases?

Yes, entry point analysis works with CosmWasm and Vyper codebases, alongside Solana/Rust, Move, and TON. It detects external functions that modify state across these environments, categorizing them by access control patterns to map the attack surface.

What is the best way to map a smart contract attack surface before a DeFi audit?

Mapping a smart contract attack surface involves identifying all externally callable functions that transfer tokens, change parameters, or pause contracts. This creates a structured audit report classifying functions by access level, forming the foundation of your audit plan.

How do I identify privileged operations and access control patterns in smart contracts?

Identifying privileged operations in smart contracts involves categorizing state-changing functions by access level, including public, admin, role-restricted, and contract-only. This analysis detects specific restriction patterns to highlight externally callable privileged functions.

Why are view and pure functions excluded from smart contract entry point analysis?

View and pure functions are excluded from smart contract entry point analysis because they are read-only operations that do not modify contract state. Security auditing focuses on state-changing entry points to accurately map the attack surface.