winter-super-cli 2026.5.26 → 2026.5.28

package/resources/local/claude/plugins/marketplaces/claude-plugins-official/plugins/mcp-server-dev/skills/build-mcpb/references/local-security.md

@@ -1,149 +0,0 @@
-# Local MCP Security
-
-**MCPB provides no sandbox.** There's no `permissions` block in the manifest, no filesystem scoping, no network allowlist enforced by the platform. The server process runs with the user's full privileges — it can read any file the user can, spawn any process, hit any network endpoint.
-
-Claude drives it. That combination means: **tool inputs are untrusted**, even though they come from an AI the user trusts. A prompt-injected web page can make Claude call your `delete_file` tool with a path you didn't intend.
-
-Your tool handlers are the only defense. Everything below is about building that defense yourself.
-
----
-
-## Path traversal
-
-The #1 bug in local MCP servers. If you take a path parameter and join it to a root, **resolve and check containment**.
-
-```typescript
-import { resolve, relative, isAbsolute } from "node:path";
-
-function safeJoin(root: string, userPath: string): string {
-  const full = resolve(root, userPath);
-  const rel = relative(root, full);
-  if (rel.startsWith("..") || isAbsolute(rel)) {
-    throw new Error(`Path escapes root: ${userPath}`);
-  }
-  return full;
-}
-```
-
-`resolve` normalizes `..`, symlink segments, etc. `relative` tells you if the result left the root. Don't just `String.includes("..")` — that misses encoded and symlink-based escapes.
-
-**Python equivalent:**
-
-```python
-from pathlib import Path
-
-def safe_join(root: Path, user_path: str) -> Path:
-    full = (root / user_path).resolve()
-    if not full.is_relative_to(root.resolve()):
-        raise ValueError(f"Path escapes root: {user_path}")
-    return full
-```
-
----
-
-## Roots — ask the host, don't hardcode
-
-Before hardcoding `ROOT` from a config env var, check if the host supports `roots/list`. This is the spec-native way to get user-approved workspace boundaries.
-
-```typescript
-import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
-
-const server = new McpServer({ name: "...", version: "..." });
-
-let allowedRoots: string[] = [];
-server.server.oninitialized = async () => {
-  const caps = server.getClientCapabilities();
-  if (caps?.roots) {
-    const { roots } = await server.server.listRoots();
-    allowedRoots = roots.map(r => new URL(r.uri).pathname);
-  } else {
-    allowedRoots = [process.env.ROOT_DIR ?? process.cwd()];
-  }
-};
-```
-
-```python
-# fastmcp — inside a tool handler
-async def my_tool(ctx: Context) -> str:
-    try:
-        roots = await ctx.list_roots()
-        allowed = [urlparse(r.uri).path for r in roots]
-    except Exception:
-        allowed = [os.environ.get("ROOT_DIR", os.getcwd())]
-```
-
-If roots are available, use them. If not, fall back to config. Either way, validate every path against the allowed set.
-
----
-
-## Command injection
-
-If you spawn processes, **never pass user input through a shell**.
-
-```typescript
-// ❌ catastrophic
-exec(`git log ${branch}`);
-
-// ✅ array-args, no shell
-execFile("git", ["log", branch]);
-```
-
-If you're wrapping a CLI, build the full argv as an array. Validate each flag against an allowlist if the tool accepts flags at all.
-
----
-
-## Read-only by default
-
-Split read and write into separate tools. Most workflows only need read. A tool that's read-only can't be weaponized into data loss no matter what Claude is tricked into calling it with.
-
-```
-list_files   ← safe to call freely
-read_file    ← safe to call freely
-write_file   ← separate tool, separate scrutiny
-delete_file  ← consider not shipping this at all
-```
-
-Pair this with tool annotations — `readOnlyHint: true` on every read tool, `destructiveHint: true` on delete/overwrite tools. Hosts surface these in permission UI (auto-approve reads, confirm-dialog destructive). See `../build-mcp-server/references/tool-design.md`.
-
-If you ship write/delete, consider requiring explicit confirmation via elicitation (see `../build-mcp-server/references/elicitation.md`) or a confirmation widget (see `build-mcp-app`) so the user approves each destructive call.
-
----
-
-## Resource limits
-
-Claude will happily ask to read a 4GB log file. Cap everything:
-
-```typescript
-const MAX_BYTES = 1_000_000;
-const buf = await readFile(path);
-if (buf.length > MAX_BYTES) {
-  return {
-    content: [{
-      type: "text",
-      text: `File is ${buf.length} bytes — too large. Showing first ${MAX_BYTES}:\n\n`
-            + buf.subarray(0, MAX_BYTES).toString("utf8"),
-    }],
-  };
-}
-```
-
-Same for directory listings (cap entry count), search results (cap matches), and anything else unbounded.
-
----
-
-## Secrets
-
-- **Config secrets** (`sensitive: true` in manifest `user_config`): host stores in OS keychain, delivers via env var. Don't log them. Don't include them in tool results.
-- **Never store secrets in plaintext files.** If the host's keychain integration isn't enough, use `keytar` (Node) / `keyring` (Python) yourself.
-- **Tool results flow into the chat transcript.** Anything you return, the user (and any log export) can see. Redact before returning.
-
----
-
-## Checklist before shipping
-
-- [ ] Every path parameter goes through containment check
-- [ ] No `exec()` / `shell=True` — `execFile` / array-argv only
-- [ ] Write/delete split from read tools; `readOnlyHint`/`destructiveHint` annotations set
-- [ ] Size caps on file reads, listing lengths, search results
-- [ ] Secrets never logged or returned in tool results
-- [ ] Tested with adversarial inputs: `../../etc/passwd`, `; rm -rf ~`, 10GB file

