agex.dev
Platform

Platform Overview

How the agex hub is organized — artifacts, projects, community features, and discovery.

Hub sections

Explore

The Explore page is a browsable, searchable registry of agent artifacts. Every artifact has:

  • A Config Card landing page with README, install instructions, and metadata
  • Files tab with a file browser (supports multi-file artifacts with directory structure)
  • Issues tab for bug reports and feature requests
  • Versions tab with diff view and changelog history
  • Version review workflow (maintainers can require approval before publishing)
  • Community upvotes, download counts, and view counts
  • Stack tags, platform badges, and language detection

You can filter by category (Rules, Skills, MCP Servers, Hooks, Agents, Commands, CLI Tools), by specific type, and by platform (Claude Code, Cursor, Codex, Gemini CLI, OpenCode).

Projects

Projects are curated bundles of artifacts. A project groups related rules, skills, MCP configs, hooks, and agents that work together for a specific workflow or stack. Projects are defined locally with agex.toml and published to the hub, where others can pull the entire bundle in one command.

Collections

Collections are user-curated editorial lists of artifacts. Unlike projects (which are pullable bundles), collections are for organizing and sharing recommendations — e.g. "Best configs for Next.js + Claude Code" or "My production agent setup".

Discussions

A community forum with a minimal, text-first design. Categories include General, Show and Tell, RFC, and Q&A. Discussions can be global or scoped to a specific artifact.

Dashboard

Your home feed showing activity from people you follow: new artifacts, version updates, stars on your work. Includes suggested artifacts and quick access to your recent work.

Authentication

agex supports three sign-in methods:

  • GitHub OAuth — your GitHub username becomes your agex username
  • Google OAuth — creates an account linked to your Google email
  • Email + Password — traditional sign-in

The CLI uses GitHub's device flow for authentication.

Organizations

Organizations let teams share artifacts under a common namespace (@acme-corp/team-rules). Org members can create and edit org-owned artifacts based on their role (owner, admin, member). Private org artifacts are visible only to members. See Organizations for details.

API & Integration

  • REST API at /api/v1/ with interactive docs
  • Claude Code marketplace — agex serves as a marketplace.json source. Add with: /plugin marketplace add https://agex.dev/api/v1/marketplace.json
  • Per-user/project marketplaces — each user and project can be consumed as a Claude Code marketplace

Community signals

Artifacts accumulate upvotes, download counts, and view counts. A trending algorithm surfaces recently-active artifacts (recent votes weighted 3x + downloads). Badges like "Popular" and "Highly Rated" provide trust signals.

There are no sponsored placements or vendor bias. Every platform is supported equally.

Social features

  • Follow users to see their activity in your dashboard feed
  • Notifications for issues, comments, version reviews, and new followers
  • Collections for curating and sharing artifact lists

On this page