develop-secure-contracts

Integrate OpenZeppelin libraries into Solidity smart contracts.

Updated Aug 23, 2026

Search Tags:#security #solidity #smart-contracts #pattern-discovery #openzeppelin #library-integration #mcp-generators

Ready to run

npx skills add https://github.com/phpmac/foundry --skill develop-secure-contracts-phpmac

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: develop-secure-contracts
Source: https://github.com/phpmac/foundry/tree/main/.agents/skills/develop-secure-contracts
Command: npx skills add https://github.com/phpmac/foundry --skill develop-secure-contracts-phpmac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides secure integration of OpenZeppelin library components into smart contracts, reducing bespoke security gaps by reusing battle-tested patterns and libraries.

Core Features & Use Cases

Library-first integration: discover, import, and compose OpenZeppelin components (e.g., Ownable, AccessControl, Pausable, Governor) instead of implementing security primitives from scratch.
Pattern discovery workflow: analyze project imports to identify required components and apply minimal, upgrade-safe integration changes.
MCP generators and tooling: leverage MCP-based baselines and diff-apply workflows to accelerate compliant integrations across supported ecosystems.

Quick Start

Start by auditing your project for OpenZeppelin imports and enable library-first integration in your workflow.

Frequently Asked Questions about develop-secure-contracts

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

FAQPage Schema

How do I integrate OpenZeppelin libraries into existing Solidity smart contracts?▼

Integrate OpenZeppelin libraries by auditing project imports, discovering required security components, and applying minimal, upgrade-safe diff changes to existing Solidity smart contracts. This preserves existing code while correctly wiring security components.

What is the best way to add access control patterns like Ownable to a smart contract?▼

The best way to add access control patterns is using a library-first integration approach that imports and composes battle-tested OpenZeppelin components like Ownable or AccessControl, rather than writing custom security primitives from scratch.

Can I use OpenZeppelin components with smart contracts outside of Solidity?▼

Yes, OpenZeppelin library integration applies across Solidity and other supported ecosystems. The pattern discovery and MCP generation workflows guide secure component composition across multiple smart contract platforms.

How does the minimal-diff approach work when wiring security components into smart contracts?▼

The minimal-diff approach preserves existing smart contract code by applying only necessary changes to wire OpenZeppelin security components correctly. It leverages MCP-based diff-apply workflows to ensure compliant, upgrade-safe integration.

Why should I use OpenZeppelin libraries instead of implementing my own smart contract security?▼

You should use OpenZeppelin libraries to reduce bespoke security gaps by reusing battle-tested patterns and libraries. Implementing security primitives from scratch introduces vulnerabilities that standardized, audited library components already solve.

Do I need to manually manage dependencies when adding OpenZeppelin security patterns?▼

No, the integration workflow handles dependency management automatically while applying minimal diffs. MCP generators and tooling leverage baseline workflows to ensure compliant OpenZeppelin library integration without manual dependency tracking overhead.