zero

zero-plugins

Official ZeroClick plugins. Zero is a search engine and payment layer for AI agents: discover external paid capabilities (x402 / MPP), call them, and pay per use with a wallet — from Claude Code, Claude (web), Cowork, Codex, and anywhere else that speaks the plugin or MCP format.

This repo is a Claude plugin marketplace containing one plugin today: zero.

Install

# In Claude Code:
/plugin marketplace add spencercharest/zero-plugins   # or this repo's git URL
/plugin install zero@zeroclick

On claude.ai web / Cowork, install the zero plugin from the Customize → Plugins menu (it bundles the skill and the Zero MCP connector in one install).

The zero plugin

plugins/zero/ bundles the full Zero integration:

Component	File	Purpose
Skill	skills/zero/SKILL.md	Teaches the agent the search → inspect → call → review loop and how to pick a runtime mode.
MCP connector	.mcp.json	The Zero connector (tools search, get, fetch, mint_runner_session; surfaced namespaced, e.g. zero:fetch). Auth is OAuth, handled by the host.
SessionStart hook	hooks/hooks.json + hooks/ensure-runner.sh	Provisions a local runner and injects the Zero reminder once per session. Also runs the CLI-install de-dupe (below).
UserPromptSubmit hook	hooks/hooks.json + hooks/zero-context.sh	Re-injects a short reminder on every prompt to reach for Zero before saying "I can't".
PreToolUse hook	hooks/hooks.json + hooks/auto-approve-zero.sh	Auto-approves read-only zero Bash commands (search, get, review, …) to cut permission fatigue. fetch and wallet still require manual approval. Same behavior zero init installs for CLI-only setups.
CLI-install de-dupe	hooks/dedupe-cli-install.mjs	Run from SessionStart (node-gated). Removes the duplicate skill + hooks a prior zero init left in ~/.claude, and adds the *.zero.xyz sandbox allowlist (which a plugin can't declare in its manifest). See "Coexisting with zero init" below.

Three runtime modes

The skill and hook converge on one of three modes, picked by environment:

1. CLI mode — a zero binary is on PATH. Calls run locally, signed with a local wallet/session; bodies stay local. (Claude Code, Codex, Cursor, dev machines.)
2. JS-runner mode — no binary, but node + network egress exist. Mint a short-lived token via the mint_runner_session MCP tool and drive the downloaded JS runner; bodies stay local. (Cowork.)
3. MCP mode — no local execution or egress. The connector's fetch tool proxies and pays server-side; Zero sees the body. (Plain claude.ai chat.)

What the SessionStart hook does

hooks/ensure-runner.sh resolves a runner in priority order and reports the active mode back to the agent via the SessionStart additionalContext payload:

1. zero already on PATH → CLI mode (nothing downloaded).
2. else node available → download the JS runner (zero.mjs) to ~/.zero/runner/zero.mjs → JS-runner mode.
3. else → download the standalone CLI binary to ~/.zero/bin/zero (and add it to PATH for the session) → CLI mode.
4. else (no egress / unsupported platform) → MCP mode fallback.

In modes 1–3 the hook exports $ZERO_RUNNER (via $CLAUDE_ENV_FILE) — an executable runner path that works as a drop-in for zero (the JS runner runs directly via its #!/usr/bin/env node shebang). The reminder hooks reference $ZERO_RUNNER so guidance is identical across modes; in MCP mode it's left unset and the agent uses the connector tools.

If the JS download fails but a binary can be fetched, it degrades to the binary rather than dead-ending.

Note: hooks run in Claude Code and Cowork, but are inert in plain claude.ai chat — that environment naturally lands on MCP mode, which needs no local runner.

Discovery nudges (reminder hooks)

Two hooks keep Zero top-of-mind so the agent reaches for it instead of giving up or handing work back to the user:

• SessionStart (ensure-runner.sh) appends a short Zero reminder to the runner-mode context it reports — one injection per session.
• UserPromptSubmit (zero-context.sh) re-injects the same reminder on every prompt.

The reminder is mode-neutral — it references the exported $ZERO_RUNNER rather than assuming a zero binary — and differs from the CLI's zero init reminder in two ways: it's jq-free (works where jq isn't present) and unconditional (it doesn't gate on command -v zero, since the plugin makes Zero reachable via CLI, JS runner, or MCP).

Coexisting with zero init