The product

Marketplace

The Marketplaceis the social heart of Forgent. You publish your agents there so they get reused, you fork other people's, and you track in real time the installs/forks/views they rack up.

Two kinds of resourcesForgent distinguishes Templates (complete agents ready to install) from Skills (modules of expertise you attach to an existing agent). Each has its own pages. The marketplace lets you choose before you explore.

Page structure

The marketplace is organized into 4 distinct surfaces:

  • /marketplace — 2-choice landing. Describes Templates vs. Skills, shows the top 3 trending of each type. An explanatory gateway for a newcomer.
  • /marketplace/templates — Feed dedicated to templates. Category/model/capability filters, search bar, Trending/Recent/Most installed sorting.
  • /marketplace/skills — A twin feed for skills.
  • /marketplace/[slug]— An agent's detail page with hero, system prompt, configurable variables, and the stats + capabilities + creator sidebar.

Templates — complete agents

A Template contains everything you need to run an agent: name, system prompt, model, tools, MCP. On its detail page, the Install this agent button loads the configuration into the builder; you can adjust it before deploying.

The Remixbutton next to it opens a modal that lets you rename the fork and add a note ("what are you changing?"). This is the flow that creates the lineage (the fork keeps a link to its parent).

Skills — attachable modules

A Skilldoesn't run an agent on its own. It grafts a capability onto an existing agent: its prompt is concatenatedto the agent's system prompt, its tools are merged, its variables added.

On a Skill's detail page, two flows:

  • Start with this skill — creates a new empty agent with this skill already attached. You land in the builder with the prompt + tools pre-filled.
  • Add to my draft— if you're currently building an agent (a draft in progress in /builder), the Skill merges into it without overwriting what you've already written.

Publishing your agent

On the page of an agent you own (/deploy/[id]), the Publish to the marketplace button opens a modal with 3 states:

  1. Claim username— if you haven't yet chosen your handle, you do it in 1 step. The handle is unique, format [a-z0-9_-]{2,32}, and serves as the URL for your public profile.
  2. Configuration — type (Template/Skill), category (7 canonical values: Productivity, Analysis, Support, Monitoring, Dev, Writing, Finance), and a custom slug for the URL /marketplace/your-slug.
  3. Published — the public URL is shown with a Copy button + external link to verify. You can unpublish at any time (the slug is kept for future re-publishes, so your external links stay stable).
The slug is permanentOnce chosen, an agent's slug never changes, even if you unpublish then re-publish. That's what makes shared links stable — a screenshot in a Slack from 6 months ago keeps working.

Forking an agent

A fork creates a copy of the configuration under your account, with a lineage link back to the original. Concretely:

  • The creator of the original gets a notification in the bell in their header
  • Their Forks received counter increments (visible on their agent page and on their profile)
  • Your fork shows a butter chip “Forked from @parent/slug” visible everywhere — on /dashboard the Installed tab and on the /deploy/[id] page of your fork
  • If the original is deleted later, your fork keeps the lineage thanks to the snapshot that captures the info at the moment of the fork (with an archived suffix)

Creator profile

Any user who has published at least 1 agent has a public page /u/[username] with:

  • A colored avatar (stable color per handle, customizable in Settings)
  • A short bio (280 chars max)
  • 4 aggregate stats: agents published, cumulative installs, forks received, total views
  • A grid of all published agents, clickable

The profile is enumeration-resistant: an existing username with no publications returns 404 for visitors. Only the owner sees their own empty state with a CTA to publish.

Notifications

The bell in the top right shows a terra badge with the number of unread notifications. On click, the dropdown lists the last 50 (read + unread, sorted by date), and everything is marked read the moment you open it.

V1 handles only one event type: fork ("@user forked your agent X under the name Y"). Other types are coming: mention in an agent, install milestone, new release of a forked agent.

Business model

Today everything is free. The DB schema already includes a nullable priceCents field for future premium agents, but no purchase flow is exposed in V1.

  • Official Forgent Templates and Skills (@forgent): free forever
  • Community publications: free by default. Creators will be able to offer paid premium later with a Forgent commission
  • Marketplace access: no general paywall planned — exploring and forking will stay free