Mothy Marketplace

Moth+Flame's Claude Code / Cowork plugin marketplace (public GitHub repo — no sign-in needed to add it).

This marketplace ships a single plugin — mothy — bundling the Moth+Flame team agent's skills + slash commands: customer briefs, capability decks, cross-source intel, in-place Google Workspace edits, demo videos, KB articles, and teammate onboarding.

1. Add the marketplace + install the plugin

In a terminal (not the app's chat box):

claude plugin marketplace add moth-flame/mothy-plugins
claude plugin install mothy@mothy-marketplace

This installs skills + commands only — no connector. (Intentional — see "Why skills-only" below.)

2. Connect the Mothy connector (one-time — gives the skills their tools)

Mothy is an org connector — it's already in everyone's connector list. No token to mint, nothing to paste. Easiest: just say "walk me through getting set up" (or /connect) and Mothy guides you. The steps:

• Desktop app (Chat / Cowork / Code):
  1. Customize → Connectors → find Mothy → Connect.
  2. Sign in with Google (@mothandflamevr.com).
  3. On Mothy's connector page, set Tool permissions → Always allow.
• Terminal Claude Code CLI: /mcp → select mothy → Authenticate (browser OAuth; works because the loopback is local).

Then test: "use mothy, run whoami" → returns your email.

Fallback only — if the org connector isn't in your list: generate a per-user URL at https://mothy-mcp.vercel.app/connect (Sign in with Google → Copy) and Customize → Connectors → Add custom connector → paste → name it Mothy.

Why skills-only (no bundled connector)

The plugin ships skills + commands only — it does NOT bundle an MCP connector. Mothy is published as an org connector that appears in the connector list ready to Connect; bundling one in the plugin would only create a dead, duplicate placeholder. The org connector is provisioned separately from the plugin.

Hooks the plugin brings with it

Installing mothy also installs a few small hooks. You do not invoke them.

Hook	When	What it does
precompact-snapshot.sh + auto-park.mjs	before a compaction	writes the objective state and the reasoning to .claude/ so a compaction does not lose them
post-compaction-notice.sh	first prompt after one	hands that back, once
arm-push-gate.mjs	session start	turns on the pre-push gate the repo already ships

Why the last one exists. Git hooks are per-clone. .git/hooks/* is never cloned, and a repo that keeps its hooks in a tracked .githooks/ still needs core.hooksPath set — which is local git config, also not cloned. So a fresh clone, and every cloud session, pushes with no gate at all and no sign that anything is missing. This hook runs that one idempotent command for you.

It never writes a hook and never guesses a test command — it only switches on what the repo itself authored (.githooks/pre-push, or the repo's own scripts/install-hooks.sh). If the repo's CLAUDE.md/AGENTS.md says it wants a pre-push gate and none can be found, it says so rather than going quiet. In a repo that declares nothing, it is silent.

Turn it off with MOTHY_ARM_PUSH_GATE=0 (default on).

Access

Org-only marketplace for Moth+Flame (the GitHub repo itself is public — no sign-in needed to add it). Mothy's data + actions are gated separately, on a valid @mothandflamevr.com identity (your /connect sign-in or an admin-minted token). Not in the registry yet? Message Rich or Chris.

What's inside

Plugin	What it does
mothy	Moth+Flame team agent skills + commands — briefs, decks, intel, Google Workspace edits, demo videos (/video), KB articles (/article), video pipeline setup (/video-setup), onboarding. See plugins/mothy/README.md.