Ext Ops Panel
Open dashboard
Comparison

focused-review vs audit-project

focused-review is a plugin bundle for AI coding tools published by 0101. Marketplaces we read that list it: 1 (Community GitHub marketplaces). audit-project is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, 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

Where each is published
Marketplacefocused-reviewaudit-project
Community marketplace 0101/focused-review Not seen in the last pass
Version: 0.11.13
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 5.1.0
Forks (GitHub): 2
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

focused-review vs audit-project
Factfocused-reviewaudit-project
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)54
LicenceMITMIT
Repository (differs)github.com/0101/focused-reviewgithub.com/agent-sh/audit-project
Changes in the last 7 days22
First seen (differs)2026-10-142026-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

focused-review

In its own words, on Community GitHub marketplaces:

Auto-generates review rules from instruction files and runs parallel code reviews

audit-project

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

Multi-agent iterative code review until zero issues remain. Spawns up to 10 specialist reviewers (code quality, security, performance, test coverage, architecture, database, API, frontend, backend, DevOps) chosen based on the project's signals. Each pass produces certainty-graded findings (HIGH / MEDIUM / LOW); HIGH findings auto-fix where safe. The orchestrator iterates passes until zero open issues remain or a max-iteration cap is reached. Specialists are role-based (defined inline via Task tool, not file-based agents) so they don't bloat the plugin's agent count. Designed to plug into /next-task and /prepare-delivery as the deep-review phase.

How to run each

focused-review As a Claude Code plugin

Claude Code
/plugin marketplace add 0101/focused-review
/plugin install focused-review@focused-review

audit-project As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install audit-project@claude-community

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: focused-review · What it can do: audit-project · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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