The Complete Production SOP: How to Deploy and Run Slither Solidity Smart Contract Static Analyzer in Autonomous AI Agents

---
name: "slither-solidity-static-analyzer"
description: "Detect vulnerabilities, reentrancy hazards, and gas optimizations in Solidity code."
metadata:
  author: "Trail of Bits"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "run slither contract audit"
  - "detect reentrancy slither"
  - "check erc20 compliance slither"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: true
  net_access: false
---

# Slither Solidity Smart Contract Static Analyzer SOP

1. Ensure dependencies are compiled using `forge build --build-info` or `npx hardhat compile`.
2. Execute static analysis via `slither . --json slither-report.json`.
3. Filter output for high and medium severity vulnerabilities.
4. Propose code modifications that follow the Checks-Effects-Interactions (CEI) pattern.
5. Verify post-patch resolution by rerunning Slither with zero non-whitelisted findings.

{
  "filter_paths": "node_modules|lib|test",
  "exclude_dependencies": true,
  "detectors_to_exclude": "naming-convention,solc-version",
  "confidence": "medium,high",
  "severity": "low,medium,high"
}

# Execute via Claude Code CLI or Codex Desktop Prompt
claude "run slither contract audit on src/Vault.sol and detect reentrancy slither hazards"

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.24;

import "@openzeppelin/contracts/utils/ReentrancyGuard.sol";

contract Vault is ReentrancyGuard {
    mapping(address => uint256) public balances;

    function withdraw() external nonReentrant {
        uint256 amount = balances[msg.sender];
        require(amount > 0, "Zero balance");

        // CEI Pattern: Update balance before external transfer
        balances[msg.sender] = 0;

        (bool success, ) = msg.sender.call{value: amount}("");
        require(success, "Transfer failed");
    }
}