convez.ai
MCP ServerIntegração & APIsIntermediário
eidos-agi

Eidos Marketplace

eidos-agi/eidos-marketplace

Marketplace auditado de plugins para Claude Code com descoberta inteligente

Ver no GitHub
BomPluginScore · de 0 a 100

Marketplace oficial de plugins para Claude Code mantido pela Eidos AGI, com padrão público de auditoria e recomendação progressiva. Oferece instalação simplificada via /eidos-install, descoberta de plugins relevantes e uma arquitetura em três camadas que falha independentemente para máxima confiabilidade.

Instalação

$npx convez-ai eidos-agi/eidos-marketplace

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
100%
Último commit
há 1 mês
Versão
—
Issues abertas
2
Contribuidores
2

Casos de uso

  • Instalar e gerenciar plugins recomendados para fluxos de trabalho específicos
  • Descobrir ferramentas auditadas para automação, desenvolvimento e produtividade
  • Publicar novos plugins com padrão de qualidade e auditoria pública

Veredito

Solução robusta e bem arquitetada para distribuição de plugins em Claude Code, com padrão de auditoria rigoroso e dogfooding real. Essencial para quem constrói ou descobre ferramentas no ecossistema Eidos.

README

A tradução para o português deste README ainda está na fila.

Eidos Marketplace

The plugin marketplace for Claude Code, by Eidos AGI.

A portfolio of how we ship. Every plugin here is built or vouched for by Eidos AGI, audited against a public standard, and removed if it falls below the bar. Visibility is the moat.

