Modules & Marketplace¶

AEGIS capabilities arrive as installable modules. The core stays small; everything optional is a module.

What a module is¶

A module is a self-contained capability package:

A manifest.json describing what it does, what services it needs, and what tools it exposes
A BaseModule subclass implementing the actual logic
Zero coupling to other modules — all cross-module access flows through the Orchestrator

Modules can be enabled, disabled, or uninstalled without touching anything else in the system.

Built-in modules¶

These ship with AEGIS and load automatically on startup:

Module	What it does
`notes`	A simple scratchpad — store and retrieve notes by tag or keyword
`daily_brief`	Morning summary — weather, calendar, tasks — filed in the vault
`finance_department`	Budget tracking, expense categorization, monthly summaries
`n8n_automation`	Trigger and receive n8n workflows over webhooks
`interview_system`	Guided interview sessions (9 topics, 46 questions) that populate long-term memory

Managing modules¶

From the web app¶

Open the Modules panel (sidebar → Modules icon)
Use the toggle next to any module to enable or disable it
Disabled modules are still installed — they just don't load at startup

From the Modules panel¶

The Modules panel shows: - Status — enabled / disabled / sandboxed (marketplace installs show 🔒) - Description — what the module does - Tools — the slash commands and tool calls the module exposes when enabled

Marketplace¶

The AEGIS Marketplace lets you install community modules from the registry.

Finding modules¶

Open the Marketplace panel (sidebar → Marketplace icon)
Browse by category or search by name
Click a module to see its description, permissions it requests, and user reviews

Installing a module¶

Every marketplace install goes through a consent gate:

Review — plain-language summary of what the module does
Integrity check — SHA-256 hash verified against the registry (tamper = hard block, no bypass)
Code scan — static analysis flags network access, subprocess use, and dynamic code evaluation
Approval — you must explicitly accept before AEGIS downloads or runs anything

If any step fails, the install is cancelled and AEGIS tells you why.

Sandboxed execution¶

Marketplace modules do not run in the same process as AEGIS core. They run in an isolated worker:

Stripped environment (no access to secrets or API keys you haven't explicitly shared)
All service access is permission-gated over a controlled RPC channel
File, network, and subprocess operations are audited
Crash or timeout → worker is killed; AEGIS core keeps running

Built-in modules (the ones that ship with AEGIS and live in modules/) run in-process and are not sandboxed — they are maintained as part of the project.

Uninstalling¶

Marketplace panel → find the installed module → Uninstall
AEGIS verifies provenance (it was installed through the consent gate) before removing

Building your own module¶

Use HEPHAESTUS — the no-code module builder (ADR-0006):

/build

HEPHAESTUS interviews you about what the module should do, then generates the full module scaffold — manifest.json, __init__.py, service wiring, and tests. No coding required.

For a code-first approach, copy templates/module_template/ and fill in the blanks. The template README explains every file.

Publishing to the marketplace¶

Modules are published to the aegis-registry GitHub repo. Once your module is tested locally, open a pull request to the registry. The registry maintainers review the code scan results before merging.

AI skills¶

AEGIS exposes three cognitive-layer skills for building capabilities programmatically:

Skill	What it does
`create_module`	Generates a new module from a description
`create_agent`	Generates a new agent for the multi-agent framework
`create_workflow`	Generates a DAG workflow definition

Access them via the chat interface or by calling POST /tools/{skill_name}.