Marketplace

prxy.monster is composable — every piece of behaviour past “forward the request” is a module. Modules can be official (shipped by us), community (third-party, listed in the public registry), or private (loaded from a local file, never published).

The marketplace is the public registry of vetted modules. Browse it at modules.prxy.monster , or directly in the underlying GitHub repo:

🏛 Registry: Ekkos-Technologies-Inc/prxy-modules-registry

What’s there today

Official modules — `@prxy-official/*`

The 12 modules shipped with every cloud and local install. These mirror the contents of @prxy/modules-core and ship enabled-by-default in cloud mode:

Module	Category	What it does
`ipc`	context	Compresses older messages instead of dropping them
`mcp-optimizer`	optimization	Prunes MCP tools to ones actually relevant to the request
`semantic-cache`	cache	Returns cached responses for semantically similar requests
`exact-cache`	cache	Returns cached responses for byte-identical requests
`patterns`	injection	Injects relevant patterns from past sessions
`cost-guard`	safety	Per-request / per-day / per-month USD budget enforcement
`router`	routing	Picks the cheapest model that fits the budget
`prompt-optimizer`	optimization	Restructures requests to maximize Anthropic prefix-cache hits
`tool-cache`	cache	Observes (and eventually caches) MCP tool-call results
`guardrails`	safety	PII redaction + content blocking via regex patterns
`rehydrator`	context	Pulls archived context back when the user references past turns
`compaction-bridge`	context	Survives Claude Code’s auto-compaction without state loss

Community modules — `@community/*`

Empty at v0 launch. The first community submissions will appear here.

Verification levels

Tier	What it means	Badge
`unverified`	Submitted but not reviewed	none
`verified`	Manual review by the prxy team — code audit, no telemetry, follows SDK contract	✅ Verified
`featured`	Recommended by prxy team for specific use cases	⭐ Featured
`official`	Maintained by ekkOS Technologies Inc.	🏛 Official

Verification is async — publish first, then optionally request verification. The gate is a human review of the package source.

Installing a marketplace module

Cloud users

Cloud users do not install npm packages directly. The pipeline only loads modules listed in the registry (security gate). Add the module name to your PRXY_PIPE:


PRXY_PIPE='mcp-optimizer,semantic-cache,@community/slack-notifier'

The cloud runtime preloads every registered module; missing entries return a clear error at config validation time.

Local users

Local users install the npm package, then reference it in PRXY_PIPE:


npm install @community/slack-notifier
PRXY_PIPE='mcp-optimizer,semantic-cache,@community/slack-notifier'

The pipeline loader resolves package-style entries via dynamic import(). The package must export a Module (or factory returning one) as its default export, and must declare @prxy/module-sdk as a peer dep.

Local-mode npm-package loading lands in v1.1 — until then, point PRXY_PIPE at a local file path. See Publishing for the file-path loading shape.

Submit your own module

Build it with @prxy/module-sdk.
Publish to npm under your own scope (@your-name/your-module).
Open a PR to the registry adding modules/@community/your-module.json.
CI validates the manifest. A maintainer reviews and merges.
Your module appears at https://modules.prxy.monster within an hour.

Full publishing guide: Publishing.

Paid modules — coming later

The marketplace is free-only at v0. Paid modules (with revenue share via Stripe Connect, default 70/30 author/marketplace) land once we have real community demand. Track progress in docs/proposals/module-marketplace-v0.md.