Skip to main content
hc
Submit
skillsFirst-partyReview first Safety ✓ Privacy ✓

Ethereum Solidity Security Foundry Skill

Build and harden Ethereum smart contracts with Foundry, invariant testing, and battle-tested OpenZeppelin security patterns.

by JSONbored·added 2026-04-10·
Claude CodeCodexWindsurfGeminiCursorCLI
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:advancedType:generalVerified:draft
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/skills/ethereum-solidity-security-foundry
Source URLs
https://ethereum.org/developers/docs/, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/ethereum-solidity-security-foundry.mdx
Package URL
/downloads/skills/ethereum-solidity-security-foundry.zip
Package SHA256
658d185c8a7a5c7981f9d4c0d5bb046f425a567016a35bbd8c8aaaf83284db5e
Safety notes
Do not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible., Use local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.
Privacy notes
Prompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context., Never paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2026-04-10

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as first-party.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    Package marked verified.

    Done

  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

6 listed

Difficulty

86/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Have accounts and credentials ready first.

0/3 ready
Account & credentials1Install & runtime1General1

Safety & privacy surface

Safety & privacy surface

2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens.

3 areas
  • SafetyExecution & processesDo not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible.
  • SafetyCredentials & tokensUse local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.
  • PrivacyGeneralPrompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context.
  • PrivacyCredentials & tokensNever paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.

Safety notes

  • Do not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible.
  • Use local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.

Privacy notes

  • Prompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context.
  • Never paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.

Prerequisites

  • Solidity project initialized with Foundry
  • Clear protocol/token specification
  • Target chain and deployment constraints

Schema details

Install type
package
Reading time
8 min
Difficulty score
86
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
658d185c8a7a5c7981f9d4c0d5bb046f425a567016a35bbd8c8aaaf83284db5e
Skill and platform metadata
Skill type
general
Skill level
advanced
Verification
draft
Verified at
2026-04-10
Retrieval sources
https://ethereum.org/developers/docs/
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Apply the Ethereum Solidity security Foundry skill to this contract."

# Required output
1) Threat model and asset flow
2) Contract architecture with security controls
3) Test/fuzz/invariant plan
4) Deployment and verification checklist

About this resource

Overview

This skill gives AI agents a security-first operating model for Ethereum smart contracts. It combines pragmatic architecture guidance with strict testing discipline and deployment safeguards.

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Prerequisites

  • Contract requirements and threat boundaries
  • Access controls and upgrade policy decisions
  • Testnet deployment pipeline

What This Skill Delivers

  • Security-centric contract design review
  • Foundry unit, fuzz, and invariant test strategy
  • Common exploit class defenses (reentrancy, auth, oracle, rounding, griefing)
  • Pre-deploy and post-deploy operational checklist

How to Use This Skill

  1. Define assets, actors, and privileged operations.
  2. Build minimal contract surface area with explicit invariants.
  3. Implement and test against adversarial cases.
  4. Run static/dynamic checks before deployment.
  5. Deploy progressively with monitoring and pause controls.

Troubleshooting

Issue: Tests pass but invariants fail under fuzzing
Fix: Revisit state transitions and assumptions around edge-case ordering.

Issue: Access control too broad
Fix: Replace role overreach with least-privilege split roles and delayed admin ops.

Issue: Upgrades create storage breakage
Fix: Add storage layout checks and upgrade simulation in CI before release.

Knowledge Freshness

Treat tooling details as time-sensitive. Re-validate APIs, limits, pricing, auth models, and deployment flags immediately before implementation. If docs conflict with prior memory, follow current official docs and release notes.

Retrieval Sources

Output Contract

  1. Return a concrete plan with implementation order.
  2. Provide production-ready commands/config/code snippets (not placeholders).
  3. Include explicit assumptions and unresolved risks.
  4. Include a verification checklist with pass/fail criteria.

Quality Gates

  • All commands are copy/paste ready.
  • Security-sensitive steps call out secret handling and least privilege.
  • Version-sensitive guidance cites current docs used.
  • Rollback path is included for risky changes.
  • Final output includes quick validation commands/tests.
#ethereum#solidity#foundry#smart-contracts#security

