writ vs Ouroboros
writ is a plugin bundle for AI coding tools published by infinri. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Ouroboros is an MCP server published by Q00. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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 |  writ |  Ouroboros |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 2.0.0 Forks (GitHub): 15 Stars (GitHub): 216 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.51.5 Downloads/month (PyPI): 91 699 Downloads/week (PyPI): 13 352 Forks (GitHub): 627 Stars (GitHub): 6 223 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 | writ | Ouroboros |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 216 (worse) | 6 223 (better) |
| Forks (GitHub) (differs) | 15 (worse) | 627 (better) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (ouroboros-ai) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | Not published | 3 |
| Parts of the bundle (differs) | 2 | 27 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/infinri/writ | github.com/q00/ouroboros |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-12 | 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
writ
Hybrid RAG rule retrieval and workflow enforcement for Claude Code. A five-stage pipeline (BM25 + vector + graph traversal + two-pass ranking) retrieves the right coding rules for each task in under 1ms from a Neo4j knowledge graph,. 726x context reduction vs loading a full rulebook at 10K rules. A mode and gate state machine enforces workflow discipline at the tool-call boundary: - writes are blocked until plans and tests are approved. - Ships with 276 rules across 12 domains (Security, Clean Code, DRY, SOLID, Architecture, Testing, Error Handling, Performance, Scaling, API Design, Process, Documentation). - AI agents can propose new rules through a structural gate; frequency-driven graduation and human review control what stays.
Ouroboros
Pins an acceptance spec; the verify command and expected output never enter the success contract.
How to run each
writ As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install writ@claude-communityOuroboros As a local MCP server: PyPI package
claude mcp add --transport stdio ouroboros -- uvx --from "ouroboros-ai[mcp]" --with mcp==2.0.0 ouroboros ouroboros-ai mcp serve --runtime claude-cliCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: writ · What it can do: Ouroboros · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.