Getting started

  1. Prerequisites
  2. Clone
  3. Run the model PoCs
  4. Run the fork-simulation replays
  5. Run the Ethernaut wargame
  6. Use it as agent skills

Prerequisites

  • Foundry (forge) — the PoC + simulation harness.
  • For fork-simulation: an archive RPC endpoint (to pin historical blocks).
  • Optional: slither, semgrep to accelerate the sweep’s static probes.

Clone 

git clone https://github.com/novaondesk/aegis
cd aegis

Run the model PoCs

The catalog’s runnable proofs (Vulnerable<X> + Safe<X> + exploit test):

cd poc
forge install foundry-rs/forge-std   # once, lib/ is gitignored
forge test -vv

Run one detector’s PoC (each catalog entry’s poc_cmd):

forge test --match-contract InflationAttack -vv

Run the fork-simulation replays

Exploit real deployed contracts on a mainnet fork (see Fork-simulation):

cd sim
cp .env.example .env          # set ETH_RPC_URL to an archive endpoint
set -a; source .env; set +a
forge test -vvv

Run the Ethernaut wargame

Aegis solving the CTF locally (see The wargame):

cd ethernaut
forge test -vv

Use it as agent skills

Aegis ships as two composable Agent Skills:

  • aegis-audit (red team) — recon & scope → catalog sweep → engines → PoC → scored report.
  • aegis-defender (blue team) — turns findings into fixes proven by a Safe<X> PoC + a release-gate.

Register the repo’s skills/ directory in place (so the ../../catalog links resolve), then ask to “audit this contract” or “remediate these findings”. See How it works.