odere-pro — Claude Code plugin marketplace

Before you start

Requirements

A short checklist — the FAQ has one-line install pointers for each.

Claude Code with a working /plugin command. It's generally available — if you don't see it, update Claude Code.
git and bash on your PATH.
A few plugins also need Node.js / Bun or jq — each plugin lists its own prerequisites.

Get started

Install

Add the marketplace once, then install any plugin under the @odere-pro scope. Every step works from the in-session /plugin command or the claude plugin shell CLI.

Global — per-user (the default)

Available in every repo you open. In a Claude Code session (one command per line):

/plugin marketplace add odere-pro/claude-software-3-0-marketplace
/plugin install <plugin>@odere-pro

Or from the shell:

claude plugin marketplace add odere-pro/claude-software-3-0-marketplace
claude plugin install <plugin>@odere-pro

Project-local — scoped to one repo, shared with your team

Commit the marketplace and the plugins you want into a project's .claude/settings.json. Anyone who clones the repo gets the same tools:

{
  "extraKnownMarketplaces": {
    "odere-pro": {
      "source": { "source": "github", "repo": "odere-pro/claude-software-3-0-marketplace" }
    }
  },
  "enabledPlugins": {
    "<plugin>@odere-pro": true
  }
}

Or register the marketplace at project scope from the shell:

claude plugin marketplace add odere-pro/claude-software-3-0-marketplace --scope project

Manage what you've installed

claude plugin update <plugin>@odere-pro     # pull the latest from the plugin's default branch
claude plugin uninstall <plugin>@odere-pro  # remove it
claude plugin list                          # what's installed / enabled
claude plugin details <plugin>@odere-pro    # component inventory + projected token cost

The registry

Available plugins

Every plugin lives in its own repository and installs individually.

claude-oop-excellence

Audits and refactors codebases for object-oriented design quality: parallel RISK + PATTERN analysis tracks, a 102-entity glossary (45 issues, 57 patterns), and gated fix/implement commands — language-agnostic.

claude plugin install claude-oop-excellence@odere-pro --scope project
claude plugin update claude-oop-excellence@odere-pro --scope project

MIT oopobject-oriented-designsolidencapsulationdesign-patternsantipatternscode-qualityrefactoringauditrisk-scanlanguage-agnostic

claude-wiki-pages

Turns an Obsidian vault into a provenance-tracked LLM knowledge base on Karpathy's LLM Wiki pattern: a four-layer stack of 23 skills, 7 agents, and 15 schema-enforcing hooks ingests sources into typed, citation-verified pages — with offline Ollama support and git-checkpointed self-healing.

claude plugin install claude-wiki-pages@odere-pro --scope project
claude plugin update claude-wiki-pages@odere-pro --scope project

Apache-2.0 obsidianknowledge-baseknowledge-managementllm-wikiragmulti-agentagenticmarkdownprovenancelocal-modelsollamakarpathy

claude-calibration

Continuous evaluate-plan-calibrate-re-evaluate loop over Claude Code setups (CLAUDE.md, rules, skills, hooks, MCP, plugins) with scoring rubrics and enforcement scaffolding for recurring findings.

claude plugin install claude-calibration@odere-pro --scope project
claude plugin update claude-calibration@odere-pro --scope project

MIT calibrationevaluationconfig-auditharnessorchestrationclaude-code-setup

Help

FAQ

I don't have Claude Code / the /plugin command

Install or update Claude Code from the official setup guide; /plugin ships in current versions.

How do I install Git?

Get it from git-scm.com/downloads. On macOS, xcode-select --install also provides it; most Linux distros ship it via their package manager.

How do I install Node.js?

Download the LTS build from nodejs.org; that includes npm.

How do I manage Node versions (NVM)?

Use nvm (macOS/Linux) — nvm install --lts, then nvm use --lts. On Windows, use nvm-windows.

URL rejected: Malformed input… when adding the marketplace

Two commands were submitted on one line, so marketplace add swallowed the next as part of the repo argument. Run each command on its own line, marketplace add first.

already installed, or the plugin loads from a local path

A prior local/dev install (e.g. --plugin-dir, or the plugin's repo added as its own marketplace) shadows the marketplace copy. Uninstall, then reinstall:

claude plugin uninstall <plugin>@odere-pro
claude plugin install <plugin>@odere-pro

Install everything through the one odere-pro marketplace — don't also register an individual plugin's repo as a separate marketplace, or same-name entries collide.

I want to contribute or add a plugin

See CONTRIBUTING.md and docs/adding-plugins.md.

Claude Code plugins, one marketplace.