audit

Audit EVM smart contracts and file GitHub issues for medium-or-higher findings.

7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Zodomo/DrandVerifier --skill audit-zodomo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/Zodomo/DrandVerifier/tree/main/.opencode/skills/ethskills/audit
Command: npx skills add https://github.com/Zodomo/DrandVerifier --skill audit-zodomo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you perform a thorough security review of EVM smart contracts, reducing the chance of missing subtle vulnerabilities before they reach production.

Core Features & Use Cases

  • Deep EVM audit methodology: Runs a systematic recon-to-synthesis workflow using domain checklists.
  • Parallel specialist coverage: Applies targeted checks across many vulnerability domains to improve breadth and depth.
  • Actionable reporting: Produces standardized findings and files GitHub issues for medium severity and above.
  • Use Case: Auditing an unknown third-party contract before integrating it into your protocol so you can identify high-risk flaws and document fixes.

Quick Start

Audit the contract at https://github.com/owner/repo/blob/main/contracts/Foo.sol using the EVM audit methodology and produce an AUDIT-REPORT.md with GitHub issues for findings of medium severity or higher.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I perform a security audit on an unknown EVM smart contract?

A smart contract security audit uncovers vulnerabilities by applying domain checklists across parallel specialist assessments, synthesizing the results, and producing standardized actionable findings to document high-risk flaws before production.

Can I automatically file GitHub issues for smart contract vulnerabilities found during an audit?

Yes, smart contract vulnerability analysis can automatically file GitHub issues by synthesizing parallel specialist assessments and generating standardized issue reports for any vulnerabilities rated medium severity or higher.

Does the checklist methodology work for auditing any third-party EVM contract before integration?

Yes, checklist methodology works for third-party EVM contract audits by fetching relevant domain checklists, running targeted parallel vulnerability assessments, and aggregating the results to identify high-risk flaws before protocol integration.

What is the best way to structure a vulnerability analysis workflow for Solidity contracts?

The best way to structure an EVM vulnerability analysis workflow is a recon-to-synthesis pipeline that selects relevant domain checklists, executes parallel specialist assessments, and outputs an aggregated audit report.

What limitations should I expect when using automated risk assessment for smart contracts?

Automated EVM risk assessment limitations include the necessity of loading a routing module, fetching external domain checklists, and restricting automated GitHub issue filing to medium or higher severity vulnerabilities.