@f5-sales-demo/xcsh 19.51.2

package/src/prompts/tools/replace.md

@@ -0,0 +1,36 @@
+Performs string replacements in files with fuzzy whitespace matching.
+
+<instruction>
+- You **MUST** use the smallest edit that uniquely identifies the change
+- If `old_text` not unique, you **MUST** expand to include more context or use `all: true` to replace all occurrences
+- Fuzzy matching handles minor whitespace/indentation differences automatically
+- You **SHOULD** prefer editing existing files over creating new ones
+</instruction>
+
+<output>
+Returns success/failure status. On success, file modified in place with replacement applied. On failure (e.g., `old_text` not found or matches multiple locations without `all: true`), returns error describing issue.
+</output>
+
+<critical>
+- You **MUST** read the file at least once in the conversation before editing. Tool errors if you attempt edit without reading file first.
+</critical>
+
+<bash-alternatives>
+Replace for content-addressed changes—you identify \_what* to change by its text.
+
+For position-addressed or pattern-addressed changes, bash more efficient:
+
+|Operation|Command|
+|---|---|
+|Append to file|`cat >> file <<'EOF'`…`EOF`|
+|Prepend to file|`{ cat - file; } <<'EOF' > tmp && mv tmp file`|
+|Delete lines N-M|`sed -i 'N,Md' file`|
+|Insert after line N|`sed -i 'Na\text' file`|
+|Regex replace|`sd 'pattern' 'replacement' file`|
+|Bulk replace across files|`sd 'pattern' 'replacement' **/*.ts`|
+|Copy lines N-M to another file|`sed -n 'N,Mp' src >> dest`|
+|Move lines N-M to another file|`sed -n 'N,Mp' src >> dest && sed -i 'N,Md' src`|
+
+Use Replace when _content itself_ identifies location.
+Use bash when _position_ or _pattern_ identifies what to change.
+</bash-alternatives>

package/src/prompts/tools/resolve.md

@@ -0,0 +1,8 @@
+Resolves a pending preview action by either applying or discarding it.
+- `action` is required:
+  - `"apply"` persists the pending changes.
+  - `"discard"` rejects the pending changes.
+- `reason` is required and must explain why you chose to apply or discard.
+
+This tool is only valid when a pending action exists (typically after a preview step).
+If no pending action exists, the call fails with an error.

package/src/prompts/tools/rewind.md

@@ -0,0 +1,13 @@
+Ends an active checkpoint and rewinds context back to that checkpoint, replacing intermediate exploration with your report.
+
+Use this immediately after investigative work started with `checkpoint`.
+
+Requirements:
+- `report` is **REQUIRED** and must be concise, factual, and actionable.
+- Include key findings, decisions, and any unresolved risks.
+- Do not include raw scratch logs unless essential.
+- You **MUST** call this before yielding if a checkpoint is active.
+
+Behavior:
+- If no checkpoint is active, this tool errors.
+- On success, the session rewinds and keeps your report as retained context.

package/src/prompts/tools/search-tool-bm25.md

