[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-96199":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":9,"totalLinesOfCode":9,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":9,"subscribersCount":14,"size":14,"stars1d":14,"stars7d":14,"stars30d":14,"stars90d":14,"forks30d":14,"starsTrendScore":14,"compositeScore":16,"rankGlobal":9,"rankLanguage":9,"license":9,"archived":17,"fork":17,"defaultBranch":18,"hasWiki":17,"hasPages":17,"topics":9,"createdAt":9,"pushedAt":9,"updatedAt":19,"readmeContent":20,"aiSummary":21,"trendingCount":14,"starSnapshotCount":14,"syncStatus":15,"lastSyncTime":22,"discoverSource":23},96199,"eigenwise-toolshed","Eigenwise\u002Feigenwise-toolshed","Eigenwise","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.",null,"https:\u002F\u002Fgithub.com\u002FEigenwise\u002Feigenwise-toolshed","JavaScript",130,18,0,2,40.84,false,"main","2026-09-20 04:01:32","# Eigenwise Toolshed\n\n[![Claude Code](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FClaude_Code-plugin_marketplace-D97757?logo=claude&logoColor=white)](https:\u002F\u002Fclaude.com\u002Fclaude-code)\n[![Docs](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fdocs-online-CB7D32)](https:\u002F\u002Feigenwise.github.io\u002Feigenwise-toolshed\u002F)\n[![License: MIT](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-MIT-yellow)](.\u002FLICENSE)\n[![GitHub Sponsors](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FSponsor-EA4AAA?logo=githubsponsors&logoColor=white)](https:\u002F\u002Fgithub.com\u002Fsponsors\u002FEigenwise)\n[![Ko-fi](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FKo--fi-support-FF5E5B?logo=kofi&logoColor=white)](https:\u002F\u002Fko-fi.com\u002Feigenwise)\n\nClaude 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.\n\nThe 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?\n\nToolshed 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.\n\n## The six plugins\n\n| Problem | Plugin | What it does |\n| --- | --- | --- |\n| A fresh session keeps exploring the same repository | [Codebase Mapper](.\u002Fplugins\u002Fcodebase-mapper) | Builds a small project map, loads it at session start, and refreshes the parts touched by changes. |\n| Project rules get forgotten or fill every context | [Live Rules](.\u002Fplugins\u002Flive-rules) | Re-injects matching rules when they apply, so conditional guidance stays out of unrelated work. |\n| Side work gets lost, and parallel changes need a clear owner | [Sidequest](.\u002Fplugins\u002Fsidequest) | Tracks work as tickets, claims changes before work starts, dispatches independent work, and gates results on verification before integration. |\n| You want the models and subscriptions you already have in Claude Code | [Model Gateway](.\u002Fplugins\u002Fmodel-gateway) | Adds supported ChatGPT\u002FCodex and Grok subscription models to Claude Code's `\u002Fmodel` picker through a local gateway. |\n| You cannot tell where time and tokens go | [Observability](.\u002Fplugins\u002Fobservability) | Records selected session and tool metadata locally, with per-project opt-in and optional sinks. |\n| Setup, updates, and missing capabilities keep pushing back | [Quartermaster](.\u002Fplugins\u002Fquartermaster) | 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. |\n\nEach 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.\n\n## Start with Quartermaster\n\nUse 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.\n\nFrom the project directory:\n\n1. Add the marketplace.\n   ```text\n   \u002Fplugin marketplace add Eigenwise\u002Feigenwise-toolshed\n   ```\n2. Install Quartermaster for this project. Project scope is the default example because the choice stays with the repository.\n   ```text\n   \u002Fplugin install quartermaster@eigenwise-toolshed --scope project\n   ```\n3. Activate the installed plugin by reloading plugins or starting a new Claude Code session.\n   ```text\n   \u002Freload-plugins\n   ```\n4. Run setup and approve the plan item by item.\n   ```text\n   \u002Fquartermaster:setup\n   ```\n5. Setup installs the selected plugins and writes the approved workspace files. When it pauses at the reload boundary, reload plugins or restart Claude Code if the change affects the process environment, then tell Claude `continue`.\n6. Let setup verify the installed plugins and workspace after that boundary. Try one real request in the project before adding more pieces.\n\nQuartermaster'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.\n\n## Install a plugin directly\n\nUse the same marketplace with the scope you want:\n\n```text\n\u002Fplugin marketplace add Eigenwise\u002Feigenwise-toolshed\n\u002Fplugin install \u003Cplugin-name>@eigenwise-toolshed --scope project\n```\n\nReplace `\u003Cplugin-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](https:\u002F\u002Feigenwise.github.io\u002Feigenwise-toolshed\u002Fgetting-started\u002F) cover the first workflow for each one.\n\n## Updates and reloads\n\n`\u002Fquartermaster: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.\n\nMarketplace 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 `\u002Freload-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.\n\n## Docs and source\n\n- [Getting started](https:\u002F\u002Feigenwise.github.io\u002Feigenwise-toolshed\u002Fgetting-started\u002F)\n- [Quartermaster setup guide](https:\u002F\u002Feigenwise.github.io\u002Feigenwise-toolshed\u002Fgetting-started\u002Fquartermaster\u002F)\n- [Plugin reference](https:\u002F\u002Feigenwise.github.io\u002Feigenwise-toolshed\u002Freference\u002F)\n- [Contributing](https:\u002F\u002Feigenwise.github.io\u002Feigenwise-toolshed\u002Fcontributing\u002F)\n- [Release process](https:\u002F\u002Feigenwise.github.io\u002Feigenwise-toolshed\u002Frelease-process\u002F)\n- [Support](https:\u002F\u002Feigenwise.github.io\u002Feigenwise-toolshed\u002Fsupport\u002F)\n- [GitHub repository](https:\u002F\u002Fgithub.com\u002FEigenwise\u002Feigenwise-toolshed)\n\n## Compatibility\n\nToolshed 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 provider access and local process setup described in its guide. No plugin activation opts a project into telemetry, a gateway, or Sidequest routing by itself.\n\n## Support\n\nIf these tools save you time, optional support is available through [Ko-fi](https:\u002F\u002Fko-fi.com\u002Feigenwise) or [GitHub Sponsors](https:\u002F\u002Fgithub.com\u002Fsponsors\u002FEigenwise).\n\n## License\n\n[MIT](.\u002FLICENSE)\n","Eigenwise Toolshed 是一套面向 Claude Code 的轻量级插件集合，旨在解决开发者在日常 AI 编程协作中反复出现的六类高频问题：代码库理解、条件规则管理、并行任务追踪、模型订阅扩展、本地使用可观测性及插件化引导配置。项目采用模块化设计，六个插件（Codebase Mapper、Live Rules、Sidequest、Model Gateway、Observability、Quartermaster）彼此独立、按需启用，全部运行于本地，不依赖远程服务。适用于中大型代码库的团队协作场景，尤其适合需要提升 Claude Code 会话一致性、任务可追溯性与资源使用透明度的工程实践。","2026-09-12 02:30:06","trending"]