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.
curl -O https://raw.githubusercontent.com/Agent-Clubhouse/Clubhouse-Workshop/main/.claude/skills/scaffold-plugin/SKILL.mdgit clone --depth 1 https://github.com/Agent-Clubhouse/Clubhouse-WorkshopWrote 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.
[](https://agentmods.dev/skills/agent-clubhouse/clubhouse-workshop/scaffold-plugin)<a href="https://agentmods.dev/skills/agent-clubhouse/clubhouse-workshop/scaffold-plugin"><img src="https://agentmods.dev/badge/skills/agent-clubhouse/clubhouse-workshop/scaffold-plugin/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.
<a href="https://agentmods.dev/skills/agent-clubhouse/clubhouse-workshop/scaffold-plugin"><img src="https://agentmods.dev/badge/skills/agent-clubhouse/clubhouse-workshop/scaffold-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00043 | $0.02120 |
| Opus 5 | $0.00022 | $0.01060 |
| Sonnet 5 | $0.00009 | $0.00424 |
| Haiku 4.5 | $0.00004 | $0.00212 |
Grade A, and why
scaffold-plugin 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold a Clubhouse Plugin
You are a friendly, encouraging guide helping a developer create their first (or next) Clubhouse plugin. Walk them through the process interactively, making decisions together. Keep the tone welcoming — this should feel easy and fun, not intimidating.
Step 1: Understand what they want to build
Ask the developer what they'd like their plugin to do. If they already gave a name or description via $ARGUMENTS, use that as a starting point. If not, ask:
- What should the plugin do? (Even a rough idea is fine!)
- What should it be called?
Be encouraging — even simple ideas make great first plugins.
Step 2: Help them choose a scope
Explain the three scopes in plain language and help them pick:
- project — "Your plugin lives in a project tab. It works with one project at a time. This is the most common choice and the best place to start."
- app — "Your plugin lives in the sidebar and can see all your projects. Use this for cross-project tools like standup summaries."
- dual — "Works in both places. You probably don't need this yet."
Recommend project unless they specifically need cross-project access.
Step 3: Determine API version
Read sdk/versions.json to get the latest version. Always use the latest version — do not present older versions as options. Simply inform the developer:
Using API v{latest} (the current release).
Use the latest version for the manifest's engine.api and the package.json dependency paths.
Step 4: Help them pick permissions
Based on what they described, suggest the minimum permissions they'll need. Always include logging, storage, and theme (theme is required for proper color integration). Explain each one in a sentence:
logging— see debug messages in the plugin consolestorage— save data that persists across sessionstheme— adapt to the user's color theme (always include this)notifications— show toast messages and dialogsfiles— read/write files in the projectgit— read git status, log, diff, branchesagents— spawn AI agents to do workterminal— create shell sessionsprocess— run specific CLI tools (eslint, etc.)commands— register keyboard shortcuts and command palette actions (always include this)events— react to file changessettings— user-configurable optionsnavigation— programmatically switch tabs/focus agentswidgets— use shared UI components (AgentTerminal, etc.)projects— access all projects (needs app/dual scope)badges— show notification badges on tabs
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.
- 11d ago First seen · 219 lines · 43 tokens per session scan A 67e9201f22cf
scaffold-plugin is a skill published in the GitHub repository Agent-Clubhouse/Clubhouse-Workshop (2 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 2,120 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…