Name the owner and the audience before writing code.
Reviewed 2026-05-31
Build the store before the agents scatter.
A practical operating guide for companies that want AI work to spread through teams without losing ownership, install policy, approvals, and proof.
Store Discovery, trust, and installation.
Creator A store-local agent, not a generic brand.
Evidence Proof across every runtime surface.
Why this matters
Plugins are becoming the company distribution layer for AI.
Teams are already building instructions, skills, tools, MCP servers, playbooks, prompts, approval loops, and automations. Without a store, those assets become private folklore.
Storemetheus turns that into a governed surface: who owns it, who can install it, what it exposes, how it updates, how it is tested, and where an agent should look first.
Current website status
Use the live Railway URL until branded DNS resolves.
The intended branded host remains https://storemetheus.eidosagi.com/. Until DNS is applied in the Cloudflare account that owns eidosagi.com, Storemetheus uses the verified Railway hostname for working links and agent contracts.
Current live root: https://storemetheus-production.up.railway.app/
Build contract
The store has to answer six questions.
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.
Platform map
Different hosts want different store assets.
Storemetheus keeps the pattern portable across the tools teams actually use. The notes below are a current snapshot, linked to primary docs.
Claude Code
Native plugin marketplaces are the strongest current store primitive.
- Distribute
- Marketplace JSON, plugins, skills, agents, hooks, MCP servers, and install/update commands.
- Move
- Make the company store a GitHub-hosted marketplace first, then publish only curated plugins.
Codex
Best current fit is a governed local/plugin workspace with explicit evidence across source, cache, config, and active session.
- Distribute
- Skills, plugins, MCP servers, AGENTS.md, local app automations, and repo-backed install notes.
- Move
- Treat Codex as the proving surface for company-specific operating skills and recurring checks.
Cursor
Rules and MCP make Cursor a strong consumer of store-managed context and tools.
- Distribute
- .cursor/rules, AGENTS.md, MCP configuration, and project-scoped guidance.
- Move
- Publish compact project rules plus MCP recipes, then keep them tied to the same store source.
Devin
Knowledge and Playbooks are the store-shaped assets.
- Distribute
- Organization knowledge, enterprise knowledge, repo-pinned knowledge, playbooks, automations, and scheduled sessions.
- Move
- Convert repeated company workflows into small knowledge items and reusable playbooks.
Antigravity
Agent-manager and artifact-review surfaces make it a good target for verifiable store workflows.
- Distribute
- Rules, workflows, skills, subagents, and task artifacts.
- Move
- Ship store content as agent-readable workflows and require artifact proof after execution.
Creator pattern
Every store gets its own creator.
Users should not need to ask for Felix. The store should expose the creator that matches the world they are operating in: Greenmark Plugin Creator, Eidos Plugin Creator, or a client-specific creator.
Felix can stay behind the scenes as the scaffolding and validation engine. The user-facing contract should be store-local, permissioned, and documented in the store.
Templates
Three store shapes cover most serious work.
Company store
Home: private GitHub org repo
Creator: Company Plugin Creator
Governance: owner approval, install allow-list, release notes, audit trail
Client store
Home: client-owned private repo
Creator: Client Plugin Creator
Governance: client scope, no cross-client secrets, transfer-ready docs
Public ecosystem store
Home: public marketplace repo
Creator: Ecosystem Plugin Creator
Governance: security review, contribution policy, pinned releases, support channel
For agents
Start here, then prove every surface.
Use this prompt when an operator asks for a new company or personal plugin store.
Use Storemetheus to design a private plugin store.
Goal:
- owner:
- audience:
- host agents:
- first three workflows:
- approval policy:
- evidence needed before launch:
Read:
https://storemetheus-production.up.railway.app/storemetheus.md
https://storemetheus-production.up.railway.app/.well-known/storemetheus.jsonValidation
A store is not ready until it is visible where agents run.
sourcemarketplacecacheconfigactive-session
Operating docs
The reusable pattern lives with the repo.
Maintenance
This page should age visibly.
Refresh the official docs and install paths before making claims about a host.