Clubhouse-Workshop: Skill for Claude Code

.claude/skills/plugin-guide/SKILL.md

plugin-guide is a skill for Claude Code from Agent-Clubhouse/Clubhouse-Workshop. It costs 52 tokens per session (2,503 once invoked), scanned A, original, MIT.

A guide to the Clubhouse plugin system, including its structure, loading process, permissions, available interfaces, and development limits.

In plain words
What is it for?
Use it to learn about plugin manifests, activation and deactivation, user-interface panels, the sandboxed API, and supported development patterns.
Why use it?
It helps developers understand how plugins are loaded and connected to the application before they build or troubleshoot one. It also points out restrictions that could otherwise cause errors.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is Agent-Clubhouse/Clubhouse-Workshop's own configuration. It tells Claude Code how to work on Clubhouse-Workshop itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Clubhouse-Workshop configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Agent-Clubhouse/Clubhouse-Workshop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Agent-Clubhouse/Clubhouse-Workshop/main/.claude/skills/plugin-guide/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Agent-Clubhouse/Clubhouse-Workshop

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for plugin-guide

README.md
[![agentmods](https://agentmods.dev/badge/skills/agent-clubhouse/clubhouse-workshop/plugin-guide/github.svg)](https://agentmods.dev/skills/agent-clubhouse/clubhouse-workshop/plugin-guide)
Your own site
<a href="https://agentmods.dev/skills/agent-clubhouse/clubhouse-workshop/plugin-guide"><img src="https://agentmods.dev/badge/skills/agent-clubhouse/clubhouse-workshop/plugin-guide/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for plugin-guide

Your own site · 80×15
<a href="https://agentmods.dev/skills/agent-clubhouse/clubhouse-workshop/plugin-guide"><img src="https://agentmods.dev/badge/skills/agent-clubhouse/clubhouse-workshop/plugin-guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,503 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.02503
Opus 5 $0.00026 $0.01252
Sonnet 5 $0.00010 $0.00501
Haiku 4.5 $0.00005 $0.00250

Measured 9d ago against content hash cb0231194a0a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

plugin-guide scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/plugin-guide/SKILL.md · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Clubhouse Plugin Guide

You are a knowledgeable, friendly guide to the Clubhouse plugin system. When developers ask questions about how plugins work, answer clearly using the reference material below. Keep explanations approachable — use plain language and examples.

How to answer questions

  1. Answer the specific question first — don't dump the entire reference
  2. Include a code example when it helps
  3. Link to docs when there's more detail: point to the wiki
  4. Be honest about limitations — if something isn't supported yet, say so

Plugin Architecture Overview

Plugins are ES modules loaded by Clubhouse at runtime. The lifecycle:

  1. Manifest validation — Clubhouse reads manifest.json, checks API version, permissions, and structure
  2. Module loading — Dynamic import() of the built dist/main.js
  3. Activationactivate(ctx, api) is called with a context object and the sandboxed API
  4. Panel rendering — If the plugin exports MainPanel, SidebarPanel, etc., they are rendered in the UI
  5. Deactivationdeactivate() is called on unload; all subscriptions auto-disposed

Key constraints

  • React access: Use globalThis.React, not import React from 'react'
  • Module format: ES modules only (built with --format=esm)
  • React bundling: Must use --external:react — the app provides React
  • Runtime environment: Electron renderer (browser-like, no direct Node.js APIs)
  • Styling: Inline styles only; use CSS custom properties for theming
  • Bundle size: Keep under 100KB

Three Plugin Scopes

Scope When loaded Where it appears API access
project When a project is open Project tab bar api.project, api.git, project-scoped storage
app At app startup Sidebar rail api.projects (all projects), global storage
dual At app startup Both tab and rail Everything

Most plugins should be project scoped.

Read the full file on GitHub · 239 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 239 lines · 52 tokens per session scan A cb0231194a0a

Subscribe to this mod's changes

plugin-guide is a skill published in the GitHub repository Agent-Clubhouse/Clubhouse-Workshop (2 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 2,503 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens