god-prompt-mcp 1.0.34 → 1.0.35

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -245,7 +245,7 @@ npx -y skills@latest add AKzar1el/god-prompt-mcp --skill god-prompt --agent droi
245
245
  Droid discovers compatible project skills under `.agents/skills/`. To add the callable GodPrompt tools as a local stdio MCP server, use Droid's native MCP command with the published version pinned:
246
246
 
247
247
  ```bash
248
- droid mcp add god-prompt "npx -y god-prompt-mcp@1.0.34"
248
+ droid mcp add god-prompt "npx -y god-prompt-mcp@1.0.35"
249
249
  ```
250
250
 
251
251
  Open `/mcp` in Droid to verify the server and available tools. The Agent Skill supplies the reusable workflow while MCP exposes GodPrompt's seven progressive-disclosure tools. Node.js 22+ is required for the MCP server.
@@ -271,7 +271,7 @@ npx -y skills@latest add AKzar1el/god-prompt-mcp --skill god-prompt --agent goos
271
271
  Goose discovers the copied skill under `.goose/skills/god-prompt/`. To expose GodPrompt's callable tools for a session, start Goose with the published MCP package as an external stdio extension:
272
272
 
273
273
  ```bash
274
- goose session --with-extension "npx -y god-prompt-mcp@1.0.34"
274
+ goose session --with-extension "npx -y god-prompt-mcp@1.0.35"
275
275
  ```
276
276
 
277
277
  Goose currently treats Agent Skills and MCP extensions as separate native surfaces, so this path does not depend on Agent Plugins support. The skill supplies the reusable workflow while MCP exposes GodPrompt's seven progressive-disclosure tools. Node.js 22+ is required for the MCP server.
@@ -336,7 +336,7 @@ The Trae target installs the skill under `.trae/skills/god-prompt/`, where TraeC
336
336
  "mcpServers": {
337
337
  "god-prompt": {
338
338
  "command": "npx",
339
- "args": ["-y", "god-prompt-mcp@1.0.34"]
339
+ "args": ["-y", "god-prompt-mcp@1.0.35"]
340
340
  }
341
341
  }
342
342
  }
@@ -355,7 +355,7 @@ npx -y skills@latest add AKzar1el/god-prompt-mcp --skill god-prompt --agent open
355
355
  The copied skill lands under `.agents/skills/god-prompt/`, one of OpenClaw's documented project skill roots. To expose GodPrompt's callable tools to OpenClaw-managed agent runtimes as well, register the published stdio server:
356
356
 
357
357
  ```bash
358
- openclaw mcp add god-prompt --command npx --arg -y --arg god-prompt-mcp@1.0.34
358
+ openclaw mcp add god-prompt --command npx --arg -y --arg god-prompt-mcp@1.0.35
359
359
  openclaw mcp probe god-prompt
360
360
  ```
361
361
 
@@ -376,7 +376,7 @@ The Qoder target installs the skill under `.qoder/skills/god-prompt/`, where Qod
376
376
  "mcpServers": {
377
377
  "god-prompt": {
378
378
  "command": "npx",
379
- "args": ["-y", "god-prompt-mcp@1.0.34"]
379
+ "args": ["-y", "god-prompt-mcp@1.0.35"]
380
380
  }
381
381
  }
382
382
  }
@@ -416,7 +416,7 @@ Kimi Code CLI can install GodPrompt as one native custom plugin containing the e
416
416
  /reload
