agent-council vs Lotor
agent-council is a plugin bundle for AI coding tools published by Avyayalaya. Marketplaces we read that list it: 2 (Copilot CLI: github/awesome-copilot, Community GitHub marketplaces). Lotor is an MCP server published by githubscum. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 0.1.3 Forks (GitHub): 6 Stars (GitHub): 11 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 Downloads/month (npm): 181 Downloads/week (npm): 39 Forks (GitHub): 7 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | agent-council | Lotor |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 11 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 6 (worse) | 7 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (lotor-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/avyayalaya/agent-council | github.com/githubscum/lotor |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
agent-council
A runtime-portable 5-agent quality gate that adjudicates text artifacts before they ship. Five role-conditioned LLM deliberators run a 2-round async protocol with cross-read rebuttal and return one verdict — SHIP, REVISE, or HOLD — plus a structured revision brief and a full audit transcript.
Lotor
A local receipt and approval gate for AI agent sessions. The agent can act, but it cannot sign.
How to run each
agent-council As a Claude Code plugin
/plugin marketplace add avyayalaya/agent-council
/plugin install agent-council@agent-council
Lotor As a local MCP server: npm package
claude mcp add --transport stdio lotor -- npx -y lotor-mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Lotor publish no settings it asks for, so we do not compare settings.
What it can do: agent-council · What it can do: Lotor · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.