Agent skill

Foundry Deploy Fixtures

by aviggiano in aviggiano/security

Create or refactor Foundry deployment fixtures for Solidity tests.

MITAuto-check passedBackend & APIs

Install Foundry Deploy Fixtures

skills CLI
$ npx skills add aviggiano/security --skill foundry-deploy-fixtures -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aviggiano/security foundry-deploy-fixtures --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aviggiano/security.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/foundry-deploy-fixtures .claude/skills/foundry-deploy-fixtures && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
foundry-deploy-fixtures
GitHub stars
144
Token cost
~634 tokens
SKILL.md length
250 words
Files
2
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Create or refactor Foundry deployment fixtures for Solidity tests.

  • Works in 7 steps: Read AGENTS.md, Foundry config, existing… → Identify the minimum deployment graph… → Create or refactor an abstract… → …
  • Codex needs to separate Deploy.t.sol
  • SKILL.md covers Goal, Workflow, Fixture Shape and Bounds And Actors, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Foundry Deploy Fixtures is an agent skill from aviggiano/security. Create or refactor Foundry deployment fixtures for Solidity tests. Use when Codex needs to separate Deploy.t.sol, BaseTest.t.sol, BaseFuzzTest.t.sol, deployment scripts, shared actors, token funding, approvals, and reusable fuzz bounds before adding unit, fuzz, property, or differential tests.

Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Backend & APIs, covering Deployment, Smart contracts and Refactoring. It works with Solidity. The repository describes itself as: Security Reviews and Audit Checklists. The licence is MIT.

When your agent uses it

  • Codex needs to separate Deploy.t.sol
  • BaseFuzzTest.t.sol
  • Deployment scripts
  • Reusable fuzz bounds before adding unit

Example prompts

  • “/foundry-deploy-fixtures”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Read AGENTS.md, Foundry config, existing tests, and deployment scripts.
  2. Identify the minimum deployment graph needed by tests.
  3. Create or refactor an abstract Deploy.t.sol that owns deployment only.
  4. Keep Deploy.t.sol free of Test inheritance unless the repository already requires it.
  5. Create or refactor BaseTest.t.sol so it extends Test and Deploy, calls deployment in setUp, and owns actors, funding, approvals…
  6. Create or refactor BaseFuzzTest.t.sol so it extends BaseTest and owns bounds/generators.
  7. Run focused tests, then the relevant suite.

What it can do on your machine

Read from SKILL.md and the folder at commit e18ce7d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are solidity).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Foundry Deploy Fixtures loads about 634 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 250 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~634

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aviggiano/security at commit e18ce7d, republished under its MIT licence (© aviggiano). 250 words, ~634 tokens.

Download SKILL.mdSave it as .claude/skills/foundry-deploy-fixtures/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
foundry-deploy-fixtures
description
Create or refactor Foundry deployment fixtures for Solidity tests. Use when Codex needs to separate Deploy.t.sol, BaseTest.t.sol, BaseFuzzTest.t.sol, deployment scripts, shared actors, token funding, approvals, and reusable fuzz bounds before adding unit, fuzz, property, or differential tests.

Foundry Deploy Fixtures

Goal

Create a fixture stack where deployment, shared test setup, and fuzz input shaping are separate. This keeps later fuzz and differential tests small and makes deployment switches possible.

Workflow

  1. Read AGENTS.md, Foundry config, existing tests, and deployment scripts.
  2. Identify the minimum deployment graph needed by tests.
  3. Create or refactor an abstract Deploy.t.sol that owns deployment only.
  4. Keep Deploy.t.sol free of Test inheritance unless the repository already requires it.
  5. Create or refactor BaseTest.t.sol so it extends Test and Deploy, calls deployment in setUp, and owns actors, funding, approvals, registration, deposits, snapshots, and common assertions.
  6. Create or refactor BaseFuzzTest.t.sol so it extends BaseTest and owns bounds/generators.
  7. Run focused tests, then the relevant suite.

Fixture Shape

Prefer this dependency direction:

solidity
abstract contract Deploy {
    function deploy() internal virtual { ... }
}

abstract contract BaseTest is Test, Deploy {
    function setUp() public virtual {
        deploy();
        // fund, approve, register, deposit
    }
}

abstract contract BaseFuzzTest is BaseTest {
    function _boundAmount(uint256 seed) internal pure returns (uint256) { ... }
}

If the project has scripts such as DeployToken.s.sol, instantiate and reuse them instead of duplicating deployment logic in tests. If a reference deployment is needed later, add a small switch such as an env var or overrideable deployReference() rather than branching inside every test.

Bounds And Actors

Use named actors and realistic balances. Include different token decimals when decimals affect math. Bounds should encode semantic validity, such as minimum order size, available balance, max price, slippage constraints, and partial-fill ranges.

Guardrails

  • Do not mix deployment-only logic with fuzz assumptions.
  • Do not hide invalid input by over-bounding; preserve meaningful edge cases.
  • Keep assertion reasons as asserted predicates when the repo requires it.
  • Preserve unrelated user changes and avoid contract changes unless explicitly requested.

© aviggiano, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/foundry-deploy-fixtures of aviggiano/security.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit e18ce7d

Compare with similar skills

