Felix

What it does

Felix is the maintainer for agent ecosystems. It helps turn a vague agent idea into something with a boundary, a command surface, a knowledge home, task ownership, tests, install shape, and proof that it is useful.

It also owns the plugin productization workflow for Eidos: inspect a Codex or Claude Code plugin, check whether its manifest and MCP runtime agree, and draft the distribution path into the Eidos Marketplace.

Install

For Claude Code, install Felix from the Eidos Marketplace:

claude plugins marketplace add eidos-agi/eidos-marketplace
claude plugins install felix@eidos-marketplace

For source work, use the public repo:

git clone https://github.com/eidos-agi/felix.git
cd felix
python -m pip install -e ".[dev]"
felix --help

Core commands

felix doctor
felix check
felix agents list
felix plugin doctor /path/to/plugin
felix plugin plan /path/to/plugin
felix interview sage --purpose "Sage Intacct maintenance CLI"
felix scaffold surfari --write

Where it fits

• Before an agent exists: Felix interviews for role boundary, source-of-truth placement, run mode, and proof.
• While an agent is being built: Felix scaffolds the CLI, docs, task surface, tests, and AGENTS.md wakeup file.
• After an agent ships: Felix checks drift, broken installs, missing tests, stale docs, and plugin readiness.
• When a plugin is ready: Felix plans the marketplace entry and names the website path, while the marketplace keeps the publishing standard.

Boundaries

Felix does not become the operating system, secrets vault, communicator, browser runner, or adversarial reviewer. It is the setup and maintenance layer: the thing that keeps agent families legible, inspectable, and repairable.

See also the Eidos Plugin Store and Eidos Marketplace.