Source citations

Add this badge to your README

Show that Ethereum Solidity Security Foundry Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/ethereum-solidity-security-foundry.svg)](https://heyclau.de/entry/skills/ethereum-solidity-security-foundry)

How it compares

Ethereum Solidity Security Foundry Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Source provenance).

Field
Ethereum Solidity Security Foundry Skill

Build and harden Ethereum smart contracts with Foundry, invariant testing, and battle-tested OpenZeppelin security patterns.

Open dossier
Ethereum Base Smart Contract Security Capability Pack Skill

Expert EVM capability skill for secure contract architecture across Ethereum and Base, including Foundry testing and operational controls.

Open dossier
Base L2 Smart Contract Launchpad Skill

Ship smart contracts on Base with secure deployment, verification, environment management, and production-readiness checklists.

Open dossier
MCP Tool Contract Testing Skill

Validate MCP server tools with contract-style tests to catch schema drift, unsafe behavior, and integration regressions early.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage verified2026-04-10Package verified2026-04-10Package verified2026-04-10Package verified2026-04-10
Source provenanceDiffersSource-backedNo submission linkNo submission linkNo submission link
Submitter————
Install riskReview firstLow riskLow riskLow risk
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand————
Categoryskillsskillsskillsskills
Sourcefirst-partyfirst-partyfirst-partyfirst-party
AuthorJSONboredJSONboredJSONboredJSONbored
Added2026-04-102026-04-102026-04-102026-04-10
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo————
Safety notes✓Do not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible. Use local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.✓Do not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible. Use local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.✓Do not deploy or transact from generated contract code without independent review, tests, and a dry run; smart contract mistakes can be irreversible. Use local forks or testnets before mainnet and keep deployment wallets and RPC credentials least-privileged.✓Use this skill as planning or review guidance; verify generated commands, code, configuration, and infrastructure changes before running them. Apply least-privilege credentials and test in staging or a disposable branch before using it on production systems, CI, deployment, or account-write workflows.
Privacy notes✓Prompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context. Never paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.✓Prompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context. Never paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.✓Prompts and reports can include contract source, audit findings, addresses, deployment config, and transaction context. Never paste private keys, seed phrases, unreleased exploit details, customer wallet data, or privileged RPC credentials into prompts.✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model. Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.
Prerequisites
  • Solidity project initialized with Foundry
  • Clear protocol/token specification
  • Target chain and deployment constraints
  • Solidity codebase and deployment scripts
  • Security requirements and risk tolerance
  • Testnet staging environment
  • Solidity contracts and deployment scripts
  • Base testnet/mainnet environment variables
  • Defined ownership, admin, and upgrade strategy
  • MCP server implementation and tool catalog
  • Staging environment for test execution
  • Known expected outputs per critical tool
Install
curl -L https://heyclau.de/downloads/skills/ethereum-solidity-security-foundry.zip -o ethereum-solidity-security-foundry.zip && unzip -o ethereum-solidity-security-foundry.zip -d ./ethereum-solidity-security-foundry
curl -L https://heyclau.de/downloads/skills/ethereum-base-smart-contract-security-capability-pack.zip -o ethereum-base-smart-contract-security-capability-pack.zip && unzip -o ethereum-base-smart-contract-security-capability-pack.zip -d ./ethereum-base-smart-contract-security-capability-pack
curl -L https://heyclau.de/downloads/skills/base-l2-smart-contract-launchpad.zip -o base-l2-smart-contract-launchpad.zip && unzip -o base-l2-smart-contract-launchpad.zip -d ./base-l2-smart-contract-launchpad
curl -L https://heyclau.de/downloads/skills/mcp-tool-contract-testing.zip -o mcp-tool-contract-testing.zip && unzip -o mcp-tool-contract-testing.zip -d ./mcp-tool-contract-testing
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

guides

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by YB0y
guides

Auto Mode Hard-Deny Policies For Safe Automation

Set autoMode.hard_deny rules to block risky actions in auto mode.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by kiannidev
Microsoft logoguides

Claude Code on Microsoft Foundry Setup

Configure Claude Code on Microsoft Foundry with Azure credentials.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by kiannidev

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.