Borrowing it
Nothing to install: this file belongs to vivalalova/claude-plugins-manager. 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/vivalalova/claude-plugins-manager/main/CLAUDE.mdgit clone --depth 1 https://github.com/vivalalova/claude-plugins-managerWrote 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/instructions/vivalalova/claude-plugins-manager/claude-md)<a href="https://agentmods.dev/instructions/vivalalova/claude-plugins-manager/claude-md"><img src="https://agentmods.dev/badge/instructions/vivalalova/claude-plugins-manager/claude-md.svg" alt="Measured on agentmods" 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.01433 | $0.01433 |
| Opus 5 | $0.00717 | $0.00717 |
| Sonnet 5 | $0.00287 | $0.00287 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
claude-plugins-manager CLAUDE.md 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 7d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Plugins Manager — VSCode Extension
指令
npm run typecheck
npm test
npm run build
npm run verify
npm run check:schema
npm run install:ext
npm run watch
有程式碼改動先跑 npm run verify,完成後一律跑 npm run install:ext。
專案不變量
src/shared/types.ts放非 settings 共用型別;ClaudeSettings/HookCommand只從 generated 檔轉匯出,禁止再手寫平行 interface。src/shared/claude-settings-schema.ts是 settings value shape + UI metadata 唯一來源。section 陣列順序就是 UI 渲染順序,enum 用 schema value +Stringcontrol,不要再加hidden逃生門。controlType預設由valueSchema推導;只有 mixed union 或刻意走 custom editor 的欄位才顯式 override。options/min/max/step也是由valueSchema即時推導,不要在 schema entry 或 flat schema 手寫平行資料。src/shared/claude-settings-types.generated.ts是 schema 衍生物;build/typecheck/test/lint 會自動重生,禁止手改 generated 檔。- Settings UI 以 schema-driven 為主;
PermissionsSection與 object 型欄位 editor 保持手動實作,其餘優先走SchemaFieldRenderer。 - 已知 env vars 一律維護在
src/shared/known-env-vars.ts,不要在 UI 或 service 內各自維護清單。 - Extension 和 Webview 的通訊契約只走
protocol.ts定義的 request/response/push message。 - Service 邊界保持清楚:CLI 封裝放
CliService,設定檔存取放SettingsFileService,UI 偏好持久化放PreferencesService。
設定頁開發
- 新增 setting 時,同步更新 schema、對應 editor/i18n,然後重生 settings generated types;不要再手動補
ClaudeSettings/HookCommand。 - 沒有自然落點的 user-facing key 直接放
advanced。 Managed settings only的 key 不做 first-party UI;包含 top-level managed key 與 sandbox nested managed key。若使用者既有 settings 檔有這些欄位,只保持 unknown/raw JSON 容忍,不新增一般 scope 控制項。- 官方 docs 有但 SchemaStore 尚未收錄的 user-facing key 可以同步到 UI;type/default 以 docs 文字為準,並在
check:schema只驗 repo 內 schema 一致性。 controlType: Object的欄位在對應 section 內手動渲染,不要硬塞進通用 renderer。- Schema 巢狀欄位(如
permissions.defaultMode、permissions.disableAutoMode)若要在 UI surface 為 top-level 欄位,必須加nestedUnder: 'permissions',UI 才會寫到settings.permissions[key];漏加 → 寫到settings[key]頂層位置,CLI 讀不到(silent bug,UI toggle 完全沒效果)。 PermissionsSection手動 render 巢狀欄位時要走updatePermissions({ ...perms, [key]: value }),禁止直接onSave(key, value)(會繞過nestedUnder機制寫到頂層)。- 實作設定頁新功能前,先查 JSON Schema: claude-code-settings.json
- SchemaStore 可能落後官方 docs;同步 settings 時一定要再交叉比對 code.claude.com/docs/en/settings
- 同步 Claude settings docs 變更回 repo 前,先讀 .claude/skills/update-settings-options/SKILL.md
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.
- 7d ago First seen · 79 lines · 1,433 tokens per session scan A aad40cfed56f
claude-plugins-manager CLAUDE.md is an instructions file published in the GitHub repository vivalalova/claude-plugins-manager (2 stars, last pushed 17d ago), licensed MIT. It adds 1,433 tokens to every session, about $0.0072 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.