Ext Ops Panel
Open dashboard
Comparison

dominion-flow vs AgentDiet Automated /llms.txt & Agent Documentation Context Compiler

dominion-flow is a plugin bundle for AI coding tools published by ThierryN. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). AgentDiet Automated /llms.txt & Agent Documentation Context Compiler is an MCP server published by agentdiet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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

Where each is published
Marketplacedominion-flowAgentDiet Automated /llms.txt & Agent Documentation Context Compiler
Claude Code: claude-plugins-community Listed
Version: 12.9.0
Forks (GitHub): 18
Stars (GitHub): 78
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 7.0.17
Forks (GitHub): 0
Stars (GitHub): 0
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

dominion-flow vs AgentDiet Automated /llms.txt & Agent Documentation Context Compiler
Factdominion-flowAgentDiet Automated /llms.txt & Agent Documentation Context Compiler
Marketplaces that list it11
Stars (GitHub) (differs)78 (better)0 (worse)
Forks (GitHub) (differs)18 (better)0 (worse)
Last release (differs)Not published2026-10-21
Where it runs (differs)Installs as a plugin bundleRemote server (llms-generator.agentdiet.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)66Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/thierryn/fire-flowgithub.com/robertoyanguas-ops/assay
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-19
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

dominion-flow

In its own words, on Claude Code: claude-plugins-community:

Research-backed orchestration for Claude Code. Structured workflow from idea to production with parallel execution, session memory, 70-point validation, autonomous mode, and adversarial review. 49 commands, 51 agents across 7 departments.

AgentDiet Automated /llms.txt & Agent Documentation Context Compiler

In its own words, on Official MCP Registry:

Crawls any documentation or SaaS site and compiles a standards-compliant /llms.txt manifest and J.

How to run each

dominion-flow As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dominion-flow@claude-community

AgentDiet Automated /llms.txt & Agent Documentation Context Compiler As a remote MCP server

Claude Code
claude mcp add --transport http llms-generator https://llms-generator.agentdiet.dev/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

Neither one's marketplaces publish the settings it asks for.

What it can do: dominion-flow · What it can do: AgentDiet Automated /llms.txt & Agent Documentation Context Compiler · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built