Ext Ops Panel
Open dashboard
Comparison

context-bench vs context-os

context-bench is a plugin bundle for AI coding tools published by nessos666. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). context-os is a plugin bundle for AI coding tools published by sravan27. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
Marketplacecontext-benchcontext-os
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 2.10.2
Forks (GitHub): 3
Stars (GitHub): 10
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

context-bench vs context-os
Factcontext-benchcontext-os
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)10 (better)
Forks (GitHub) (differs)0 (worse)3 (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
Hooks it runs (differs)32
Parts of the bundle (differs)37
LicenceMITMIT
Repository (differs)github.com/nessos666/context-benchgithub.com/sravan27/context-os
Changes in the last 7 days00
First seen2026-10-112026-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

context-bench

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

Plugin description: Self-learning Claude Code plugin that automatically detects what project you're working on and injects the right file context into every session. No manual configuration needed — it learns from your usage patterns, builds confidence scores, and removes stale topics automatically. Uses three hooks: UserPromptSubmit (match & inject), PostToolUse (track changes), SessionEnd (learn & decay). Zero dependencies, Python 3.9+ stdlib only.

context-os

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

Context OS helps Claude Code find the right files faster. It builds a local repo graph of paths, symbols, imports, line counts, and hot files, then injects a compact autocontext block with up to five likely file candidates for each prompt. It runs locally with no server, no embeddings, and no telemetry. Live proof in the repo shows 40.9 percent aggregate token reduction across 36 Claude Code calls.

How to run each

context-bench As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install context-bench@claude-community

context-os As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install context-os@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: context-bench · What it can do: context-os · Compare two other plugins

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