# Eidos Storemetheus

Reviewed: 2026-05-31
Canonical repo: https://github.com/eidos-agi/eidos-storemetheus

Storemetheus is an agent-readable operating guide for building governed plugin stores for people, teams, and companies.

A store is not just a list of plugins. It is a distribution system with ownership, install policy, approval paths, evidence, stale-content cleanup, and a store-local creator agent.

## Build contract
- Name the owner and the audience before writing code.
- Decide private, team, or public distribution up front.
- Separate source repo, marketplace catalog, installed cache, runtime config, and active session proof.
- Ship one store-local creator plugin so users do not have to know Felix by name.
- Publish an agent-readable quickstart and a human-readable landing page.
- Add a stale-content review cadence for platform docs and installation paths.

## Claude Code
Fit: Native plugin marketplaces are the strongest current store primitive.
Distribution: Marketplace JSON, plugins, skills, agents, hooks, MCP servers, and install/update commands.
Storemetheus move: Make the company store a GitHub-hosted marketplace first, then publish only curated plugins.
Sources: https://code.claude.com/docs/en/plugin-marketplaces, https://code.claude.com/docs/en/discover-plugins

## Codex
Fit: Best current fit is a governed local/plugin workspace with explicit evidence across source, cache, config, and active session.
Distribution: Skills, plugins, MCP servers, AGENTS.md, local app automations, and repo-backed install notes.
Storemetheus move: Treat Codex as the proving surface for company-specific operating skills and recurring checks.
Sources: https://developers.openai.com/codex/cli, https://developers.openai.com/learn/docs-mcp

## Cursor
Fit: Rules and MCP make Cursor a strong consumer of store-managed context and tools.
Distribution: .cursor/rules, AGENTS.md, MCP configuration, and project-scoped guidance.
Storemetheus move: Publish compact project rules plus MCP recipes, then keep them tied to the same store source.
Sources: https://cursor.com/docs/rules, https://cursor.com/docs/mcp

## Devin
Fit: Knowledge and Playbooks are the store-shaped assets.
Distribution: Organization knowledge, enterprise knowledge, repo-pinned knowledge, playbooks, automations, and scheduled sessions.
Storemetheus move: Convert repeated company workflows into small knowledge items and reusable playbooks.
Sources: https://docs.devin.ai/product-guides/knowledge, https://docs.devin.ai/product-guides/creating-playbooks

## Antigravity
Fit: Agent-manager and artifact-review surfaces make it a good target for verifiable store workflows.
Distribution: Rules, workflows, skills, subagents, and task artifacts.
Storemetheus move: Ship store content as agent-readable workflows and require artifact proof after execution.
Sources: https://antigravity.google/docs/ide-overview?app=antigravity

## Validation surfaces
- source
- marketplace
- cache
- config
- active-session

## Store-local creator pattern
Every serious store should include its own creator plugin. Greenmark should expose Greenmark Plugin Creator. Eidos should expose Eidos Plugin Creator. Felix can remain the implementation engine, but the user-facing creator belongs to the store.

## Guides
- Company store operating guide: /docs/company-store-operating-guide.md
- Greenmark private store case study: /docs/case-studies/greenmark-private-plugin-store.md
- Greenmark private store blueprint: /stores/greenmark.md