Foundry Deploy Fixtures next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Foundry Deploy Fixtures compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Foundry Deploy Fixtures this skillaviggiano/security144—~634Automated safety check: PassMIT
New Configlidofinance/diffyscan142—~1kAutomated safety check: PassMIT
Validate Configlidofinance/diffyscan142—~1.1kAutomated safety check: PassMIT
function Object() { [native code] } Patternsccashwell/evm-cortex131—~1.7kAutomated safety check: PassMIT
Test Fixturesccashwell/evm-cortex131—~1.9kAutomated safety check: PassMIT
Cross Chain Securityccashwell/evm-cortex131—~1.7kAutomated safety check: PassMIT

Similar skills

  • New Config

    lidofinance/diffyscan

    Creates or extends a Diffyscan verification config for a deployed contract or deployment.

    142 GitHub stars~1k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • Validate Config

    lidofinance/diffyscan

    Reviews an existing Diffyscan YAML or JSON config for load errors, runtime prerequisites, pinned sources, address mappings and broad exceptions.

    142 GitHub stars~1.1k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • Test Fixtures

    ccashwell/evm-cortex

    A skill your agent uses when setting up test environments for Solidity protocols.

    131 GitHub stars~1.9k tokensUpdated 11 days ago
    Backend & APIsAuto-check passed
  • Cross Chain Security

    ccashwell/evm-cortex

    Cross-chain security patterns for multi-chain Solidity deployments and bridge interactions.

    131 GitHub stars~1.7k tokensUpdated 11 days ago
    Backend & APIsAuto-check passed
  • Library Patterns

    ccashwell/evm-cortex

    Library design patterns for reusable Solidity code. An agent skill from ccashwell/evm-cortex.

    131 GitHub stars~1.6k tokensUpdated 11 days ago
    DevelopmentAuto-check passed

More from aviggiano/security

All 10 skills in this repo
  • Foundry Fuzz Mirrors

    aviggiano/security

    Create Foundry fuzz tests from deterministic unit tests. An agent skill from aviggiano/security.

    144 GitHub stars~584 tokensUpdated 25 days ago
    Auto-check passed
  • Foundry Spec Properties

    aviggiano/security

    Turn whitepapers, protocol specs, and public documentation into Foundry property tests.

    144 GitHub stars~489 tokensUpdated 25 days ago
    Auto-check passed
  • Foundry Test Campaign

    aviggiano/security

    Master skill for running an end-to-end multi-pass Foundry testing campaign for Solidity projects.

    144 GitHub stars~1.6k tokensUpdated 25 days ago
    Auto-check passed
  • Stateful Invariant Testing

    aviggiano/security

    Build metric-driven Chimera/create-chimera-app stateful invariant testing campaigns for Solidity projects.

    144 GitHub stars~2.8k tokensUpdated 25 days ago
    Auto-check passed
  • Foundry Differential Tests

    aviggiano/security

    Create Foundry differential tests comparing production Solidity contracts against an independent reference model.

    144 GitHub stars~613 tokensUpdated 25 days ago
    Auto-check passed
  • Foundry Failure Triage

    aviggiano/security

    Classify failing Foundry fuzz, property, invariant, and differential tests.

    144 GitHub stars~637 tokensUpdated 25 days ago
    Auto-check passed

Works with

Questions about Foundry Deploy Fixtures

What does Foundry Deploy Fixtures do?

Create or refactor Foundry deployment fixtures for Solidity tests. Foundry Deploy Fixtures is an agent skill from aviggiano/security. Create or refactor Foundry deployment fixtures for Solidity tests.

When should I use Foundry Deploy Fixtures?

Foundry Deploy Fixtures fits situations like: Codex needs to separate Deploy.t.sol; baseFuzzTest.t.sol; deployment scripts; reusable fuzz bounds before adding unit.

How do I install Foundry Deploy Fixtures in Claude Code?

Run `npx skills add aviggiano/security --skill foundry-deploy-fixtures -a claude-code`. Or copy the skill folder (skills/foundry-deploy-fixtures in aviggiano/security) into .claude/skills/foundry-deploy-fixtures in your project. Claude Code loads it when a task matches its description.

How do I install Foundry Deploy Fixtures in Codex?

Run `npx skills add aviggiano/security --skill foundry-deploy-fixtures -a codex`. Or copy the skill folder (skills/foundry-deploy-fixtures in aviggiano/security) into .agents/skills/foundry-deploy-fixtures in your project. Codex loads it when a task matches its description.

Can I use Foundry Deploy Fixtures in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aviggiano/security --skill foundry-deploy-fixtures -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/foundry-deploy-fixtures, .gemini/skills/foundry-deploy-fixtures, .github/skills/foundry-deploy-fixtures and .opencode/skills/foundry-deploy-fixtures in your project.

What does Foundry Deploy Fixtures need to run?

SKILL.md names no scripts, command-line tools or credentials: Foundry Deploy Fixtures is instructions for the agent only.

Does Foundry Deploy Fixtures access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Foundry Deploy Fixtures safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Foundry Deploy Fixtures use?

Foundry Deploy Fixtures is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Foundry Deploy Fixtures use?

About 634 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Foundry Deploy Fixtures?

Skills that share tags, products or a category with Foundry Deploy Fixtures: New Config (lidofinance/diffyscan, 142 stars), Validate Config (lidofinance/diffyscan, 142 stars), function Object() { [native code] } Patterns (ccashwell/evm-cortex, 131 stars) and Test Fixtures (ccashwell/evm-cortex, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Foundry Deploy Fixtures?

aviggiano (a GitHub user) maintains it in aviggiano/security, which has 144 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 15, 2026.

Source: aviggiano/security on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.