@@ -0,0 +1,34 @@
+Search hidden MCP tool metadata when MCP tool discovery is enabled.
+
+Use this tool to discover MCP tools that are loaded into the session but not exposed to the model by default.
+
+{{#if hasDiscoverableMCPServers}}Discoverable MCP servers in this session: {{#list discoverableMCPServerSummaries join=", "}}{{this}}{{/list}}.{{/if}}
+{{#if discoverableMCPToolCount}}Total discoverable MCP tools loaded: {{discoverableMCPToolCount}}.{{/if}}
+Input:
+- `query` — required natural-language or keyword query
+- `limit` — optional maximum number of tools to return and activate (default `8`)
+
+Behavior:
+- Searches hidden MCP tool metadata using BM25-style relevance ranking
+- Matches against MCP tool name, server name, description, and input schema keys
+- Activates the top matching MCP tools for the rest of the current session
+- Repeated searches add to the active MCP tool set; they do not remove earlier selections
+- Newly activated MCP tools become available before the next model call in the same overall turn
+
+Notes:
+- If you are unsure, start with `limit` between 5 and 10 to see a broader set of tools.
+- `query` is matched against MCP tool metadata fields:
+  - `name`
+  - `label`
+  - `server_name`
+  - `mcp_tool_name`
+  - `description`
+  - input schema property keys (`schema_keys`)
+
+This is not repository search, file search, or code search. Use it only for MCP tool discovery.
+
+Returns JSON with:
+- `query`
+- `activated_tools` — MCP tools activated by this search call
+- `match_count` — number of ranked matches returned by the search
+- `total_tools`

package/src/prompts/tools/ssh.md

@@ -0,0 +1,44 @@
+Runs commands on remote hosts.
+
+<instruction>
+You **MUST** build commands from the reference below
+</instruction>
+
+<commands>
+**linux/bash, linux/zsh, macos/bash, macos/zsh** — Unix-like:
+- Files: `ls`, `cat`, `head`, `tail`, `grep`, `find`
+- System: `ps`, `top`, `df`, `uname` (all), `free` (Linux only)
+- Navigation: `cd`, `pwd`
+**windows/bash, windows/sh** — Windows Unix layer (WSL, Cygwin, Git Bash):
+- Files/System/Navigation: same as Unix-like above, minus `free`
+**windows/powershell** — PowerShell:
+- Files: `Get-ChildItem`, `Get-Content`, `Select-String`
+- System: `Get-Process`, `Get-ComputerInfo`
+- Navigation: `Set-Location`, `Get-Location`
+**windows/cmd** — Command Prompt:
+- Files: `dir`, `type`, `findstr`, `where`
+- System: `tasklist`, `systeminfo`
+- Navigation: `cd`, `echo %CD%`
+</commands>
+
+<critical>
+You **MUST** verify the shell type from "Available hosts" and use matching commands.
+</critical>
+
+<example name="linux">
+Task: List /home/user files on "server1"
+Host: server1 (10.0.0.1) | linux/bash
+Command: `ls -la /home/user`
+</example>
+
+<example name="windows-cmd">
+Task: Show running processes on "winbox"
+Host: winbox (192.168.1.5) | windows/cmd
+Command: `tasklist /v`
+</example>
+
+<example name="macos">
+Task: Get system info on "macbook"
+Host: macbook (10.0.0.20) | macos/zsh
+Command: `uname -a && sw_vers`
+</example>

package/src/prompts/tools/task-summary.md

@@ -0,0 +1,28 @@
+<task-summary>
+<header>{{successCount}}/{{totalCount}} succeeded{{#if hasCancelledNote}} ({{cancelledCount}} cancelled){{/if}} [{{duration}}]</header>
+
+{{#each summaries}}
+<agent id="{{id}}" agent="{{agent}}">
+<status>{{status}}</status>
+{{#if meta}}<meta lines="{{meta.lineCount}}" size="{{meta.charSize}}" />{{/if}}
+{{#if truncated}}
+<preview full-path="agent://{{id}}">
+{{preview}}
+</preview>
+{{else}}
+<result>
+{{preview}}
+</result>
+{{/if}}
+</agent>
+{{#unless @last}}
+---
+{{/unless}}
+{{/each}}
+
+{{#if mergeSummary}}
+<merge-summary>
+{{mergeSummary}}
+</merge-summary>
+{{/if}}
+</task-summary>

package/src/prompts/tools/task.md

@@ -0,0 +1,131 @@
+Launches subagents to parallelize workflows.
+
+{{#if asyncEnabled}}
+- Use `read jobs://` to inspect state; `read jobs://<job_id>` for detail.
+- Use the `poll` tool to wait until completion. You **MUST NOT** poll `read jobs://` in a loop.
+{{/if}}
+
+Subagents lack your conversation history. Every decision, file content, and user requirement they need **MUST** be explicit in `context` or `assignment`.
+
+<parameters>
+- `agent`: Agent type for all tasks.
+  - `.id`: CamelCase, max 32 chars
+  - `.description`: UI display only — subagent never sees it
+  - `.assignment`: Complete self-contained instructions. One-liners PROHIBITED; missing acceptance criteria = too vague.
+- `context`: Shared background prepended to every assignment. Session-specific info only.
+- `schema`: JSON-encoded JTD schema for expected output. Format lives here — **MUST NOT** be duplicated in assignments.
+- `tasks`: Tasks to execute in parallel.
+- `isolated`: Run in isolated environment; returns patches. Use when tasks edit overlapping files.
+</parameters>
+
+<critical>
+- **MUST NOT** duplicate shared constraints across assignments — put them in `context` once.
+- **MUST NOT** tell tasks to run project-wide build/test/lint. Parallel agents share the working tree; each task edits, stops. Caller verifies after all complete.
+- For large payloads (traces, JSON blobs), write to `local://<path>` and pass the path in context.
+- Prefer `task` agents that investigate **and** edit in one pass. Only launch a dedicated read-only discovery step when the affected files are genuinely unknown and cannot be inferred from the task description.
+</critical>
+
+<scope>
+Each task: **at most 3–5 files**. Globs in file paths, "update all", or package-wide scope = too broad. Enumerate files explicitly and fan out to a cluster of agents.
+</scope>
+
+<parallelization>
+**Test:** Can task B produce correct output without seeing A's result? Yes → parallel. No → sequential.
+
+|Sequential first|Then|Reason|
+|---|---|---|
+|Types/interfaces|Consumers|Need contract|
+|API exports|Callers|Need signatures|
+|Core module|Dependents|Import dependency|
+|Schema/migration|App logic|Schema dependency|
+**Safe to parallelize:** independent modules, isolated file-scoped refactors, tests for existing code.
+</parallelization>
+
+<templates>
+**context:**
+```
+## Goal         ← one sentence: what the batch accomplishes
+## Non-goals    ← what tasks must not touch
+## Constraints  ← MUST/MUST NOT rules and session decisions
+## API Contract ← exact types/signatures if tasks share an interface (omit if N/A)
+## Acceptance   ← definition of done; build/lint runs AFTER all tasks complete
+```
+**assignment:**
+```
+## Target       ← exact file paths; named symbols; explicit non-goals
+## Change       ← step-by-step what to add/remove/rename; patterns/APIs to use
+## Edge Cases   ← tricky inputs; existing behavior that must survive
+## Acceptance   ← observable result proving the task is done; no project-wide commands
+```
+</templates>
+
+<checklist>
+Before invoking:
+- `context` contains only session-specific info
+- Every `assignment` follows the template; no one-liners; edge cases covered
+- Tasks are truly parallel — you can articulate why none depends on another's output
+- File paths are explicit; no globs
+- `schema` is set if you expect structured output
+</checklist>
+
+<example label="Rename exported symbol + update all call sites">
+Two tasks with non-overlapping file sets. Neither depends on the other's edits.
+
+<context>
+## Goal
+Rename `parseConfig` → `loadConfig` in `src/config/parser.ts` and all callers.
+## Non-goals
+Do not change function behavior, signature, or tests — rename only.
+## Acceptance (global)
+Caller runs `bun check:ts` after both tasks complete. Tasks must NOT run it.
+</context>
+<tasks>
+  <task name="RenameExport">
+    <description>Rename the export in parser.ts</description>
+    <assignment>
+## Target
+- File: `src/config/parser.ts`
+- Symbol: exported function `parseConfig`
+- Non-goals: do not touch callers or tests
+
+## Change
+- Rename `parseConfig` → `loadConfig` (declaration + any JSDoc referencing it)
+- If `src/config/index.ts` re-exports `parseConfig`, update that re-export too
+
+## Edge Cases
+- If the function is overloaded, rename all overload signatures
+- Internal helpers named `_parseConfigValue` or similar: leave untouched — different symbols
+- Do not add a backwards-compat alias
+
+## Acceptance
+- `src/config/parser.ts` exports `loadConfig`; `parseConfig` no longer appears as a top-level export in that file
+    </assignment>
+  </task>
+  <task name="UpdateCallers">
+    <description>Update import and call sites in consuming modules</description>
+    <assignment>
+## Target
+- Files: `src/cli/init.ts`, `src/server/bootstrap.ts`, `src/worker/index.ts`
+- Non-goals: do not touch `src/config/parser.ts` or `src/config/index.ts` — handled by sibling task
+
+## Change
+- In each file: replace `import { parseConfig }` → `import { loadConfig }` from its config path
+- Replace every call site `parseConfig(` → `loadConfig(`
+
+## Edge Cases
+- If a file spreads the import (`import * as cfg from "…"`) and calls `cfg.parseConfig(…)`, update the property access too
+- String literals containing "parseConfig" (log messages, comments) are documentation — leave them
+- If any file re-exports `parseConfig` to an external package boundary, keep the old name via `export { loadConfig as parseConfig }` and add a `// TODO: remove after next major` comment
+
+## Acceptance
+- No bare reference to `parseConfig` (as identifier, not string) remains in the three target files
+    </assignment>
+  </task>
+</tasks>
+</example>
+
+{{#list agents join="\n"}}
+### Agent: {{name}}
+**Tools:** {{default (join tools ", ") "All"}}
+{{description}}
+{{/list}}

package/src/prompts/tools/todo-write.md

@@ -0,0 +1,89 @@
+Manages a phased task list. Submit an `ops` array — each op mutates state incrementally.
+**Primary op: `update`.** Use it to mark tasks `in_progress` or `completed`. Only reach for other ops when the structure itself needs to change.
+
+<critical>
+You **MUST** call this tool twice per task:
+1. Before beginning — `{op: "update", id: "task-N", status: "in_progress"}`
+2. Immediately after finishing — `{op: "update", id: "task-N", status: "completed"}`
+
+You **MUST** keep exactly one task `in_progress` at all times. Mark `completed` immediately — no batching.
+</critical>
+
+<conditions>
+Create a todo list when:
+1. Task requires 3+ distinct steps
+2. User explicitly requests one
+3. User provides a set of tasks to complete
+4. New instructions arrive mid-task — capture before proceeding
+</conditions>
+
+<protocol>
+## Operations
+
+|op|When to use|
+|---|---|
+|`update`|Mark a task in_progress / completed / abandoned, or edit content/notes|
+|`replace`|Initial setup, or full restructure when the plan changes significantly|
+|`add_phase`|Add a new phase of work discovered mid-task|
+|`add_task`|Add a task to an existing phase|
+|`remove_task`|Remove a task that is no longer relevant|
+
+## Statuses
+
+|Status|Meaning|
+|---|---|
+|`pending`|Not started|
+|`in_progress`|Currently working — exactly one at a time|
+|`completed`|Fully done|
+|`abandoned`|Dropped intentionally|
+
+## Rules
+- You **MUST** mark `in_progress` **before** starting work, not after
+- You **MUST** mark `completed` **immediately** — never defer
+- You **MUST** keep exactly **one** task `in_progress`
+- You **MUST** complete phases in order — do not mark later tasks `completed` while earlier ones are `pending`
+- On blockers: keep `in_progress`, add a new task describing the blocker
+- Multiple ops can be batched in one call (e.g., complete current + start next)
+</protocol>
+
+## Task Anatomy
+- `content`: Short label (5-10 words). What is being done, not how.
+- `details`: File paths, implementation steps, edge cases. Shown only when task is active.
+- `notes`: Runtime observations added during execution.
+
+<avoid>
+- Single-step tasks — act directly
+- Conversational or informational requests
+- Tasks completable in under 3 trivial steps
+</avoid>
+
+<example name="start-task">
+Mark task-2 in_progress before beginning work:
+ops: [{op: "update", id: "task-2", status: "in_progress"}]
+</example>
+
+<example name="complete-and-advance">
+Finish task-2 and start task-3 in one call:
+ops: [
+  {op: "update", id: "task-2", status: "completed"},
+  {op: "update", id: "task-3", status: "in_progress"}
+]
+</example>
+
+<example name="add_task">
+Add a follow-up task with implementation specifics in `details`:
+ops: [{op: "add_task", phase: "Implementation", after: "task-2", task: {content: "Handle retries", details: "Update retry.ts to cap exponential backoff and preserve AbortSignal handling", status: "pending"}}]
+</example>
+
+<example name="initial-setup">
+Replace is for setup only. Prefer add_phase / add_task for incremental additions.
+ops: [{op: "replace", phases: [
+  {name: "Investigation", tasks: [{content: "Read source"}, {content: "Map callsites"}]},
+  {name: "Implementation", tasks: [{content: "Apply fix", details: "Update parser.ts to handle edge case in line 42"}, {content: "Run tests"}]}
+]}]
+</example>
+
+<example name="skip">
+User: "What does this function do?" / "Add a comment" / "Run npm install"
+→ Do it directly. No list needed.
+</example>

package/src/prompts/tools/vim.md

@@ -0,0 +1,98 @@
+Vim-style `edit` mode. The tool name stays `edit`; every call requires `file`, and the buffer loads automatically on first use.
+- `{"file": "path"}` - view file
+- `{"file": "path", "steps": [{"kbd": ["…"], "insert": "…"}]}` - edit file
+
+**Multi-location edits: always edit highest line number first (bottom-up).** Each insert shifts lines below it.
+
+## steps vs kbd vs insert
+
+`steps` = ordered editing steps. Each step runs `kbd`, then optionally types `insert`.
+`kbd` = Vim commands only (`dd`, `G`, `o`, `cc`, `gg`, etc.).
+`insert` = raw text content to type into the buffer.
+`o`/`O` already create a new line — do not start `insert` with `\n`. A trailing `\n` in `insert` adds an extra blank line.
+
+Never put text content in `kbd`. Only Vim keystrokes go there.
+- BAD: `{"steps": [{"kbd": ["1Gohello world<Esc>"]}]}`
+- BAD: `{"steps": [{"kbd": ["1Go", "hello world"]}]}`
+- BAD: `{"steps": [{"kbd": ["1Ao"], "insert": "text"}]}`
+- GOOD: `{"steps": [{"kbd": ["1Go"], "insert": "hello world"}]}`
+
+If a step uses `insert`, the last `kbd` entry in that step must leave INSERT mode active (`o`, `O`, `i`, `a`, `A`, `cc`, `C`, `s`, `S`).
+
+Each non-final `kbd` entry inside a step must end in NORMAL mode (add `<Esc>`).
+
+Between steps, the tool auto-exits INSERT mode.
+
+Whitespace in `kbd` is literal. Do not use spaces as separators between keys; `ggdGi` is one sequence, not `ggdG i`.
+
+Common mistake: `Ni` means "insert N copies", NOT "insert at line N". To insert at line N, use `NGo` (below) or `NGO` (above).
+## Editing patterns
+
+`NGo` = new line BELOW line N. `NGO` = new line ABOVE line N.
+
+Insert new line after line 3:
+```json
+{"file": "f.py", "steps": [{"kbd": ["3Go"], "insert": "    new line here"}]}
+```
+
+Insert new line before line 3:
+```json
+{"file": "f.py", "steps": [{"kbd": ["3GO"], "insert": "    new line here"}]}
+```
+
+Replace line N:
+```json
+{"file": "f.py", "steps": [{"kbd": ["5Gcc"], "insert": "    replacement content"}]}
+```
+
+Replace entire file. `ggdGi` = go to top, delete all, enter INSERT. Use that exact sequence when rewriting the whole file:
+```json
+{"file": "f.py", "steps": [{"kbd": ["ggdGi"], "insert": "entire new file content"}]}
+```
+
+Multi-location edit — edit **highest line number first** (bottom-up) so inserts don't shift later targets:
+```json
+{"file": "f.py", "steps": [
+  {"kbd": ["8Go"], "insert": "    print(result)"},
+  {"kbd": ["3Go"], "insert": "def helper(x):\n    return x + 1"}
+]}
+```
+Each `o`/`O` insert adds lines, shifting everything below. Bottom-up order keeps all line numbers valid. Use `\n` within `insert` for multi-line content.
+
+Navigation or search step without insert:
+```json
+{"file": "f.py", "steps": [{"kbd": ["/pattern<CR>"]}]}
+```
+
+Find and replace:
+```json
+{"file": "f.py", "steps": [{"kbd": [":%s/old/new/g<CR>"]}]}
+```
+
+Delete line range:
+```json
+{"file": "f.py", "steps": [{"kbd": [":3,5d<CR>"]}]}
+```
+Ex commands always start with `:` and end with `<CR>`. `3,5d` without `:` is NOT an ex command — it is interpreted as normal-mode keystrokes and will fail.
+
+## Undo mistakes
+- `{"file": "f.py", "steps": [{"kbd": ["u"]}]}` - undo last change
+- `{"file": "f.py", "steps": [{"kbd": ["3u"]}]}` - undo last 3 changes
+
+`:e!` reloads from disk. Warning: because non-paused calls auto-save, `:e!` reloads your last saved state, not the original file. Use `u` to undo instead. If stuck, use `ggdGi` with the full desired file content.
+
+## Session persistence
+
+The edit buffer in vim mode persists across tool calls. Cursor position, undo history, and file state are maintained until you close the buffer. Auto-save happens once after all steps in a non-paused call complete.
+
+## Supported
+
+Keys: `<Esc>` `<CR>` `<BS>` `<Tab>` `<C-d>` `<C-u>` `<C-r>` `<C-w>` `<C-o>`
+Motions: `h j k l <Space> w b e 0 $ ^ + - _ gg G { } f F t T % H M L ; ,` with counts
+Operators: `d c y p` with motions and text objects (`iw aw ip ap i" a" i( a( i{ a{`)
+Insert: `i a o O I A cc C s S R` - these all enter INSERT mode; do not add another `i` after them
+Visual: `v V` with `d y c > < ~ r u U p P o J`
+Other: `.` repeat, `u`/`<C-r>` undo/redo, `/pattern<CR>` search, `n N * #`, `gv` `gJ` `gU` `gu` `ZZ` `ZQ`
+Ex: `:w` `:q` `:wq` `:e` `:e!` `:N` `:s///` `:%s///` `:N,Md` `:%d` `:N,Mt N` `:sort` `:j` `:j!` `:g/pattern/d` `:v/pattern/d`
+Addresses: absolute line numbers, `.`, `$`, and `+N`/`-N` relative offsets, including ranges like `:.,$d` and `:.+2,$g/pattern/d`
+More ex: `:up` `:N,My` `:put` `:put!` `:N,Mco $` `:N,Mm $`

package/src/prompts/tools/web-search.md

@@ -0,0 +1,10 @@
+Searches the web for up-to-date information beyond Claude's knowledge cutoff.
+
+<instruction>
+- You **SHOULD** prefer primary sources (papers, official docs) and corroborate key claims with multiple sources
+- You **MUST** include links for cited sources in the final response
+</instruction>
+
+<caution>
+Searches are performed automatically within a single API call—no pagination or follow-up requests needed.
+</caution>

package/src/prompts/tools/write.md

@@ -0,0 +1,14 @@
+Creates or overwrites file at specified path.
+
+<conditions>
+- Creating new files explicitly required by task
+- Replacing entire file contents when editing would be more complex
+- Supports `.tar`, `.tar.gz`, `.tgz`, and `.zip` archive entries via `archive.ext:path/inside/archive`
+- Supports SQLite row operations via `db.sqlite:table` (insert), `db.sqlite:table:key` (update with JSON content, delete with empty content)
+</conditions>
+
+<critical>
+- You **SHOULD** use Edit tool for modifying existing files (more precise, preserves formatting)
+- You **MUST NOT** create documentation files (*.md, README) unless explicitly requested
+- You **MUST NOT** use emojis unless requested
+</critical>