package/resources/local/claude/plugins/marketplaces/claude-plugins-official/plugins/mcp-server-dev/skills/build-mcpb/references/manifest-schema.md

@@ -1,156 +0,0 @@
-# MCPB Manifest Schema (v0.4)
-
-Validated against `github.com/anthropics/mcpb/schemas/mcpb-manifest-v0.4.schema.json`. The schema uses `additionalProperties: false` — unknown keys are rejected. Add `"$schema"` to your manifest for editor validation.
-
----
-
-## Top-level fields
-
-| Field | Required | Description |
-|---|---|---|
-| `manifest_version` | ✅ | Schema version. Use `"0.4"`. |
-| `name` | ✅ | Package identifier (lowercase, hyphens). Must be unique. |
-| `version` | ✅ | Semver version of YOUR package. |
-| `description` | ✅ | One-line summary. Shown in marketplace. |
-| `author` | ✅ | `{name, email?, url?}` |
-| `server` | ✅ | Entry point and launch config. See below. |
-| `display_name` | | Human-friendly name. Falls back to `name`. |
-| `long_description` | | Markdown. Shown on detail page. |
-| `icon` / `icons` | | Path(s) to icon file(s) in the bundle. |
-| `homepage` / `repository` / `documentation` / `support` | | URLs. |
-| `license` | | SPDX identifier. |
-| `keywords` | | String array for search. |
-| `user_config` | | Install-time config fields. See below. |
-| `compatibility` | | Host/platform/runtime requirements. See below. |
-| `tools` / `prompts` | | Optional declarative list for marketplace display. Not enforced at runtime. |
-| `tools_generated` / `prompts_generated` | | `true` if tools/prompts are dynamic (can't list statically). |
-| `screenshots` | | Array of image paths. |
-| `localization` | | i18n bundles. |
-| `privacy_policies` | | URLs. |
-
----
-
-## `server` — launch configuration
-
-```json
-"server": {
-  "type": "node",
-  "entry_point": "server/index.js",
-  "mcp_config": {
-    "command": "node",
-    "args": ["${__dirname}/server/index.js"],
-    "env": {
-      "API_KEY": "${user_config.apiKey}",
-      "ROOT_DIR": "${user_config.rootDir}"
-    }
-  }
-}
-```
-
-| Field | Description |
-|---|---|
-| `type` | `"node"`, `"python"`, or `"binary"` |
-| `entry_point` | Relative path to main file. Informational. |
-| `mcp_config.command` | Executable to launch. |
-| `mcp_config.args` | Argv array. Use `${__dirname}` for bundle-relative paths. |
-| `mcp_config.env` | Environment variables. Use `${user_config.KEY}` to substitute user config. |
-
-**Substitution variables** (in `args` and `env` only):
-- `${__dirname}` — absolute path to the unpacked bundle directory
-- `${user_config.<key>}` — value the user entered at install time
-- `${HOME}` — user's home directory
-
-**There are no auto-prefixed env vars.** The env var names your server reads are exactly what you declare in `mcp_config.env`. If you write `"ROOT_DIR": "${user_config.rootDir}"`, your server reads `process.env.ROOT_DIR`.
-
----
-
-## `user_config` — install-time settings
-
-```json
-"user_config": {
-  "apiKey": {
-    "type": "string",
-    "title": "API Key",
-    "description": "Your service API key. Stored encrypted.",
-    "sensitive": true,
-    "required": true
-  },
-  "rootDir": {
-    "type": "directory",
-    "title": "Root directory",
-    "description": "Directory to expose to the server.",
-    "default": "${HOME}/Documents"
-  },
-  "maxResults": {
-    "type": "number",
-    "title": "Max results",
-    "description": "Maximum items returned per query.",
-    "default": 50,
-    "min": 1,
-    "max": 500
-  }
-}
-```
-
-| Field | Required | Description |
-|---|---|---|
-| `type` | ✅ | `"string"`, `"number"`, `"boolean"`, `"directory"`, `"file"` |
-| `title` | ✅ | Form label. |
-| `description` | ✅ | Help text under the input. |
-| `default` | | Pre-filled value. Supports `${HOME}`. |
-| `required` | | If `true`, install blocks until filled. |
-| `sensitive` | | If `true`, stored in OS keychain + masked in UI. **NOT `secret`** — that field doesn't exist. |
-| `multiple` | | If `true`, user can enter multiple values (array). |
-| `min` / `max` | | Numeric bounds (for `type: "number"`). |
-
-`directory` and `file` types render native OS pickers — prefer these over free-text paths for UX and validation.
-
----
-
-## `compatibility` — gate installs
-
-```json
-"compatibility": {
-  "claude_desktop": ">=1.0.0",
-  "platforms": ["darwin", "win32", "linux"],
-  "runtimes": { "node": ">=20" }
-}
-```
-
-| Field | Description |
-|---|---|
-| `claude_desktop` | Semver range. Install blocked if host is older. |
-| `platforms` | OS allowlist. Subset of `["darwin", "win32", "linux"]`. |
-| `runtimes` | Required runtime versions, e.g. `{"node": ">=20"}` or `{"python": ">=3.11"}`. |
-
----
-
-## Minimal valid manifest
-
-```json
-{
-  "$schema": "https://raw.githubusercontent.com/anthropics/mcpb/main/schemas/mcpb-manifest-v0.4.schema.json",
-  "manifest_version": "0.4",
-  "name": "hello",
-  "version": "0.1.0",
-  "description": "Minimal MCPB server.",
-  "author": { "name": "Your Name" },
-  "server": {
-    "type": "node",
-    "entry_point": "server/index.js",
-    "mcp_config": {
-      "command": "node",
-      "args": ["${__dirname}/server/index.js"]
-    }
-  }
-}
-```
-
----
-
-## What MCPB does NOT have
-
-- **No `permissions` block.** There is no manifest-level filesystem/network/process scoping. The server runs with full user privileges. Enforce boundaries in your tool handlers — see `local-security.md`.
-- **No auto env var prefix.** No `MCPB_CONFIG_*` convention. You wire config → env explicitly in `server.mcp_config.env`.
-- **No `entry` field.** It's `server` with `entry_point` inside.
-- **No `minHostVersion`.** It's `compatibility.claude_desktop`.

package/resources/local/claude/plugins/marketplaces/claude-plugins-official/plugins/php-lsp/LICENSE

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

package/resources/local/claude/plugins/marketplaces/claude-plugins-official/plugins/php-lsp/README.md

@@ -1,24 +0,0 @@
-# php-lsp
-
-PHP language server (Intelephense) for Claude Code, providing code intelligence and diagnostics.
-
-## Supported Extensions
-`.php`
-
-## Installation
-
-Install Intelephense globally via npm:
-
-```bash
-npm install -g intelephense
-```
-
-Or with yarn:
-
-```bash
-yarn global add intelephense
-```
-
-## More Information
-- [Intelephense Website](https://intelephense.com/)
-- [Intelephense on npm](https://www.npmjs.com/package/intelephense)

package/resources/local/claude/plugins/marketplaces/claude-plugins-official/plugins/playground/.claude-plugin/plugin.json

@@ -1,8 +0,0 @@
-{
-  "name": "playground",
-  "description": "Creates interactive HTML playgrounds — self-contained single-file explorers with visual controls, live preview, and prompt output with copy button",
-  "author": {
-    "name": "Anthropic",
-    "email": "support@anthropic.com"
-  }
-}