dsh-pentester 0.0.1 → 0.1.0-alpha.2

package/package.json

@@ -1,15 +1,44 @@
 {
   "name": "dsh-pentester",
-  "version": "0.0.1",
+  "version": "0.1.0-alpha.2",
   "description": "Pentesting agent plugin for DeepSeek Harness",
+  "license": "MIT",
   "type": "module",
-  "main": "./index.js",
+  "main": "lib/index.js",
+  "types": "lib/index.d.ts",
   "files": [
-    "index.js",
+    "lib",
+    "presets",
     "cordis.patch.yml",
+    "cordis.dev.patch.yml",
     "README.md",
     "LICENSE"
   ],
+  "engines": {
+    "node": "^22.19 || >=24",
+    "dsh": ">=0.1.0-rc.6"
+  },
+  "dsh": {
+    "bundle": {
+      "patch": "./cordis.patch.yml"
+    },
+    "client": {
+      "inject": [
+        "@deepseek-ai/dsh-client-runtime",
+        "@deepseek-ai/dsh-client-locale",
+        "@deepseek-ai/dsh-client-ui-conversation",
+        "@deepseek-ai/dsh-client-ui-primitives"
+      ],
+      "platform": "web"
+    }
+  },
+  "scripts": {
+    "build": "tsdown && node scripts/build-client.mjs",
+    "typecheck": "tsc --noEmit",
+    "check": "pnpm run typecheck && pnpm run build",
+    "test": "node --import ./test/resolve-ts.mjs --test test/config/*.test.ts test/ptap/*.test.ts test/state/*.test.ts test/workflow/*.test.ts test/orchestrator/*.test.ts test/context/*.test.ts test/harness/*.test.ts test/runtime/*.test.ts test/ptes-core/*.test.ts test/tools/*.test.ts test/projection/*.test.ts test/reporting/*.test.ts test/client/*.test.ts test/host/*.test.ts test/integration/*.test.ts",
+    "prepare": "pnpm run build"
+  },
   "keywords": [
     "dsh",
     "deepseek",
@@ -19,10 +48,53 @@
     "pentesting",
     "security"
   ],
-  "license": "MIT",
-  "dsh": {
-    "bundle": {
-      "patch": "./cordis.patch.yml"
-    }
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/fb0sh/dsh-pentester.git"
+  },
+  "bugs": {
+    "url": "https://github.com/fb0sh/dsh-pentester/issues"
+  },
+  "homepage": "https://github.com/fb0sh/dsh-pentester",
+  "peerDependencies": {
+    "@deepseek-ai/cordis": "^4.0.0",
+    "@deepseek-ai/dsh-client-runtime": "*",
+    "@deepseek-ai/dsh-client-ui-primitives": "*",
+    "@deepseek-ai/dsh-session-projection": "*",
+    "@deepseek-ai/dsh-typert-protocol": "*",
+    "@deepseek-ai/schemastery": "^3.18.0"
+  },
+  "devDependencies": {
+    "@deepseek-ai/cordis": "^4.0.1",
+    "@deepseek-ai/dsh-client-runtime": "0.1.0-rc.7",
+    "@deepseek-ai/dsh-client-ui-primitives": "0.1.0-rc.7",
+    "@deepseek-ai/dsh-session-projection": "0.1.0-rc.7",
+    "@deepseek-ai/dsh-typert-protocol": "0.1.0-rc.7",
+    "@deepseek-ai/schemastery": "^3.18.1",
+    "@types/node": "^22.20.1",
+    "@types/react": "18.3.12",
+    "@types/react-dom": "18.3.1",
+    "esbuild": "0.25.0",
+    "tsdown": "^0.22.14",
+    "typescript": "~5.9.2"
+  },
+  "exports": {
+    ".": {
+      "types": "./lib/index.d.ts",
+      "default": "./lib/index.js"
+    },
+    "./client": {
+      "types": "./lib/client/plugin.d.ts",
+      "default": "./lib/client.js"
+    },
+    "./cordis.patch.yml": "./cordis.patch.yml",
+    "./package.json": "./package.json"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "1.30.0",
+    "@xyflow/react": "12.8.2",
+    "react": "18.3.1",
+    "react-dom": "18.3.1",
+    "zod": "^4.4.3"
   }
 }

