AI SummaryDeployGuard is a Python CLI tool that audits Foundry deployment scripts for security vulnerabilities and best practices, helping developers catch CPIMP vulnerabilities and ensure proper test coverage before deployment. It's designed for Cursor users who want automated security checks integrated into their development workflow.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "deployguard — Cursor Rules" prompt rules to my project. Repository: https://github.com/0xstormblessed/deployguard Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
CLI tool for checking deployment scripts against a set of best practices
Testing Requirements
• ALL code MUST have comprehensive test coverage (target >90%) • Tests live in tests/ and follow test_*.py naming • Use pytest fixtures from tests/fixtures/ • Tests MUST include: happy path, edge cases, error conditions • Run tests with pytest (coverage is automatic via pyproject.toml) • Property-based testing with hypothesis for complex parsing logic
About This Project
DeployGuard is a Python CLI tool that audits Foundry deployment scripts for security vulnerabilities, best practice violations, and missing test coverage. It focuses on detecting CPIMP (Clandestine Proxy In the Middle of Proxy) vulnerabilities, security anti-patterns, and ensuring deployment scripts have proper test coverage. It parses Foundry deployment scripts (*.s.sol), performs static and dynamic analysis, and outputs actionable findings with recommendations. Key technologies: Python 3.10+, pytest, py-solc-x, click, rich, web3.py
Git Commit Policy
CRITICAL: NEVER commit or push changes without explicit user approval. • DO NOT create commits automatically • DO NOT push to remote repositories • DO NOT include Co-Authored-By or attribution in commit messages • ONLY stage files when explicitly requested • When user asks to commit, show the proposed commit message and wait for approval • User will create their own commit messages and commits • Do not add comments that are only relevant in the current conversational context • Never credit yourself in commit messages or PR bodies • Do not include time estimates for your work
Workflow
• Make code changes as requested • Stage files ONLY when user asks • User will handle all git commits and pushes themselves ---
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts