@modootoday/pmcp 0.13.1 → 0.14.0

package/plugins/tsup-8/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "tsup-8",
+  "version": "8.0.0",
+  "description": "Build and pack typed ESM/CJS libraries, then verify imports from a consumer project.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/tsup-8/skills/tsup/SKILL.md

@@ -0,0 +1,97 @@
+---
+name: tsup
+description: Build and diagnose TypeScript library packages using tsup 8, including ESM/CJS exports, declaration files, dependency externalization, and packed consumer verification. Use for an existing tsup build rather than application bundler or migration selection.
+---
+
+# tsup 8 library builds
+
+Use the project's installed tsup version and package manager. The fixture targets
+tsup 8.5.1; its execution evidence belongs to the generated catalog, not an
+assumption that every application configuration has been tested.
+
+[The upstream repository](https://github.com/egoist/tsup) states that tsup is no
+longer actively maintained and recommends considering tsdown. Keep an existing
+tsup build working when that is the task. Evaluate a migration separately rather
+than changing the bundler as part of an ordinary packaging fix.
+
+## Choose the package contract before the build
+
+Inspect package.json, the existing exports map, tsconfig, runtime target, entry
+points and consumers. Emit CJS only if consumers need require. Keep Node built-ins
+and peer dependencies external. tsup normally externalizes dependencies and peer
+dependencies from package.json; use explicit external entries when the packaging
+contract requires them. Bundling a dependency deliberately requires checking its
+license, runtime assumptions and duplicate-instance behavior.
+
+The following configuration keeps output paths explicit in a type: module package:
+
+```ts
+import { defineConfig } from "tsup";
+
+export default defineConfig({
+  entry: ["src/index.ts"],
+  format: ["esm", "cjs"],
+  target: "node22",
+  platform: "node",
+  dts: true,
+  clean: true,
+  external: ["node:crypto"],
+  outExtension({ format }) {
+    return { js: format === "esm" ? ".js" : ".cjs" };
+  },
+});
+```
+
+Keep the export map synchronized with emitted files, including the declarations
+that TypeScript associates with each module format:
+
+```json
+{
+  "type": "module",
+  "files": ["dist"],
+  "exports": {
+    ".": {
+      "import": { "types": "./dist/index.d.ts", "default": "./dist/index.js" },
+      "require": {
+        "types": "./dist/index.d.cts",
+        "default": "./dist/index.cjs"
+      }
+    }
+  }
+}
+```
+
+Check actual declaration filenames after the build. Do not invent .d.cts files
+from an export-map example if the installed configuration emitted something else.
+Declare public runtime dependencies and peers in the shipped manifest; an
+external import does not make an undeclared dependency available to consumers.
+
+## Diagnose failures at the right boundary
+
+- JavaScript success with declaration failure: run the project's TypeScript
+  check and inspect exported types, module resolution and external type imports.
+  Bundling JavaScript does not establish that declarations are valid.
+- Runtime module errors: compare type, exports, extensions and the actual import
+  or require consumer. Do not rewrite an ESM-only dependency into a require call.
+- Missing assets or entry points: inspect npm pack output and the files allowlist.
+  A workspace import from src can conceal an incomplete published package.
+- A React or other singleton peer bundled into the output: confirm externalization
+  and compare consumer dependency resolution before adding deduplication aliases.
+
+## Verify the distributable
+
+Build once, inspect npm pack --dry-run --json, then create an actual tarball when
+the task changes exports, declarations or packaging. Test an isolated consumer
+against that tarball, without workspace aliases or source-file imports.
+
+Check the ESM import and CJS require branches that the package promises. Run a
+NodeNext TypeScript consumer for both .mts and .cts when both branches are
+published. Browser libraries also need their browser consumer environment;
+the Node fixture does not prove browser or native-addon compatibility.
+
+## Sources
+
+- [tsup configuration, formats and dependencies](https://tsup.egoist.dev/)
+- [tsup maintenance status and source](https://github.com/egoist/tsup)
+- [Node.js package exports](https://nodejs.org/api/packages.html#conditional-exports)
+- [TypeScript compiler options for libraries](https://www.typescriptlang.org/docs/handbook/modules/guides/choosing-compiler-options.html)

package/plugins/tsx-4/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "tsx-4",
+  "version": "4.0.0",
+  "description": "Use tsx v4 as a Node-compatible TypeScript loader, or use its documented ESM/CJS Developer APIs from a plain script. Covers v4 changes, dynamic loading, scoped registration, and the boundary between the API and the tsx CLI.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/tsx-4/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/plugins/tsx-4/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/tsx-4/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "tsx-4", "version": "4.0.0" }

package/plugins/tsx-4/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "tsx-4",
+  "version": "4.0.0",
+  "description": "Use tsx v4 as a Node-compatible TypeScript loader, or use its documented ESM/CJS Developer APIs from a plain script. Covers v4 changes, dynamic loading, scoped registration, and the boundary between the API and the tsx CLI.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/tsx-4/skills/tsx/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: tsx
+description: Use tsx v4 as a Node-compatible TypeScript loader, or use its documented ESM/CJS Developer APIs from a plain script. Covers v4 changes, dynamic loading, scoped registration, and the boundary between the API and the tsx CLI.
+---
+
+Verified against tsx@4.23.13 on 2026-09-07. 2 of 2 examples executed.
+
+# tsx
+
+## Scope
+
+This skill targets `tsx` `^4.0.0`. It covers the documented package entry points and Developer APIs, plus the CLI features shown by the research. `tsx` is a drop-in `node` replacement that adds TypeScript support, CommonJS/ESM interoperability, `tsconfig.json` paths, and esbuild-based transformation. It does not perform type checking.
+
+The runnable examples below are standalone Bun scripts. The package-entry, `tsImport`, and enhanced-`require` smoke tests were not retained because they failed when run standalone under the supplied Bun environment; see [Standalone-runtime limitation](#standalone-runtime-limitation).
+
+## v4 corrections
+
+- Use the `TSX_` environment-variable prefix. `ESBK_` is the v3-era prefix and is not the v4 prefix.
+- v4 supports Node.js LTS versions 18 and newer. Do not target Node.js versions below 18.
+- v4 added resolver support for `.tsx` and `.jsx`.
+- CommonJS import specifiers may contain queries.
+- Transformation warnings are emitted through stderr.
+
+## CLI usage
+
+Install it as a development dependency with `npm install -D tsx`, then run a TypeScript file with `tsx file.ts`. The general command shape is:
+
+`tsx [tsx flags] ./file.ts [flags & arguments for file.ts]`
+
+A package script can use `tsx ./file.ts`, and `npx tsx ./script.ts` also works without a local installation.
+
+The equivalent Node integration is `node --import tsx ./file.ts`.
+
+## Package entry points
+
+The package entry point automatically registers TypeScript loading for subsequent imports:
+
+```ts
+import 'tsx'
+
+const loaded = await import('./file.ts')
+```
+
+For CommonJS-only mode, use `require('tsx/cjs')`. For module-only mode, use `import 'tsx/esm'`.
+
+The package entry point is a loader setup, not a value-oriented API. Use it when the surrounding runtime can perform the subsequent TypeScript import. The standalone smoke test from the earlier draft failed under the supplied Bun execution environment with a missing `./cjs/index.cjs` module, so this skill does not claim that smoke test is portable to that environment.
+
+## Dynamic ESM loading: `tsx/esm/api`
+
+`tsx/esm/api` exports named `tsImport`. It dynamically imports a TypeScript module, with the second argument supplying import context:
+
+```ts
+import { tsImport } from 'tsx/esm/api'
+
+const loaded = await tsImport('./file.ts', import.meta.url)
+```
+
+The options form accepts `parentURL` and can select a custom tsconfig:
+
+```ts
+const loaded = await tsImport('./file.ts', {
+  parentURL: import.meta.url,
+  tsconfig: './custom-tsconfig.json'
+})
+```
+
+The documented options also include `tsconfig: false` and an `onImport` callback receiving the imported file path.
+
+Do not use a built-in module as a portability smoke test for this API. The earlier standalone example calling `tsImport('node:path', import.meta.url)` failed under the supplied Bun environment because the generated `tsx://...` module could not be resolved. The research does not establish a standalone Bun-compatible substitute.
+
+## Enhanced CommonJS loading: `tsx/cjs/api`
+
+`tsx/cjs/api` exports a named enhanced `require` function. Its documented usage supplies the request and parent path:
+
+```ts
+import { require } from 'tsx/cjs/api'
+
+const loaded = require('./file.ts', import.meta.url)
+```
+
+The function also exposes `.resolve` and `.cache`:
+
+```ts
+const filepath = require.resolve('./file.ts', import.meta.url)
+```
+
+The earlier standalone example using `node:path` failed under the supplied Bun environment while invoking the enhanced loader. It is therefore not presented as a runnable standalone example. The documented API remains the relevant shape for a compatible Node/CommonJS integration.
+
+## Scoped CJS registration
+
+`tsx/cjs/api` exports `register`. It returns an `unregister` cleanup function, or a scoped API containing `require` and `unregister`:
+
+```ts
+const tsx = require('tsx/cjs/api')
+const unregister = tsx.register()
+const loaded = require('./file.ts')
+unregister()
+```
+
+Use the cleanup function when the registration is no longer needed.
+
+```ts pmcp-example
+import { register } from 'tsx/cjs/api'
+import assert from 'node:assert/strict'
+
+const unregister = register()
+
+assert.equal(typeof unregister, 'function')
+unregister()
+```
+
+## Scoped ESM registration
+
+`tsx/esm/api` also exports `register`. It returns an `unregister` cleanup function, or a scoped API containing `import` and `unregister`:
+
+```ts
+import { register } from 'tsx/esm/api'
+
+const unregister = register()
+await import('./file.ts')
+unregister()
+```
+
+```ts pmcp-example
+import { register } from 'tsx/esm/api'
+import assert from 'node:assert/strict'
+
+const unregister = register()
+
+assert.equal(typeof unregister, 'function')
+unregister()
+```
+
+## CLI-only features
+
+These features are exercised by the `tsx` command itself rather than by the Developer API:
+
+- Watch mode: `tsx watch ./file.ts`
+- Watch includes: `--include ./other-dep.txt` and `--include "./other-deps/*"`
+- Watch exclusions: `--exclude "./data/**/*"`
+- Disable watch-screen clearing with `--clear-screen=false`
+- The TypeScript REPL, entered by running `tsx` with no script
+- Node's enhanced test runner, invoked with `tsx --test`
+
+Watch mode reruns when dependencies change. The Developer API does not provide watch mode or the REPL. `describe`, `it`, and `expect` are not available in a directly executed script; test files use the tool's test-runner integration instead.
+
+## Standalone-runtime limitation
+
+In the supplied standalone Bun execution, these documented loading operations did not produce runnable examples:
+
+- importing the package entry point failed with a missing `./cjs/index.cjs` module;
+- `tsImport` failed while resolving its generated `tsx://...` module;
+- enhanced `require` failed while loading the built-in-module smoke test.
+
+Those failures are runtime-specific observations from the required standalone execution, not evidence that the documented Node integration shapes should be changed. Registration itself was independently runnable, so those examples are retained.
+
+## Does not cover
+
+This skill does not cover the full CLI flag set, watch-mode dependency semantics beyond the documented include/exclude options, REPL behavior, `tsx --test` test discovery, TypeScript compiler type checking, undocumented loader internals, Bun-specific compatibility beyond the observed standalone failures, or configuration details not shown in the supplied research.

package/plugins/type-fest-5/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "type-fest-5",
+  "version": "5.0.0",
+  "description": "Use type-fest v5.0.0 as a strict, type-only utility package. Covers v5 module/configuration requirements, the documented Except and Tagged APIs, and migration traps from v4.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/type-fest-5/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/plugins/type-fest-5/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/type-fest-5/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "type-fest-5", "version": "5.0.0" }

package/plugins/type-fest-5/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "type-fest-5",
+  "version": "5.0.0",
+  "description": "Use type-fest v5.0.0 as a strict, type-only utility package. Covers v5 module/configuration requirements, the documented Except and Tagged APIs, and migration traps from v4.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}