Documentation
Add Agora to Claude Code
Agora installs as a plugin marketplace inside Claude Code. Pick whichever source you prefer.
1. Add the marketplace
From the Git repo (recommended — keeps you on the latest plugins):
/plugin marketplace add probablybadmove/agora
From the hosted manifest:
/plugin marketplace add https://agora.gagansingh.tech/marketplace.json
Either command registers the marketplace under the name agora.
2. Install a plugin
Install any plugin by name, scoped to the marketplace with @agora:
/plugin install conventional-commits@agora
Then reload so Claude Code picks it up:
/reload-plugins
(Or just restart Claude Code — same effect.)
3. Use it
Invoke the plugin's slash command in any project:
/conventional-commits:commit
Browse first (optional)
Start with the meta-plugin to see what's on offer:
/plugin install agora-welcome@agora /reload-plugins /agora-welcome:agora
List your plugin
Agora is an open marketplace — and your plugin stays in your repo. We list it by adding one entry to marketplace.json that points source at your GitHub repository, so you keep full ownership and control.
1. Prepare your plugin
Put your plugin in a public GitHub repo with a valid .claude-plugin/plugin.json at its root:
your-plugin/ .claude-plugin/ plugin.json # name, description, version, author skills/ # your slash commands (SKILL.md) agents/ # optional: subagents
Keep it focused — one plugin, one clear job — and project-aware: read the repo before acting.
2. Submit it
Open the plugin submission form. It files a pre-filled GitHub issue with your name, owner/repo, description, and category. That's the whole submission — no code goes into our repo.
3. We review and list it
A maintainer checks your repo, then adds a referencing entry:
{ "name": "your-plugin", "source": { "source": "github", "repo": "your-username/your-plugin", "ref": "v1.0.0" }, "description": "One sharp sentence: what it does.", "category": "Git" }
Once merged, anyone can install it with /plugin install your-plugin@agora, and it appears in the catalog here.
Prefer a pull request?
First-party plugins that live in this repo are welcome too — fork probablybadmove/agora, add a plugins/<name>/ directory plus a relative-source entry in .claude-plugin/marketplace.json, and open a PR.
About Agora
Agora is a marketplace of plugins for Claude Code. Add it once, and a shelf of focused slash commands and subagents becomes available inside your editor — each one a small, sharp tool that does one job well: writing your commit message, drafting your PR, scaffolding your tests, hardening your Dockerfile, untangling a regex, tuning a slow query.
The name is borrowed from the agora of the ancient Greek city — the open square at the heart of the polis where citizens gathered to trade goods, argue philosophy, and conduct the daily business of the city. It was marketplace, forum, and commons all at once. That is the idea here: a common space where good tools are brought into the light, shared freely, and put to honest use.
We've kept the spirit and dropped the togas. Every plugin in Agora is built to be idiomatic, project-aware, and quietly correct — it reads your repo before it opens its mouth. No ceremony, no boilerplate generators that spray the same template over every stack.
Walk in, take what's useful, and get back to building. The square is open.
Questions
FAQ
What exactly is a Claude Code plugin?
A plugin bundles slash commands and/or subagents that extend Claude Code. Agora’s plugins are task-focused: you run something like /conventional-commits and the plugin reads your repo, does the work, and hands back a result. Each one is small and does a single job well.
Do I have to install all the plugins?
No. Adding the marketplace just makes the catalog available — nothing runs until you install it. Pick only the plugins you want with /plugin install <name>@agora. Install one, install ten, or install agora-welcome first to browse the shelf.
Should I add Agora via the Git repo or the hosted marketplace.json?
Either works. `/plugin marketplace add probablybadmove/agora` pulls from the repo and resolves plugins via relative paths, which is the simplest way to stay current. The hosted manifest at https://agora.gagansingh.tech/marketplace.json adds the same catalog with absolute git-subdir sources. Use whichever you prefer.
I installed a plugin but the command isn't showing up. Why?
Plugins activate after a reload. Run /reload-plugins (or restart Claude Code) and the new slash command will appear. This is the single most common snag — a quick reload fixes it.
Are these plugins safe to run on my codebase?
Agora’s plugins are designed to read context and propose changes, not to act behind your back. Commit-, license-, and PR-style plugins show you the result and offer to proceed rather than committing or pushing silently. Every plugin’s source lives in the public repo, so you can read exactly what it does before installing.
How do I get my own plugin into Agora?
Open a pull request. Add a plugins/<your-plugin>/ directory and a matching entry in marketplace.json with a relative source path and a category, test it against your fork, and submit the PR. See the "Publish your own plugin" guide above.
Agora
The public square for Claude Code plugins.
© 2026 Agora · Built by Gagan Singh · MIT