Mubit's Claude Code marketplace

This repository is the distribution point for Mubit's Claude Code plugins. It holds one plugin today:

Install

/plugin marketplace add mubit-ai/claude-plugins
/plugin install mubit-memory@mubit
/reload-plugins

Then start a new Claude Code session. /reload-plugins registers the hooks but does not fire SessionStart, so until a new session begins the plugin has never actually run: no run id, no registered agent, nothing on the status line. It looks broken and is fine.

Full setup, configuration and troubleshooting: integrations/claude-code/README.md.

Connect it to Mubit

/mubit-memory:auth

Opens the Mubit console, signs you in, and stores a key for this machine after checking it against your instance. No browser — over SSH, say — is covered in the plugin README.

This is a generated repository — do not edit it here

Contents are published from Mubit's source repository on release. Any commit made directly here is overwritten by the next publish.

source repository
  ├── .claude-plugin/marketplace.json ──┐
  └── integrations/claude-code/ ────────┤ published on release
                                        ▼
mubit-ai/claude-plugins (this repo)  →  git clone by Claude Code  →  a user's plugin dir

Claude Code fetches a GitHub marketplace with git clone --depth 1, using your own git credentials — there is no separate plugin token. If your git is configured for SSH only, run gh auth setup-git first; the clone URL is always HTTPS, even for sources written as git@.

The integrations/claude-code path is preserved deliberately: the marketplace entry's source is the marketplace-relative path ./integrations/claude-code, which resolves inside whichever repository served the catalog. Keeping the same path means marketplace.json needs no rewriting when it is published here, so there is nothing that can drift between the two copies.

What is published is the plugin's tracked files, minus development-only scripts and QA transcripts written against a developer's own checkout. What runs on your machine is exactly what you see here — Claude Code executes this directory as fetched, with no build step, which is why hooks/dist/, mcp/dist/ and bin/statusline.mjs are committed artifacts rather than build output.

Verifying what you are about to run

Everything here executes on your machine: nine hooks run as Node processes on Claude Code events, and the MCP server runs as a long-lived subprocess. Two things make that auditable:

• integrations/claude-code/hooks/src/ is the readable source for every bundle in hooks/dist/. Diff them rather than trusting the bundles — npm run build in integrations/claude-code regenerates the bundles in place, so a clean git diff afterwards is proof the committed artifacts match their source.
• integrations/claude-code/test/ carries the full suite, including the redaction cases — pattern scrub, path denylist, and byte caps applied after the scrub. Run it with npm test.

claude plugin validate .

License

Apache-2.0 — see integrations/claude-code/LICENSE.