Three layers, one bar. Onboarding via /eidos-install (a progressive-reveal forge that asks what you're doing and recommends a starter set). Discovery via marketplace.json and /forge recommend-for (a forge-specific recommender). Installation via claude plugins install <name> (the normal Claude Code path). Each layer can fail without breaking the others.

The marketplace is its own first customer. Audits run via foss-forge. Releases via ship-forge. Security checks via security-forge. Each is itself a plugin in this marketplace. If our own tools can't run our own operations, they don't belong here. See Dogfooding.

Install

Codex

Add the Eidos AGI marketplace once:

codex plugin marketplace add eidos-agi/eidos-marketplace

Then install plugins from the single public Codex marketplace identity:

codex plugin add eidos@eidos-agi
codex plugin add felix@eidos-agi
codex plugin add foreman@eidos-agi

Codex users should see one Eidos marketplace: Eidos AGI. Bootstrap and catalog helpers are plugins inside that marketplace, not separate stores.

Claude Code

Add the marketplace once:

claude plugins marketplace add eidos-agi/eidos-marketplace

First time? Use the front door.

claude plugins install eidos-install
/eidos-install

/eidos-install interviews you ("what are you doing?"), recommends a coherent starter set drawn from this marketplace and the broader Eidos ecosystem, and shows the install commands. It hands off to /forge recommend-for <project> for ongoing forge-specific drilldown.

Already know what you want? Install directly.

claude plugins install cept            # proprioception for coding agents
claude plugins install resume-resume   # post-crash session recovery
claude plugins install ike             # task and project management
claude plugins install visionlog       # vision, goals, guardrails, ADRs
claude plugins install forge-forge     # forge-specific recommender
claude plugins install felix           # agent ecosystem builder and maintainer
claude plugins install foreman         # scoped coding delegation to worker agents

Every plugin is directly installable. The recommenders (eidos-install, forge-forge) are optional middleware over the flat listing — if either is broken, every plugin remains installable by name.

Publishing from source repos

Source repos remain canonical for code, tests, package releases, skills, and MCP implementation. This marketplace owns the public store surface: plugin bundles, marketplace.json, audit docs, and recommendation metadata.

Publish a source-owned plugin into the marketplace with:

python tools/marketplace_publish.py publish /path/to/source-repo
python tools/marketplace_publish.py check <plugin-name> --source /path/to/source-repo

The publisher copies store-facing files into plugins/<name>/, normalizes local MCP paths to ${CLAUDE_PLUGIN_ROOT}, upserts .claude-plugin/marketplace.json, and creates a pending audit doc when one does not exist. The source-aware check compares generated bundle files back to the source repo, ignoring local cache artifacts such as __pycache__. Run the source repo's own doctor/checks first, then run the marketplace checks before shipping.

What's in here

Tools — discrete capabilities

PluginWhat it doesQuality
ceptProprioception for coding agents — slice recent Claude Code transcript, redact, ask a model for steeringA (2026-04-28, by-hand)
rheaAdversarial sparring partner — challenge, debate, simplify, unstick. Sibling to cept; the outside-perspective mirror to cept's self-perspective(Phase 3c)
emuxEidos mux — pick up where you left off in tmux. TUI session picker for humans (emux) + MCP server for agents (emux mcp). One shared registry of named sessions; works with any tmux session — Claude Code, shells, long-running services(Phase 3d)
resume-resumePost-crash session recovery, dirty repos inventory, session search across history(audit pending)
ikeTask and project management — tasks, milestones, documents, Definition of Done(audit pending)
visionlogVision, goals, guardrails, SOPs, ADRs — the contracts all execution must honor(audit pending)
meeting2actionTurns meeting artifacts from many sources into grounded decisions, tasks, docs, and CRM updates(audit pending)
research-mdEvidence-graded, phase-gated research decisions(audit pending)
railgueyRailway deployment management(audit pending)
clawdflareCloudflare management — DNS, Workers, Pages, KV, R2(audit pending)
eidos-mailEmail for Claude Code — read, search, send, reply, forward(audit pending)

Forges — opinionated workflows

PluginWhat it doesQuality
eidos-installProgressive-reveal interview that recommends a starter set for the Eidos ecosystem; delegates to forge-forge for ongoing forge-specific drilldown(Phase 3)
eidos-storemetheusBuilds governed company plugin stores: scope, manifests, review gates, install proof, and operating cadence(audit pending)
felixAgent ecosystem builder and maintainer — standards, scaffolding, repo health, and plugin doctor checks(audit pending)
foremanDelegation forge — scoped coding work in isolated worker worktrees with collect/finalize flows(audit pending)
forge-forgeForge-specific recommender; reads the marketplace's x-eidos.recommend blocks(Phase 3)
probe-forgeProbing tools(audit pending)

Per-plugin scorecards live in AUDITS/. Audit metadata is also published machine-readably under each plugin's x-eidos.audit block in marketplace.json. Claude Code ignores x-eidos at install time; Eidos tooling reads it for audits, recommendations, and source-to-store checks.

How it works

This marketplace is a directory of pointers, not code. The preferred Eidos pattern is CLI-first progressive reveal: plugins and MCP shims should point agents to local CLIs, while the CLIs expose deeper capability through --help, status, doctor, list, find, ask, and domain subcommands. This avoids loading thousands of tools into every agent context while preserving discoverability.

Plugins ship in two shapes depending on what they distribute:

MCP-server plugins (like cept) — two small JSON files; the actual code lives on PyPI. MCP should stay bounded. When a surface wants to expose many domains or a large tool graph, ship a CLI and use MCP only as a thin pointer or bridge to that CLI.

plugins/cept/
├── .claude-plugin/plugin.json   ← name + description
└── .mcp.json                    ← command to start the MCP server

The .mcp.json tells Claude Code how to run the server:

{
  "cept": {
    "command": "uvx",
    "args": ["--from", "cept", "cept"]
  }
}

uvx pulls the package from PyPI on demand — no pre-install needed.

Skill-bearing plugins (forges) ship either as github-source entries (when the source lives in another repo) or as local entries inside this marketplace repo (when the skill is small enough to live alongside the listings). Either way, the marketplace pulls skills/<name>/SKILL.md directly. No PyPI package required. See STANDARD.md for the source-shape spec.

What "eidos-grade" means

See STANDARD.md for the full bar. The short version:

  • Community Health — LICENSE, README, CHANGELOG, CONTRIBUTING, COC, SECURITY
  • Agentic Quality — every tool typed, described, and built for agents to choose between
  • Engineering — semver, ≤5 dependencies, CI green, OIDC trusted publisher (no long-lived tokens)

Each plugin is also classified as a Tool or Forge, with kind-specific bar additions (e.g., forges must populate x-eidos.recommend; progressive-reveal forges like eidos-install must be interview-driven). See STANDARD.md § Tools and Forges.

Plugins that drop below the bar are pulled. Removal is a stronger signal than silent inclusion.

How to contribute

See CONTRIBUTING.md. Today the marketplace lists only Eidos-maintained plugins; third-party submissions are by issue, not PR.

Roadmap and current state

See PHASES.md — the runnable phased plan. Any agent or human can pick up at the current phase and execute. Each task is tickable; nothing is deleted, only checked off with a one-line note when something was learned.

LEARNINGS.md captures friction encountered along the way.

Requirements

Troubleshooting

Plugin "X" not found in marketplace "eidos-marketplace" — your local marketplace cache is stale. Run:

claude plugins marketplace update eidos-marketplace

claude plugins marketplace add only fetches the marketplace if it isn't already cached; it does not re-fetch when the marketplace.json on GitHub has changed. Every install of a newly-added plugin will fail with "not found" until the cache is refreshed. See LEARNINGS.md § 2026-04-28.

License

MIT — see LICENSE.

Ver o original no GitHub

Bom para

Relacionados