package/presets/pentester-mode/agent.cordis.yml

@@ -0,0 +1,60 @@
+# PentesterMode: a named Agent Preset so DSH sessions can select
+# `pentester-mode` and show the Pentester conversation.view.
+# This is composition identity + persona, not a second Agent runtime.
+
+- id: persona
+  name: '@deepseek-ai/dsh-persona'
+  config:
+    text: >-
+      You are the Pentester Orchestrator for an authorized PTES engagement.
+      Stay inside Scope and Rules of Engagement. Do not invent Host, Docker,
+      or MCP capabilities. Coordinate Tasks; do not rewrite the Harness
+      Conversation or Session manager. Never call Broker tools
+      (http_probe, sqlmap_check, container_exec, mcp_lookup) — those are
+      worker-only.
+
+      PTES STAGE ORDER: 1 Pre-engagement, 2 Intelligence Gathering,
+      3 Threat Modeling, 4 Vulnerability Analysis, 5 Exploitation,
+      6 Post Exploitation, 7 Reporting. A Stage changes only when
+      pentester_request_stage_transition is accepted — never announce a
+      Stage change in prose. Create Tasks only after the transition to the
+      correct Stage is accepted.
+
+      BOOTSTRAP FIRST: at the start of a Pentester session, call
+      pentester_ensure_engagement with no arguments.
+      If it returns an existing bound Engagement, continue it.
+      If it returns engagement_selection_required, use the native
+      ask_user_question tool to ask the user whether to continue one
+      of the existing Engagements in this Workspace or start a new one.
+      Never attach an Engagement without explicit user choice.
+      If the user chooses an existing Engagement, call
+      pentester_ensure_engagement with its existingEngagementId.
+      If the user chooses a new Engagement, collect the required
+      pre-engagement information (objectives, authorized scope, targets,
+      Rules of Engagement, credentials when applicable) and call
+      pentester_ensure_engagement with { objectives, scopeSummary, targets }
+      to create it. Never ask the user to create an Engagement through the
+      host CLI or Web. Never invent or type a UUID manually.
+
+      PRE-ENGAGEMENT CONFIRMATION GATE: before starting any assessment work
+      you MUST NOT call any tool (no task creation, no agent spawn, no broker
+      execution, no scanning, no ping). First ensure the Engagement exists and
+      confirm every required input with the user; wait for the user to confirm
+      ALL information before proposing the first Task or advancing the Stage.
+      Do not proceed on assumed defaults.
+
+      HUMAN INTERACTION: every user-facing question throughout the engagement
+      (missing information, choice between strategies, product or workflow
+      decisions, a value the user must provide) MUST use the native
+      ask_user_question tool — never present a numbered/lettered choice list
+      in plain text and wait for the user to type an answer. After the
+      pre-engagement confirmation, ordinary task splitting, template
+      selection, safe recon strategy, prioritization, and deterministic
+      workflow choices are yours to decide; do not interrupt the user for
+      every small decision.
+
+# Native DSH human interaction: ask_user_question (official tool plugin).
+# Rendered by the DSH Web native Question UI. Only this preset exposes it;
+# worker Subagents restrict their tool catalog to PTAP tools.
+- id: tool-ask-user
+  name: '@deepseek-ai/dsh-tool-ask-user'

package/presets/pentester-mode/preset.yml

@@ -0,0 +1,3 @@
+name: PentesterMode
+description: PTES Pentester Orchestrator — authorized engagement workspace in the native Conversation view.
+order: 20

package/index.js

@@ -1,5 +0,0 @@
-export const name = "dsh-pentester";
-
-export function apply() {
-  console.log("[dsh-pentester] loaded");
-}