audit_context

Generate audit context reports for MultiversX smart contract codebases.

12|5|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/multiversx/mx-ai-skills --skill audit-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit_context
Source: https://github.com/multiversx/mx-ai-skills/tree/main/antigravity/skills/audit_context
Command: npx skills add https://github.com/multiversx/mx-ai-skills --skill audit-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you quickly understand the structure, roles, assets, and potential risks of a smart contract codebase before starting a detailed security audit.

Core Features & Use Cases

  • Reconnaissance: Identifies core logic, external dependencies, and available documentation.
  • System Mapping: Maps out user roles, token assets, and contract state.
  • Threat Modeling: Provides an initial assessment of potential threats and attacker profiles.
  • Environment Check: Verifies language versions and test suite status.
  • Use Case: Before auditing a new MultiversX smart contract, use this skill to generate a concise report outlining its key components and potential security surface.

Quick Start

Use the audit_context skill to build a report for the current smart contract codebase.

Frequently Asked Questions about audit_context

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

FAQPage Schema
What is smart contract audit context and why do I need it before a security review?

Smart contract audit context identifies core logic, external dependencies, user roles, and token assets to generate an initial threat model, helping you understand system architecture before a detailed security audit.

How do I build a threat model for a MultiversX smart contract codebase?

Generate a threat model for MultiversX by mapping contract state, user roles, and token assets to produce an initial assessment of potential threats and attacker profiles specific to the ecosystem.

Can I use this to map external dependencies and roles in a MultiversX codebase?

Yes, system mapping identifies external dependencies, available documentation, user roles, and token assets within MultiversX smart contracts to clarify the security posture.

What's the best way to start reconnaissance on smart contract security risks?

Start reconnaissance by generating a comprehensive report that verifies language versions, checks test suite status, and identifies core logic to outline the potential security surface.

Does the audit context report check the environment and test suite status?

Yes, the environment check verifies language versions and test suite status, ensuring the smart contract codebase meets required standards before deeper security analysis begins.