smart-contract-audit
Skill4 starsChanged 5 months agoMITView on GitHub
Smart contract and Web3 security audit skill for Solidity, Vyper, Move, and Cairo. Covers reentrancy, access control, oracle manipulation, MEV/sandwich exposure, signature replay, upgrade safety, ERC token edge cases, bridge risk, and DeFi invariants. Tooling includes Slither, Mythril, Echidna, Foundry, Halmo, Certora, and custom invariant tests. Use for design review, code audit, and incident analysis on contracts you own or are authorized to assess.
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Treat private keys and seed phrases as untouchable.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Smart Contract Audit
Authorization Boundary
- Audit only protocols and code where you have explicit authorization or a public bounty scope.
- Treat private keys and seed phrases as untouchable; never request, store, or use them.
- Distinguish lab/testnet from mainnet; never simulate exploits against live user funds.
Audit Workflow
- Architecture: contract map, upgrade pattern, proxy admin, roles, external calls, oracles, AMMs, bridges, governance.
- Threat model: trust assumptions, economic invariants, privileged actors, off-chain dependencies, MEV exposure.
- Static and semantic:
slither,aderyn,semgrep,mythril, Solidity compiler warnings; review storage layout for upgradeable contracts. - Property tests: write invariants in Foundry/Echidna/Halmo; fuzz with state-machine harnesses; run differential tests vs reference.
- Manual review: reentrancy (CEI), unchecked external calls, signature replay, frontrunning, slippage, rounding, oracle freshness/TWAP, ERC-20 fee-on-transfer and rebasing edge cases, ERC-721/1155 callbacks.
- Economic: invariant set on liquidity, fees, debt, collateral; simulate MEV (
mev-share,cannon,tenderly). - Report: severity, likelihood, impact, fix, regression test.
High-Risk Patterns Checklist
- Upgrade safety: storage gaps, initializer guards, admin keys, timelocks.
- Bridge messages: replay protection, finality, message origin validation.
- Oracles: single-source, manipulable spot price, missing staleness checks.
- Governance: flash-loan-driven votes, quorum manipulation, proposal hijack.
- Token assumptions: non-standard ERC-20 (USDT-style, rebasing, fee-on-transfer, blocklist).
Output Contract
scope.md,architecture.md,threat-model.md.findings/<id>.md: severity, code refs, PoC, fix, test.invariants/: Foundry/Echidna harnesses.report.pdforreport.md: exec summary, findings, appendices, remediation status matrix.
Other versions8 projects use a version of this.
Word for word · 1
- Garyson26/Trident-SecOps-Skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 7
- Gabson0x/bountyforge★ 431same name
- forefy/.context★ 153same name
- ZhouXiaoHong/binance-skills★ 2same name
- conjure-3301/skills★ 0same name
- CorentinGC/claude-skills★ 0same name
- poorvith-mp/skills-developer★ 0same name
- Viprasol-Tech/smart-contract-audit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- go-programmingSkill
- kubernetes-securitySkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- prompt-enhancementSkill
- python-programmingSkill
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- go-programmingSkill
- kubernetes-securitySkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- osint-recon-automationSkill
- prompt-enhancementSkill
- purple-team-automationSkill
- python-programmingSkill
- soc-operationsSkill
- threat-intel-fusionSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.