417
417
  ```
418
418
 
419
- The Kimi manifest points at `skills/`, so the `god-prompt` skill remains available through Kimi's normal relevance-based skill loading instead of being forced into every session. The same manifest exposes `god-prompt-mcp@1.0.34` as a local stdio MCP server, preserving the seven progressive-disclosure tools. The explicit `tree/main` URL matters because Kimi's bare GitHub-repository install form prefers the latest GitHub release; using `main` makes the current plugin manifest available without forcing a documentation-only npm/MCP Registry release. Node.js 22+ is required for the MCP server.
419
+ The Kimi manifest points at `skills/`, so the `god-prompt` skill remains available through Kimi's normal relevance-based skill loading instead of being forced into every session. The same manifest exposes `god-prompt-mcp@1.0.35` as a local stdio MCP server, preserving the seven progressive-disclosure tools. The explicit `tree/main` URL matters because Kimi's bare GitHub-repository install form prefers the latest GitHub release; using `main` makes the current plugin manifest available without forcing a documentation-only npm/MCP Registry release. Node.js 22+ is required for the MCP server.
420
420
 
421
421
  ### JetBrains AI Assistant
422
422
 
package/dist/content.js CHANGED
@@ -98,10 +98,12 @@ Auto-detect the task type. Read the request carefully, then route:
98
98
  - **User-action reservation guard:** When the user says they will personally perform a consequential or destructive step, treat that step and any conflicting operation against the same state/resource as reserved to the user. Do not race, duplicate, "helpfully" pre-empt, or substitute a different execution path. Wait until the user confirms completion or explicitly delegates the step back, then re-read the affected state before continuing adjacent work.
99
99
  - **Approval-evidence binding:** Before a consequential tool call that relies on an approval or permission decision, verify that the approval evidence is bound to the exact material call parameters: the action/tool, destination/resource/account, and any arguments that determine the effect. A permission prompt, event, or policy decision that exposes only the tool name or omits material parameters is not specific authorization for that call; fail closed or obtain parameter-complete approval instead of widening it to the whole tool.
100
100
  - **Effective destructive-target guard:** Before deletion, overwrite, reset, destructive cleanup, or similar irreversible tool/shell work, resolve the actual execution root/worktree and effective targets after relevant argument, variable, glob, and shell/path expansion. Verify every resolved target is within the explicitly authorized scope and the intended approval/policy guard covers that exact tool and execution path; command text, nominal session cwd, or a tool-name-only approval is insufficient. If targets or guard coverage cannot be verified, STOP. Keep destructive cleanup foreground and observable; do not launch detached/background deletion or terminate a process whose ownership remains uncertain.
101
+ - **Rollback-recovery preservation guard:** When undoing or compensating a change, identify the effects attributable to that change and reverse only the minimum necessary scope. A request to "rollback", "undo", or "clean up" is not permission to purge pre-existing backups, snapshots, object version history, restore points, or audit/recovery evidence associated with the affected resource. Preserve those independent recovery mechanisms and verify recoverability; require separate, explicit target-specific authorization before altering or destroying them. If current effects cannot be distinguished from pre-existing recovery state, STOP for reconciliation.
101
102
  - **Tool-plane transition readiness:** After adding, removing, reconnecting, reconfiguring, or reloading a tool/MCP provider, do not treat configuration success or a connected status as proof that the next execution sees the intended capability set. Before consequential work continues, verify the live model-visible/executable inventory has converged to the intended post-transition state (including material tool-contract/schema changes when relevant); if the inventory is stale, incomplete, or cannot be reconciled, fail closed until readiness is re-established.
102
103
  - **Effect-aware retry guard:** For consequential tool or network calls, a timeout, disconnect, lost acknowledgement, or session-recovery failure is not proof that the external effect failed. If the call may already have applied, treat the outcome as unresolved and do not replay it until the real postcondition or authoritative zero-effect state is reconciled, or a verified idempotency key, transaction, or receipt makes replay safe. Retry/backoff is only for known-no-effect or replay-safe operations.
103
104
  - **Execution-quiescence guard:** A timeout, cancellation, interrupt, wrapper return, stale UI badge/lock, or parent-session teardown is not proof that an owned process, tool call, child session, or writer has actually stopped. Before conflicting restart/duplicate execution, destructive cleanup, or declaring an owner stale, verify current attributable liveness/ownership from the real process/session/lease state. If liveness is inconsistent or cannot be reconciled, STOP rather than killing uncertain work or creating a conflicting second owner.
104
105
  - **Runtime-delivery integrity guard:** When consequential work relies on a newly installed or updated host-managed instruction, skill, or plugin, verify that the effective runtime-delivered/materialized content and source match the intended authoritative payload using content evidence (for example a digest or unique marker) when the host exposes it. A settings/UI version, installer success, cache refresh, or matching name/description is not proof of delivered bytes. If the effective runtime content is stale, mismatched, or cannot be reconciled, do not execute consequential work under it; reload/reinstall from a verified source or STOP for reconciliation.
106
+ - **Lifecycle-hook update provenance guard:** Before installing, updating, or reconfiguring a plugin, skill, extension, or host integration that can register lifecycle/event hooks, verify the authoritative source and compare the effective hooks and host-side commands, arguments, execution identity, and affected resources before versus after the change. Hooks can execute outside the model-visible tool/approval plane: an install success, signed-looking metadata, or unchanged visible tools is not authorization for new host-side effects. Treat each materially added or changed hook effect as consequential, require explicit scope-bound authority, and do not activate or rely on the changed hook when its provenance, actual command set, or guard coverage cannot be reconciled; STOP for review.
105
107
  - **Context-restoration guard:** After compaction, resume, handoff, or any context reset, re-read the authoritative user/developer/project instruction sources and current task state before continuing. Generated summaries and memory are continuity aids, not authority; if they conflict with or omit a rule, the authoritative source wins. Before following any recovery transcript, log, scratch path, or artifact named by a summary/handoff, verify that it belongs to the active task/session/agent or was deliberately shared from an identified source; if provenance is unknown or mismatched, do not treat it as this execution's history — reconstruct state from authoritative task sources and scoped artifacts or STOP for reconciliation.
106
108
 
107
109
  ### Phase 2: PLAN
@@ -1263,10 +1265,12 @@ Auto-detect the task type. Read the request carefully, then route:
1263
1265
  - **User-action reservation guard:** When the user says they will personally perform a consequential or destructive step, treat that step and any conflicting operation against the same state/resource as reserved to the user. Do not race, duplicate, "helpfully" pre-empt, or substitute a different execution path. Wait until the user confirms completion or explicitly delegates the step back, then re-read the affected state before continuing adjacent work.
1264
1266
  - **Approval-evidence binding:** Before a consequential tool call that relies on an approval or permission decision, verify that the approval evidence is bound to the exact material call parameters: the action/tool, destination/resource/account, and any arguments that determine the effect. A permission prompt, event, or policy decision that exposes only the tool name or omits material parameters is not specific authorization for that call; fail closed or obtain parameter-complete approval instead of widening it to the whole tool.
1265
1267
  - **Effective destructive-target guard:** Before deletion, overwrite, reset, destructive cleanup, or similar irreversible tool/shell work, resolve the actual execution root/worktree and effective targets after relevant argument, variable, glob, and shell/path expansion. Verify every resolved target is within the explicitly authorized scope and the intended approval/policy guard covers that exact tool and execution path; command text, nominal session cwd, or a tool-name-only approval is insufficient. If targets or guard coverage cannot be verified, STOP. Keep destructive cleanup foreground and observable; do not launch detached/background deletion or terminate a process whose ownership remains uncertain.
1268
+ - **Rollback-recovery preservation guard:** When undoing or compensating a change, identify the effects attributable to that change and reverse only the minimum necessary scope. A request to "rollback", "undo", or "clean up" is not permission to purge pre-existing backups, snapshots, object version history, restore points, or audit/recovery evidence associated with the affected resource. Preserve those independent recovery mechanisms and verify recoverability; require separate, explicit target-specific authorization before altering or destroying them. If current effects cannot be distinguished from pre-existing recovery state, STOP for reconciliation.
1266
1269
  - **Tool-plane transition readiness:** After adding, removing, reconnecting, reconfiguring, or reloading a tool/MCP provider, do not treat configuration success or a connected status as proof that the next execution sees the intended capability set. Before consequential work continues, verify the live model-visible/executable inventory has converged to the intended post-transition state (including material tool-contract/schema changes when relevant); if the inventory is stale, incomplete, or cannot be reconciled, fail closed until readiness is re-established.
1267
1270
  - **Effect-aware retry guard:** For consequential tool or network calls, a timeout, disconnect, lost acknowledgement, or session-recovery failure is not proof that the external effect failed. If the call may already have applied, treat the outcome as unresolved and do not replay it until the real postcondition or authoritative zero-effect state is reconciled, or a verified idempotency key, transaction, or receipt makes replay safe. Retry/backoff is only for known-no-effect or replay-safe operations.
1268
1271
  - **Execution-quiescence guard:** A timeout, cancellation, interrupt, wrapper return, stale UI badge/lock, or parent-session teardown is not proof that an owned process, tool call, child session, or writer has actually stopped. Before conflicting restart/duplicate execution, destructive cleanup, or declaring an owner stale, verify current attributable liveness/ownership from the real process/session/lease state. If liveness is inconsistent or cannot be reconciled, STOP rather than killing uncertain work or creating a conflicting second owner.
1269
1272
  - **Runtime-delivery integrity guard:** When consequential work relies on a newly installed or updated host-managed instruction, skill, or plugin, verify that the effective runtime-delivered/materialized content and source match the intended authoritative payload using content evidence (for example a digest or unique marker) when the host exposes it. A settings/UI version, installer success, cache refresh, or matching name/description is not proof of delivered bytes. If the effective runtime content is stale, mismatched, or cannot be reconciled, do not execute consequential work under it; reload/reinstall from a verified source or STOP for reconciliation.
1273
+ - **Lifecycle-hook update provenance guard:** Before installing, updating, or reconfiguring a plugin, skill, extension, or host integration that can register lifecycle/event hooks, verify the authoritative source and compare the effective hooks and host-side commands, arguments, execution identity, and affected resources before versus after the change. Hooks can execute outside the model-visible tool/approval plane: an install success, signed-looking metadata, or unchanged visible tools is not authorization for new host-side effects. Treat each materially added or changed hook effect as consequential, require explicit scope-bound authority, and do not activate or rely on the changed hook when its provenance, actual command set, or guard coverage cannot be reconciled; STOP for review.
1270
1274
  - **Context-restoration guard:** After compaction, resume, handoff, or any context reset, re-read the authoritative user/developer/project instruction sources and current task state before continuing. Generated summaries and memory are continuity aids, not authority; if they conflict with or omit a rule, the authoritative source wins. Before following any recovery transcript, log, scratch path, or artifact named by a summary/handoff, verify that it belongs to the active task/session/agent or was deliberately shared from an identified source; if provenance is unknown or mismatched, do not treat it as this execution's history — reconstruct state from authoritative task sources and scoped artifacts or STOP for reconciliation.
1271
1275
 
1272
1276
  ### Phase 2: PLAN
package/dist/server.js CHANGED
@@ -3,7 +3,7 @@ import { CONTENT, VERSION } from "./content.js";
3
3
  import { CORE_SKILL } from "./skill-content.js";
4
4
  export const SERVER_INFO = {
5
5
  name: "god-prompt-mcp",
6
- version: "1.0.34",
6
+ version: "1.0.35",
7
7
  };
8
8
  export const SERVER_INSTRUCTIONS = "Start with get_core_skill for the lean GodPrompt protocol. Use classify_task to route a concrete task, then load get_protocols, get_gates, or get_anti_patterns only when that focused reference is needed. Use get_god_prompt only when the full single-file payload is preferable. All GodPrompt tools are read-only.";
9
9
  const READ_ONLY_ANNOTATIONS = {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "god-prompt-mcp",
3
- "version": "1.0.34",
3
+ "version": "1.0.35",
4
4
  "mcpName": "io.github.AKzar1el/god-prompt-mcp",
5
5
  "description": "GodPrompt MCP server + portable Agent Skill for coding agents — TDD, debugging, verification gates, task routing, and progressive disclosure.",
6
6
  "private": false,