Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Automated smart contract bug bounty hunting. Scans Immunefi/Code4rena targets with Slither static analysis, triages findings with local LLMs, and generates P...
Automated smart contract bug bounty hunting. Scans Immunefi/Code4rena targets with Slither static analysis, triages findings with local LLMs, and generates P...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Automated smart contract vulnerability scanner for bug bounty programs. Uses free tools (Slither + local LLMs) for the heavy lifting, saves expensive models for PoC writing.
slither-analyzer (pip): Static analysis solc-select (pip): Solidity compiler management Node.js: For script execution Optional: Ollama with any code model for local triage
# Scan a repo bash scripts/scan.sh <github-repo-url> [src-dir] # Triage findings (uses local LLM if available, otherwise prints raw) bash scripts/triage.sh <scan-output.json> # Generate PoC template for a finding bash scripts/poc-template.sh <finding-id> <contract-address>
Target Selection β Check Immunefi/Code4rena for active programs Clone & Scan β scan.sh clones the repo, installs solc, runs Slither Triage β triage.sh filters HIGH/MEDIUM findings, removes known false positives Deep Dive β Only read code that Slither flagged (save your tokens) PoC β Use poc-template.sh to generate Foundry test scaffolding Submit β Write up finding on Immunefi/Code4rena
Before scanning, check: Scope last updated within 30 days (fresh code = more bugs) Past payouts > $50K (they actually pay) GitHub repo in scope (not just deployed addresses) Solidity-based (Slither only works with Solidity)
Don't read entire codebases manually β let Slither scan first Don't spend > 1 hour on a target without a concrete lead Don't submit known issues (check past reports first) Don't ignore test coverage β untested code is where bugs hide
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.