---
sidebar_position: 1
title: Agent Marketplace
---

# Agent Marketplace

Zibby ships a set of **ready-made agents** — production-ready automations you can deploy today. Each one is a real Zibby agent, eating its own dog food. Browse them, deploy with one command, and tune them to your project.

> An **Agent** is a deployed automation built on coding-agent CLIs. Build and ship one with the `zibby agent` CLI.

```
                       ┌──────────────────┐
   ┌──────────────────►│  zibby agent new │  ◄── Build your own
   │                   │  zibby agent ... │
   │                   └──────────────────┘
   │                              ▲
   │                              │ uses the same primitives
   │                              │
   │                   ┌──────────────────────┐
   │  Marketplace ────►│  board-runner        │  ◄── A whole dev team on a ticket board
   │  agents built     │  github-ai-scout     │  ◄── Daily AI-project radar
   │  on top of the    │  pipeline-supervisor │  ◄── Zibby managing Zibby
   │  same platform    │  sentry-triage       │  ◄── Incident routing
   │                   │  zibby test          │  ◄── Browser testing
   │                   └──────────────────────┘
```

You don't have to use the marketplace. You can build whatever agent you want with `zibby agent new`. The marketplace just saves you from writing the obvious starter graphs for common cases.

## Available agents

| Agent | What it does | Best for |
|---|---|---|
| MAGNUM (`board-runner`) | A project manager that runs a ticket board on a schedule: triage, a developer and a frontend developer that open PRs, a reviewer, a tester and a product owner — each a reusable building-block agent dispatched as a sub-graph. | Running a team from a ticket board, PRD → PR |
| [GitHub AI scout](./github-ai-scout) | Daily scan of new/trending AI projects on GitHub, LLM-scored against your rubric, shortlist posted to Slack | Tracking a fast-moving space without manual triage |
| [Pipeline supervisor](./pipeline-supervisor) | Watches the project's *other* agents, flags failing/slow ones, posts an improvement proposal to Slack/Lark | Zibby managing Zibby — agent fleet health |
| [Sentry triage](./sentry-triage) | Hourly: fetch unresolved Sentry issues, classify by severity, route via Slack/Lark (author DM + usergroup mention) | Automated incident routing without a human triager |
| [`zibby test`](./test) | Drives a browser via Cursor or Claude, runs assertions, generates a Playwright script + verification video | E2E test generation from plain-English specs |

Plus reusable **building-block agents** that the orchestrators compose via sub-graph dispatch — `ticket-triage`, `developer`, `tracker-writeback`, `notify-slack`, `notify-lark`, `notify-notion`. Each is independently deployable and usable on its own.

## Why a marketplace

Three reasons we ship ready-made agents alongside the platform:

1. **Proof of concept** — every marketplace agent IS a Zibby agent. If MAGNUM works, the platform works. You can see the actual graph definition and adapt it.
2. **Faster onboarding** — you don't need to design a full graph on day one. Deploy an agent, see the output, then build your own.
3. **Composable** — the orchestrators (MAGNUM) are built from smaller building-block agents dispatched as sub-graphs, so you can reuse the pieces in your own agents.

## Building your own agent

If you have an agent you'd want shipped as a built-in:

```bash
zibby agent new my-agent          # scaffold
# ... build it out ...
zibby agent run my-agent          # test locally
zibby agent deploy my-agent       # ship to your cloud account
```

If it's broadly useful, we may pull it into the official marketplace. Open an issue or PR.

## Next

- **[Build your own agent](../get-started/your-first-workflow)** — scaffold and customize
- **[Concepts: graph](../concepts/graph)** — the primitives every agent is built on