Skip to content

Add @aegis-defi/plugin-elizaos#315

Closed
StanleytheGoat wants to merge 1 commit intoelizaos-plugins:mainfrom
StanleytheGoat:add-aegis-defi-plugin
Closed

Add @aegis-defi/plugin-elizaos#315
StanleytheGoat wants to merge 1 commit intoelizaos-plugins:mainfrom
StanleytheGoat:add-aegis-defi-plugin

Conversation

@StanleytheGoat
Copy link

@StanleytheGoat StanleytheGoat commented Mar 20, 2026

Plugin Submission

Adding @aegis-defi/plugin-elizaos to the registry.

Repository: https://github.com/StanleytheGoat/aegis
Package: @aegis-defi/plugin-elizaos

What it does

DeFi safety plugin for ElizaOS agents. Scans smart contracts against 165 exploit patterns (honeypots, rug pulls, reentrancy, oracle manipulation), simulates transactions on forked chains, and returns go/no-go decisions before agents trade.

On-chain enforcement via AegisGateway and Uniswap v4 hook on Base mainnet.

Actions

Action Purpose
AEGIS_ASSESS_RISK Full risk assessment combining scan + simulation + token check
AEGIS_SCAN_CONTRACT Static analysis against 165 vulnerability patterns
AEGIS_CHECK_TOKEN Anti-honeypot detection (sellability, hidden fees)
AEGIS_SEARCH_AUDIT_FINDINGS Search 50K+ real audit findings from Solodit

Checklist

  • NPM package name on left side of entry
  • Uses github: not github.com
  • No .git extension
  • Alphabetically sorted
  • Valid JSON
  • Public GitHub repository
  • elizaos-plugins topic added to repo
  • README with installation and usage docs
  • Standard plugin structure (src/, actions/, providers/)

Summary by CodeRabbit

  • Chores
    • Updated package registry to register a new plugin.
    • Improved file formatting consistency.

Greptile Summary

This PR adds a single registry entry for @aegis-defi/plugin-elizaos, a DeFi safety plugin that scans smart contracts for exploit patterns, simulates transactions on forked chains, and integrates with on-chain enforcement via AegisGateway on Base mainnet. It also incidentally fixes a missing newline at the end of index.json.

  • ✅ Entry format is correct — uses github: prefix, no .git extension, valid JSON
  • ✅ Alphabetically sorted correctly between @1BDO/plugin-delta and @andysalvo/plugin-x402-trust
  • ✅ EOF newline added as a side effect
  • ⚠️ The npm scope @aegis-defi differs from the GitHub repository owner StanleytheGoat — worth confirming that the npm package is published and the submitter controls the @aegis-defi scope to prevent scope-squatting risks

Confidence Score: 4/5

  • Safe to merge pending confirmation that the npm package is published and the submitter controls the @aegis-defi scope.
  • The change is a single well-formed JSON entry that is correctly formatted, alphabetically ordered, and follows all stated registry conventions. The only notable point is the mismatch between the npm scope (@aegis-defi) and the GitHub owner (StanleytheGoat), which is an accepted pattern in this registry but warrants a quick verification to ensure npm package availability and scope ownership.
  • No files require special attention beyond confirming the npm package details noted above.

Important Files Changed

Filename Overview
index.json Adds @aegis-defi/plugin-elizaos mapped to github:StanleytheGoat/aegis. Entry format, alphabetical ordering, and JSON validity are all correct. Also incidentally fixes a missing newline at EOF. The npm scope (@aegis-defi) differs from the GitHub owner (StanleytheGoat), which is acceptable but worth verifying that the published npm package matches the declared scope.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[ElizaOS Agent] --> B{Action Request}
    B --> C[AEGIS_ASSESS_RISK]
    B --> D[AEGIS_SCAN_CONTRACT]
    B --> E[AEGIS_CHECK_TOKEN]
    B --> F[AEGIS_SEARCH_AUDIT_FINDINGS]

    C --> G[Static Contract Scan\n165 vulnerability patterns]
    C --> H[Transaction Simulation\non forked chain]
    C --> I[Token Anti-honeypot Check]

    D --> G
    E --> I
    F --> J[Search 50K+ Solodit\naudit findings]

    G --> K{Risk Decision}
    H --> K
    I --> K
    J --> K

    K -->|Go| L[AegisGateway On-chain\nEnforcement on Base]
    K -->|No-Go| M[Block Transaction]

    L --> N[Uniswap v4 Hook\nBase Mainnet]
Loading

Last reviewed commit: "add @aegis-defi/plug..."

Greptile also left 1 inline comment on this PR.

(2/5) Greptile learns from your feedback when you react with thumbs up/down!

DeFi safety plugin for ElizaOS agents. Scans contracts against 165
exploit patterns, detects honeypot tokens, and simulates transactions
before execution. On-chain enforcement on Base mainnet.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 20, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0acf4112-b2df-47f9-834c-3f5a90326cd0

📥 Commits

Reviewing files that changed from the base of the PR and between ce554dd and ccdf81e.

📒 Files selected for processing (1)
  • index.json

Walkthrough

A new package entry @aegis-defi/plugin-elizaos was added to the manifest file, mapping it to the GitHub repository github:StanleytheGoat/aegis. The file was also corrected to properly end with a newline.

Changes

Cohort / File(s) Summary
Manifest Configuration
index.json
Added mapping for @aegis-defi/plugin-elizaos package and fixed file formatting to include proper line terminator.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A new package hops into place,
Listed with grace in the index space,
A simple entry, clean and neat,
The manifest is now complete! 📦✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title directly and concisely summarizes the main change: adding a new package entry for @aegis-defi/plugin-elizaos to the registry.
Description check ✅ Passed The description comprehensively covers the plugin's purpose, functionality, and actions, and includes a checklist confirming compliance with all registry requirements.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

You can customize the high-level summary generated by CodeRabbit.

Configure the reviews.high_level_summary_instructions setting to provide custom instructions for generating the high-level summary.

@@ -1,5 +1,6 @@
{
"@1BDO/plugin-delta": "github:1BDO/plugin-delta",
"@aegis-defi/plugin-elizaos": "github:StanleytheGoat/aegis",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 NPM scope vs. GitHub owner mismatch

The npm package scope @aegis-defi does not match the GitHub repository owner StanleytheGoat. While this is technically allowed, it raises a question about whether the published npm package (@aegis-defi/plugin-elizaos) is actually owned/controlled by the same person as the GitHub repo.

Please confirm:

  1. The npm package @aegis-defi/plugin-elizaos is published and publicly available on npmjs.com.
  2. You control the @aegis-defi npm organisation/scope (to prevent a potential package hijacking scenario where someone else publishes a malicious package under that scope).

Other entries in this registry (e.g. "@coinrailz/plugin-coinrailz": "github:tdnupe3/coinrailz-eliza-plugin") follow the same pattern, so this is not a blocker — but it is worth verifying.

@StanleytheGoat StanleytheGoat closed this by deleting the head repository Mar 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant