Community agents and swarms

The community marketplace lives at two URLs that mirror each other in structure but cover different kinds of artefact:/community/agents for individual agents and /community/swarms for multi-agent swarms. The marketplace exists because the most valuable thing about a learning platform is not the lessons it ships with on day one; it is the body of work that the community of learners produces and shares with each other over time. Every agent and every swarm on the platform can be published to the marketplace, browsed, liked, commented on, and — most importantly — forked into another learner's workspace in a single click.

Browsing and discovery

The marketplace pages are designed for discovery rather than search. The default view ranks items by a combination of recency, likes, and run count, with a category filter on the left and a sort dropdown on the right that lets you switch to pure recency or pure likes. Every listed item shows a thumbnail (a generated preview for agents, an actual rendered swarm graph for swarms), a short description, the author's display name, and a count of likes and remixes.

• Item preview pages show a generous preview of what the agent or swarm actually contains: system prompts (with secrets stripped), node graphs (for swarms), the tool catalogue, the knowledge bases the agent is configured to attach to, and the author's notes on how they intended the artefact to be used. Previews are designed to let you decide whether to fork without committing to the fork first.
• Likes and comments work in the way they do on any modern social platform, with threaded comments under each item and notifications routed back to the author. The social affordances exist to encourage the community to surface high-quality work, and the platform deliberately does not surface engagement-bait metrics like vanity view counts.
• Sample runs for swarms let you try the author's exact configuration against a sample input without committing to a fork. The run is performed in a sandboxed version of your account so it counts towards no quota and produces no persistent state in your workspace, which is ideal for browsing.

Remixing and forking

Forking — what we call "remixing" — is the heart of the marketplace. Every item has a prominent "Remix" button that creates a fully-editable copy in your workspace, including the attached knowledge bases (which are themselves copied so you are not bound to the author's original) and any skills the agent depends on. The author of the original is credited on the remixed item's metadata but no ongoing dependency exists: changes to the original do not propagate to your fork, and changes to your fork do not affect the original.

Publishing your own work

Publishing an agent or a swarm is one click from the corresponding library page. The platform runs the candidate through the Publish Quality Check first, and only allows the item to be listed publicly once the check passes. The quality check is designed to protect both the author (from accidentally publishing a key) and the audience (from encountering broken or undocumented listings), and it is intentionally a little strict.

• No plaintext secrets in any prompt, tool configuration, or environment variable. Detected secrets block publication and the offending field is highlighted in the publish dialog so you can fix it.
• No obvious personally-identifiable informationin any prompt or knowledge-base snippet. A small classifier flags candidates and you can choose to confirm or remove them; confirmed PII blocks publication.
• Minimum description length of around eighty characters, because items with one-line descriptions almost never get any traction in the marketplace and we would rather catch the problem at publish time than let the item rot.
• At least one screenshot for swarms so the marketplace listing has a meaningful visual preview. The screenshot can be auto-generated from the canvas if you do not want to upload your own.
• Category and tags are required so the item can be found. Categories are curated and the picker suggests the right ones based on the item's contents.
• Remix permission can be set per item: open for anyone (the default and strongly recommended) or preview-only with the source visible but the fork button disabled. The latter is useful if you are publishing as a showcase rather than as a starting point.

Moderation and unpublishing

You can unpublish, edit, or update the description and tags of any of your published items at any time from your profile page. We do not take down items for any reason other than violations of the platform's terms of service (illegal content, abusive content, content that exfiltrates other users' data), and when we do we email the author with the reason and the option to appeal. Items removed for policy reasons leave a tombstone in the marketplace so that anyone who had previously forked them knows the original is gone and why.