Six Claude Code plugins for the work that keeps coming back: repo maps, conditional rules, ticketed parallel work, extra subscription models, local usage metrics, and guided setup.
翻译准备中
取自仓库 README
正在加载完整 README。 以下为已保存的摘录。
Claude Code can use a project well and still make you re-teach it the repository, lose a side issue, or repeat the same setup work in every new session.
The same thing happens around model choice and measurement. Expensive models get routine jobs, parallel changes need ownership and verification, and usage stays invisible until a bill or a slow week makes it obvious. Then a plugin install or update has its own friction: what scope did it change, which session needs a reload, and what is safe to turn on?查看完整 README ↗Claude Code can use a project well and still make you re-teach it the repository, lose a side issue, or repeat the same setup work in every new session.
The same thing happens around model choice and measurement. Expensive models get routine jobs, parallel changes need ownership and verification, and usage stays invisible until a bill or a slow week makes it obvious. Then a plugin install or update has its own friction: what scope did it change, which session needs a reload, and what is safe to turn on?
Toolshed packages those jobs as six independent Claude Code plugins. Use one, a few, or all six. Quartermaster is the guided starting path when you want help choosing, installing, and checking the pieces that fit a project, and it draws on whatever plugins are available on the machine, not only these six.
Sidequest makes it easy for every task recorded as a ticket to survive context compaction and new sessions. The task, instructions, status, and recorded discussion live on a local board, so Claude can pick the work up again after the chat context shrinks. Record decisions, progress, and next actions on the ticket to give the next session a useful starting point.
| Problem | Plugin | What it does |
|---|---|---|
| A fresh session keeps exploring the same repository | Codebase Mapper | Builds a small project map, loads it at session start, and refreshes the parts touched by changes. |
| Project rules get forgotten or fill every context | Live Rules | Re-injects matching rules when they apply, so conditional guidance stays out of unrelated work. |
| Tasks get lost when context compacts or a new session starts | Sidequest | Keeps every recorded task on a local board across context compaction and sessions, assigns ownership, dispatches independent work, and gates results on verification before integration. |
| You want the models and subscriptions you already have in Claude Code | Model Gateway | Adds supported ChatGPT/Codex and Grok subscription models to Claude Code's /model picker through a local gateway. |
| You want a number on the code Claude writes, not a vibe | Quality Gate | Scores every new or complexity-raised function by cyclomatic complexity and measured coverage (CRAP) from LCOV any language can produce, and reports missing measurement as unverified instead of guessing. |
| You cannot tell where time and tokens go | Observability | Records one metadata row per turn in a local JSONL ledger with per-project opt-in, and renders a self-contained local board. Nothing leaves the machine. |
| Setup, updates, and missing capabilities keep pushing back | Quartermaster | Recommends and installs plugins from any marketplace on the machine for setup, keeps active Toolshed installs current, checks health, and uses bounded session summaries to suggest one approved improvement at a time. |
Each plugin has its own install path and guide. None requires the others. Sidequest can route across Claude models on its own; Model Gateway is only needed for its non-Claude routes. Observability is separate from the other plugins and remains opt-in per project.
Use Quartermaster when you want Claude to look at a project and recommend what fits from the plugins available on the machine, Toolshed and otherwise, installing only what you approve. Before it names a plugin, it can check current sources for whether that plugin is still maintained, whether its cached description is stale, and whether something better fits, including from a marketplace you have not added yet. Searches use generic capability terms, so your project names and file paths stay out of the search engine's logs. Install a plugin directly when you already know which job you want.
From the project directory:
/plugin marketplace add Eigenwise/eigenwise-toolshed
/plugin install quartermaster@eigenwise-toolshed --scope project
/reload-plugins
/quartermaster:setup
continue.Quartermaster's setup uses project scope by default, but Claude Code also supports user and local scopes. Setup can recommend and install plugins from any marketplace. The updater is scoped to Toolshed only: it follows the recorded scope and project path for every active Toolshed install, so a request from one project can update Toolshed installs in other recorded projects too, and it never touches plugins from other marketplaces. Read the update and reload notes before running it.
Use the same marketplace with the scope you want:
/plugin marketplace add Eigenwise/eigenwise-toolshed
/plugin install <plugin-name>@eigenwise-toolshed --scope project
Replace <plugin-name> with sidequest, model-gateway, observability, codebase-mapper, live-rules, or quartermaster. Use --scope user for a plugin you want in every project, or --scope local when it should stay out of shared settings. Reload plugins or start a new session after an install. The plugin guides cover the first workflow for each one.
/quartermaster:update-toolshed is the requested updater. It refreshes the Eigenwise Toolshed marketplace and updates all active Toolshed registry installs at their recorded user, project, or local scope and project path. It leaves third-party marketplaces alone. Freshness hooks only report cached availability or loaded-version mismatches and point you to the updater; they do not install or restart anything.
Marketplace auto-update is optional. Enable it for the Eigenwise Toolshed marketplace in Claude Code if you want marketplace checks after session start. An open session still needs /reload-plugins after plugin code changes. Changes to process-level gateway wiring or model discovery may need a new Claude Code process instead of a reload.
Toolshed plugins run inside Claude Code and use its plugin marketplace, plugin scopes, and reload commands. Quartermaster's local scripts use Node.js and the Node standard library. Model Gateway also needs the supported provider subscription and local process setup described in its guide. The plugin does not include that subscription. No plugin activation opts a project into telemetry, a gateway, or Sidequest routing by itself.
Toolshed's plugin code is free and MIT-licensed. If it saves you time, optional donations through Ko-fi or GitHub Sponsors support its maintenance. Donations are never required to install or use a plugin.