one-code-extension 0.4.0 → 0.5.0

package/extensions/skill/invoke.ts

@@ -1,18 +1,18 @@
 /**
  * User-invoked skill commands (pure). pi registers each skill as a `/skill:<name>`
  * slash command and, on invocation, expands it into a `<skill>` block that it
- * submits as a *user message* — so loading a skill shows up in the transcript as
- * a new user turn. One Code intercepts that command in the `input` hook and
- * re-delivers the same block as a hidden message instead (see index.ts), so the
- * model receives byte-identical content but nothing renders.
+ * submits as a *user message*. One Code intercepts that command (and its own
+ * bare `/<name>` and typed `/<plugin>:<skill>` forms) and delivers the skill
+ * the way Claude Code does: a hidden message holding the command breadcrumb
+ * and the skill's text, so nothing renders and no `skill` call is needed.
+ * A model's `skill` call gets Claude Code's "Launching skill" result with the
+ * same text beside it (see index.ts).
  *
- * These helpers mirror pi's own `_expandSkillCommand`/`formatSkillInvocation`
- * exactly (same `/skill:` prefix, same block template) so the model sees the same
- * bytes it would have without the interception — only the display changes.
+ * pi's own `<skill>` block still reaches a session through pi's native
+ * expansion on older pi (steer/followUp skip the `input` hook there), which
+ * is why the off-skill redaction below still matches it.
  */
 
-import { dirname } from "node:path";
-
 const SKILL_PREFIX = "/skill:";
 
 /** Parse a `/skill:<name> [args]` command; undefined if it is not one. */
@@ -45,23 +45,121 @@ export function resolveSkill<T extends { name: string }>(all: T[], wanted: strin
 }
 
 /**
- * Rebuild the exact `<skill>` block pi's `/skill:` expansion produces. `body` is
- * the SKILL.md with frontmatter already stripped and trimmed; `filePath` is the
- * skill file (its directory is the base for relative references, as pi does).
+ * Claude Code's breadcrumb for a typed slash command, the first text block of
+ * the message a typed skill becomes. Its arguments ride `<command-args>` only
+ * when there are some.
+ */
+export function commandBreadcrumb(name: string, args: string): string {
+	return `<command-message>${name}</command-message>\n<command-name>/${name}</command-name>${args ? `\n<command-args>${args}</command-args>` : ""}\n`;
+}
+
+// commandBreadcrumb's shape at the start of a message; the arguments may span lines.
+const BREADCRUMB = /^<command-message>[^<\n]*<\/command-message>\n<command-name>(\/[^<\n]*)<\/command-name>(?:\n<command-args>([\s\S]*?)<\/command-args>)?\n/;
+
+/**
+ * What a user message that opens with commandBreadcrumb shows in the
+ * transcript: the command as typed, `/name args`. Claude Code shows a prompt
+ * command (a skill, `/init`, `/doctor`) by its command line and keeps the
+ * expanded text out of the transcript. `undefined` for any other message.
+ */
+export function commandDisplayLine(text: string): string | undefined {
+	const match = BREADCRUMB.exec(text);
+	if (!match) return undefined;
+	return match[2] ? `${match[1]} ${match[2]}` : match[1];
+}
+
+/**
+ * Claude Code's argument substitution in a skill's text: `$ARGUMENTS`,
+ * `$ARGUMENTS[n]` and `$n` (both counted from 0) take the arguments, and a
+ * backslash keeps a `$` literal. When nothing was substituted, the arguments
+ * follow the text on an `ARGUMENTS:` line.
+ */
+export function substituteSkillArguments(text: string, args: string): string {
+	if (!args.trim()) return text;
+	const parts = args.trim().split(/\s+/);
+	let used = false;
+	// One pass, so an argument holding `$0` is never substituted again.
+	const out = text.replace(/\\\$(?=\d|ARGUMENTS)|\$ARGUMENTS\[(\d+)\]|\$ARGUMENTS|\$(\d+)(?!\w)/g, (match, listed?: string, positional?: string) => {
+		if (match.startsWith("\\")) return "$";
+		if (match === "$ARGUMENTS") {
+			used = true;
+			return args;
+		}
+		const part = parts[Number(listed ?? positional)];
+		if (part === undefined) return match;
+		used = true;
+		return part;
+	});
+	return used ? out : `${out}\n\nARGUMENTS: ${args}`;
+}
+
+/**
+ * The text a skill hands the model, as Claude Code builds it: the skill's
+ * folder first (`Base directory for this skill: …`, so relative `references/`
+ * and `scripts/` resolve), then the body with its arguments. A skill that
+ * ships inside One Code, like Claude Code's own, names no folder.
+ */
+export function skillPromptText(body: string, args: string, baseDir: string | undefined): string {
+	const text = substituteSkillArguments(body, args);
+	return baseDir ? `Base directory for this skill: ${baseDir}\n\n${text}` : text;
+}
+
+/**
+ * The message a typed skill command becomes, as Claude Code sends it: the
+ * breadcrumb, then the skill's text, each ending in a newline. Arguments a
+ * generated body already carries are not passed again.
  */
-export function buildSkillBlock(skill: { name: string; filePath: string }, body: string, args: string): string {
-	const block = `<skill name="${skill.name}" location="${skill.filePath}">
-References are relative to ${dirname(skill.filePath)}.
+export function typedSkillContent(name: string, typedArgs: string, promptText: string): [string, string] {
+	return [commandBreadcrumb(name, typedArgs), promptText.endsWith("\n") ? promptText : `${promptText}\n`];
+}
 
-${body}
-</skill>`;
-	return args ? `${block}\n\n${args}` : block;
+/**
+ * A prompt command (`/init`, `/doctor`, a plugin command) as one user message,
+ * in a typed skill's exact bytes: Claude Code sends every prompt command led by
+ * its breadcrumb, and the transcript shows it as its command line
+ * (commandDisplayLine).
+ */
+export function promptCommandText(name: string, args: string, prompt: string): string {
+	return typedSkillContent(name, args, prompt).join("\n");
+}
+
+/** Claude Code's result for a model's skill call; the skill's text follows it as a second block. */
+export const launchingSkill = (name: string): string => `Launching skill: ${name}`;
+
+/**
+ * The lines that open and close a skill tool result when the model called a
+ * skill that takes arguments without passing any. A skill's text is its
+ * instructions, not a manual: a weak model "checking the interface" of
+ * `/loop` got the no-argument body, which starts an autonomous loop. A mild
+ * opening line lost to that body's "The user invoked /loop with no prompt"
+ * on DeepSeek V4.1 Flash; telling it to stop and check, plus a closing
+ * reminder, turned it around. Only the model's tool calls get this; a user's
+ * bare `/<name>` is deliberate.
+ */
+export function missingArgumentsNote(argumentHint: string): { before: string; after: string } {
+	return {
+		before: `Stop and check before following this. This skill takes arguments (${argumentHint}) and this call passed none, so what follows is its no-argument mode, written as if the user asked for the skill with nothing after it. If the user's request names any of those arguments, do not follow the instructions below: call the skill again with them in \`args\`.`,
+		after: "Reminder: those were the no-argument instructions. If the user's request included arguments, call the skill again with them in `args` instead of following them.",
+	};
 }
 
 /** Fast pre-check before the regex walk; also the marker `redactOffSkillText` scans for. */
 const SKILL_BLOCK_START = '<skill name="';
 const SKILL_BLOCK_RE = /<skill name="([^"]+)"[^>]*>[\s\S]*?<\/skill>/g;
 
+/**
+ * The hidden message a `/skill:` command is delivered as. `details.input` is
+ * the text the user typed, so an extension that saw that text at `input` (the
+ * hooks extension's UserPromptSubmit context) can find the message that
+ * replaced it.
+ */
+export const SKILL_INVOCATION_TYPE = "one-code:skill-invocation";
+export interface SkillInvocationDetails {
+	skill: string;
+	args: string;
+	input?: string;
+}
+
 export const offSkillNotice = (name: string): string =>
 	`[Skill "${name}" is turned off — its instructions were removed. The user can re-enable it from /skills or /plugins.]`;
 
@@ -184,3 +282,15 @@ export function skillCommandCandidates<T extends { name: string; source: string
 	}
 	return out;
 }
+
+/**
+ * The `/` suggestions without pi's `/skill:<name>` entry for a skill that also
+ * has its bare `/<name>` command, so each skill is listed once, as in Claude
+ * Code. Kept when the user is typing `/skill:` themselves, and for a skill
+ * whose bare name was skipped (a collision), where `/skill:` is its only form.
+ * Typed `/skill:<name>` still runs either way: this only trims the list.
+ */
+export function withoutDuplicateSkillCommands<T extends { value: string }>(items: T[], prefix: string, bareSkills: ReadonlySet<string>): T[] {
+	if (!prefix.startsWith("/") || prefix.startsWith("/skill:")) return items;
+	return items.filter((item) => !(item.value.startsWith("skill:") && bareSkills.has(item.value.slice("skill:".length))));
+}

package/extensions/skill/listing.ts

@@ -2,20 +2,144 @@
  * The model-facing skills listing (pure). The state decides visibility: "on"
  * carries name + description, "name-only" just the name (saving context
  * tokens), "user-only"/"off" are hidden so the model won't auto-trigger them.
- * The description goes in whole, newlines included, the way Claude Code lists
- * it: a skill written with a YAML block description puts its "Use when…"
- * trigger on the later lines, and a first-line-only listing dropped exactly
- * the sentence that tells the model when to reach for the skill.
+ * A skill whose frontmatter sets `disable-model-invocation: true` is hidden
+ * whatever its state: only the user may start it, as in Claude Code.
+ *
+ * Each line is built the way Claude Code builds it: the description, then
+ * " - " and the `when_to_use` frontmatter when there is one, clipped at 1,536
+ * characters (1,535 and an ellipsis). The description keeps its newlines: a
+ * skill written with a YAML block description puts its "Use when…" trigger on
+ * the later lines, and a first-line-only listing dropped exactly the sentence
+ * that tells the model when to reach for the skill.
+ *
+ * The whole listing has a budget, 1% of the context window in characters
+ * (`SLASH_COMMAND_TOOL_CHAR_BUDGET` replaces it). Over budget, a bundled skill
+ * and a name-only one keep their lines; the others keep theirs by usage rank
+ * while the budget lasts and are listed by name after that.
  */
 
 import { type SkillState, skillListingVisibility } from "../lib/skill-overrides.ts";
+import type { UsageEntry } from "../lib/usage-tracker.ts";
 
-export function skillListingText(skills: ReadonlyArray<{ name: string; description?: string; state: SkillState }>): string {
-	const lines = skills.flatMap((skill) => {
+/** Claude Code's per-entry cap (its `skillListingMaxDescChars` default). */
+export const SKILL_DESCRIPTION_CAP = 1536;
+/** The listing's share of the context window, at 4 characters per token, 200K tokens when the window is unknown. */
+const BUDGET_FRACTION = 0.01;
+const CHARS_PER_TOKEN = 4;
+const DEFAULT_CONTEXT_WINDOW = 200_000;
+
+export interface ListedSkill {
+	name: string;
+	description?: string;
+	/** The `when_to_use` frontmatter, appended after " - ". */
+	whenToUse?: string;
+	state: SkillState;
+	disableModelInvocation?: boolean;
+	/** Ships inside One Code: keeps its line over budget, as Claude Code's bundled skills do. */
+	bundled?: boolean;
+	/** The usage score that ranks the line over budget (`usageScore`). */
+	usage?: number;
+}
+
+/** The text after `- <name>: `, clipped as Claude Code clips it. */
+export function listingDescription(skill: Pick<ListedSkill, "description" | "whenToUse">): string {
+	const description = skill.description?.trim() ?? "";
+	const whenToUse = skill.whenToUse?.trim();
+	const text = whenToUse ? `${description} - ${whenToUse}` : description;
+	return text.length > SKILL_DESCRIPTION_CAP ? `${text.slice(0, SKILL_DESCRIPTION_CAP - 1)}…` : text;
+}
+
+/** The listing's character budget for a context window (tokens). */
+export function skillListingBudget(contextWindow: number | undefined, env: NodeJS.ProcessEnv = process.env): number {
+	const fromEnv = Number.parseInt(env.SLASH_COMMAND_TOOL_CHAR_BUDGET ?? "", 10);
+	if (fromEnv > 0) return fromEnv;
+	const window = contextWindow && contextWindow > 0 ? contextWindow : DEFAULT_CONTEXT_WINDOW;
+	return Math.max(1, Math.floor(window * CHARS_PER_TOKEN * BUDGET_FRACTION));
+}
+
+/** Claude Code's ranking score: uses, halved every week since the last one, never below a tenth. */
+export function usageScore(entry: UsageEntry | undefined, now: Date = new Date()): number {
+	if (!entry) return 0;
+	const last = Date.parse(entry.lastUsedAt);
+	if (Number.isNaN(last)) return 0;
+	const days = (now.getTime() - last) / 86_400_000;
+	return entry.count * Math.max(0.5 ** (days / 7), 0.1);
+}
+
+export function skillListingText(skills: ReadonlyArray<ListedSkill>, budget = Number.POSITIVE_INFINITY): string {
+	const listed = skills.flatMap((skill) => {
+		if (skill.disableModelInvocation) return [];
 		const visibility = skillListingVisibility(skill.state);
 		if (visibility === "hidden") return [];
-		if (visibility === "name") return [`- ${skill.name}`];
-		return [`- ${skill.name}${skill.description?.trim() ? `: ${skill.description.trim()}` : ""}`];
+		const short = `- ${skill.name}`;
+		if (visibility === "name") return [{ skill, short, full: short }];
+		const text = listingDescription(skill);
+		return [{ skill, short, full: text ? `${short}: ${text}` : short }];
 	});
-	return lines.length === 0 ? "(no skills available)" : lines.join("\n");
+	if (listed.length === 0) return "(no skills available)";
+	const separators = listed.length - 1;
+	const whole = listed.reduce((sum, line) => sum + line.full.length, 0) + separators;
+	if (whole <= budget) return listed.map((line) => line.full).join("\n");
+
+	// A name-only line's full form is its short form, so it needs no place in `kept`.
+	const kept = new Set(listed.filter((line) => line.skill.bundled));
+	const ranked = listed.filter((line) => !kept.has(line));
+	let left = budget - (listed.reduce((sum, line) => sum + (kept.has(line) ? line.full.length : line.short.length), 0) + separators);
+	// A stable sort: equal scores keep the listing's order.
+	for (const line of [...ranked].sort((a, b) => (b.skill.usage ?? 0) - (a.skill.usage ?? 0))) {
+		const extra = line.full.length - line.short.length;
+		if (extra > left) continue;
+		kept.add(line);
+		left -= extra;
+	}
+	return listed.map((line) => (kept.has(line) ? line.full : line.short)).join("\n");
+}
+
+/**
+ * The skills listing for a session without the skill tool: each skill's file,
+ * to read with `reader`. The same states as the tool's listing: user-only and
+ * off skills stay hidden, a name-only skill shows no description. Undefined
+ * when nothing is listable.
+ */
+export function readableSkillListing(
+	skills: ReadonlyArray<ListedSkill & { path?: string; kind?: string }>,
+	reader: string,
+): string | undefined {
+	const lines = skills
+		.filter((skill) => !skill.kind && !skill.disableModelInvocation && skill.path && skillListingVisibility(skill.state) !== "hidden")
+		.map((skill) => {
+			const text = skillListingVisibility(skill.state) === "full" ? listingDescription(skill) : "";
+			return `- ${skill.name}${text ? `: ${text}` : ""} (${skill.path})`;
+		});
+	if (lines.length === 0) return undefined;
+	return `The following skills provide specialized instructions for specific tasks. Read a skill's file with ${reader} when the task matches its description:\n\n${lines.join("\n")}`;
+}
+
+/**
+ * Claude Code's reading of a boolean frontmatter flag such as
+ * `disable-model-invocation`: `true` or the string `"true"`, nothing else.
+ */
+export function frontmatterFlag(value: unknown): boolean {
+	return value === true || value === "true";
+}
+
+/**
+ * pi's own skills section in a rendered system prompt (`formatSkillsForPrompt`):
+ * pi 1.0 renders it as a `<skills>` section, older pi (the 0.84 floor)
+ * appends it after a blank line. Both start with this sentence.
+ */
+const PI_SKILLS_LEAD = "The following skills provide specialized instructions for specific tasks.";
+const PI_SKILLS_SECTION = /\n*<skills>\nThe following skills provide specialized instructions for specific tasks\.[\s\S]*?<\/available_skills>\n<\/skills>/;
+const PI_SKILLS_APPENDED = /\n\nThe following skills provide specialized instructions for specific tasks\.[\s\S]*?<\/available_skills>/;
+
+/**
+ * `prompt` without pi's own skills section ("Use the read tool to load a
+ * skill's file …" and its `<available_skills>` list), unchanged when it has
+ * none. A session with the skill tool lists skills for that tool instead, and
+ * a child agent's prompt (pi adds the section to an agent's own prompt)
+ * otherwise told it both "read the file" and "call the skill tool first".
+ */
+export function withoutPiSkillsBlock(prompt: string): string {
+	if (!prompt.includes(PI_SKILLS_LEAD)) return prompt;
+	return prompt.replace(PI_SKILLS_SECTION, "").replace(PI_SKILLS_APPENDED, "");
 }

package/extensions/skill/panel/keys.ts

@@ -1,41 +1,40 @@
 /**
- * Raw-byte key decoding for the /skills panel (pure).
+ * Key decoding for the /skills panel (pure), named through
+ * `lib/key-input.ts` so every terminal encoding of a key decodes alike.
  *
- * Same control-byte map as the /plugins panel; kept local so the skill
+ * Same key map as the /plugins panel; kept local so the skill
  * extension carries no dependency on another extension's internals. Printable
  * input is a `text` intent the state layer routes (into the search box, or as a
  * single-letter action when search is inactive). Skill names never contain
  * spaces, so Space is always the cycle action, never typed.
  */
 
+import { keyId, keyText } from "../../lib/key-input.ts";
+
 export type SkillsKey =
 	| { kind: "up" | "down" | "enter" | "space" | "back" | "backspace" | "close" }
 	| { kind: "text"; text: string };
 
 export function decodeSkillsKey(data: string): SkillsKey | undefined {
-	switch (data) {
-		case "\x1b[A":
-		case "\x1bOA":
+	switch (keyId(data)) {
+		case "up":
 			return { kind: "up" };
-		case "\x1b[B":
-		case "\x1bOB":
+		case "down":
 			return { kind: "down" };
-		case "\r":
-		case "\n":
+		case "enter":
 			return { kind: "enter" };
-		case " ":
+		case "space":
 			return { kind: "space" };
-		case "\x1b":
+		case "escape":
 			return { kind: "back" };
-		case "\x7f":
-		case "\b":
+		case "backspace":
+		case "ctrl+backspace":
 			return { kind: "backspace" };
-		case "\x03":
+		case "ctrl+c":
 			return { kind: "close" };
 		default:
 			break;
 	}
-	if (data.startsWith("\x1b")) return undefined;
-	const text = [...data].filter((ch) => ch >= " " && ch !== "\x7f").join("");
+	const text = keyText(data);
 	return text ? { kind: "text", text } : undefined;
 }

package/extensions/skill/panel/render.ts

@@ -9,7 +9,7 @@
  * under-measure and risk pi's overwide-line crash.
  */
 
-import { cutPlainText, padPlainText, panelTopRule, searchBoxLines, visibleWidth } from "../../lib/tui-render.ts";
+import { cutPlainText, padPlainText, panelTopRule, searchBoxLines, visibleWidth, wrapHints } from "../../lib/tui-render.ts";
 import type { SkillState } from "../../lib/skill-overrides.ts";
 import { clampSkillsCursor, type SkillsPanelState, type SkillsRow, visibleRows } from "./state.ts";
 
@@ -64,7 +64,10 @@ export function renderSkillsPanel(input: SkillsRenderInput, paint: SkillsPaint):
 	const out: string[] = [panelTopRule(paint.fg, width)];
 	out.push(` ${paint.bold("Skills")}`);
 	const sortNote = state.sort === "state" ? "sorted by state" : "sorted by name";
-	out.push(paint.fg("dim", cutPlainText(` ${rows.length} skill${rows.length === 1 ? "" : "s"} · ${sortNote} · enter/space to cycle, / to search, t to sort, Esc to close`, width - 1)));
+	// Wraps at the separators on a narrow terminal, so no key is cut off; the
+	// list budget below is taken after it.
+	const hints = `${rows.length} skill${rows.length === 1 ? "" : "s"} · ${sortNote} · enter/space to cycle · / to search · t to sort · Esc to close`;
+	for (const line of wrapHints(hints, Math.max(1, width - 2))) out.push(paint.fg("dim", ` ${line}`));
 	out.push("");
 	out.push(...searchBoxLines(state.search, "Search skills…", paint.fg, width));
 	out.push("");

package/extensions/skill/panel/state.ts

@@ -14,7 +14,8 @@ export interface SkillsRow {
 	/** Override-store key, `<scope>:<name>`. */
 	key: string;
 	name: string;
-	scope: SkillScope;
+	/** Shown in the row: where the skill comes from; "bundled" is One Code's own catalog. */
+	scope: SkillScope | "bundled";
 	tokens: number;
 	/** Current state; for locked (plugin) rows this is the effective on/off. */
 	state: SkillState;
@@ -63,6 +64,16 @@ export function clampSkillsCursor(state: SkillsPanelState, visible: SkillsRow[])
 	state.cursor = Math.max(0, Math.min(state.cursor, visible.length - 1));
 }
 
+/**
+ * Keep the cursor on the skill `key` after the list reordered (a sort toggle,
+ * or a state change under the state sort), so the next key acts on the skill
+ * the user was looking at, not the one that slid into its row.
+ */
+export function followRow(state: SkillsPanelState, visible: SkillsRow[], key: string): void {
+	const index = visible.findIndex((row) => row.key === key);
+	if (index >= 0) state.cursor = index;
+}
+
 /**
  * Fold a key into the state, returning an effect the wiring must act on. The
  * caller passes the already-filtered/sorted rows so "the selected row" matches

package/extensions/subagents/agent-args.ts

@@ -0,0 +1,39 @@
+import { DEFAULT_AGENT } from "./runs.ts";
+
+/**
+ * The Agent tool's argument preparation (pure), run by pi before schema
+ * validation. `task` is required in the schema: a weak model read an optional
+ * task as optional and sent run options with no task, again and again
+ * (DeepSeek V3.2, live, 2026-10-05). Two callers still validate:
+ *
+ * - a Claude Code-trained model writes the task as `prompt`, which is moved
+ *   into `task` (TOOL-FIDELITY-REVIEW-2026-09-07 H1);
+ * - `action: "list"` only browses the catalog and needs no task.
+ *
+ * A run that names no agent gets general-purpose here, as in Claude Code, so
+ * the permission gate, hooks and the stored call see the agent that runs: an
+ * `Agent(general-purpose)` deny rule must stop a call that omits the type.
+ *
+ * Anything that is not a plain object is passed through for the validator to
+ * reject as it does today.
+ */
+export function prepareAgentArguments(args: unknown): unknown {
+	if (!args || typeof args !== "object" || Array.isArray(args)) return args;
+	const input = args as Record<string, unknown>;
+	const prepared = withTask(input);
+	if (!isRun(input) || (typeof input.subagent_type === "string" && input.subagent_type)) return prepared;
+	return { ...prepared, subagent_type: DEFAULT_AGENT };
+}
+
+function withTask(input: Record<string, unknown>): Record<string, unknown> {
+	if (typeof input.task === "string" && input.task.length > 0) return input;
+	if (typeof input.prompt === "string" && input.prompt.length > 0) return { ...input, task: input.prompt };
+	if (input.action === "list" && input.task === undefined) return { ...input, task: "" };
+	return input;
+}
+
+/** A call carrying run options (a task, a name, a model/thinking/isolation override, or action:"run"); one with none lists the catalog. */
+function isRun(input: Record<string, unknown>): boolean {
+	if (input.action === "list") return false;
+	return input.action === "run" || [input.task, input.prompt, input.name, input.model, input.isolation, input.thinking].some((value) => value != null);
+}

package/extensions/subagents/agent-description.ts

@@ -0,0 +1,132 @@
+/**
+ * The Agent tool's model-facing description: Claude Code's Agent text plus
+ * One Code's own paragraph (pure).
+ *
+ * The short form goes to frontier and workhorse models, the long form (the
+ * text Claude Code writes for its weakest models, with the fork guidance,
+ * the briefing section and worked examples) to cheap and tiny ones
+ * (lib/tool-variants.ts). Changes from Claude Code's text: a fork rejects a
+ * `model` override rather than ignoring it, agent definitions come from
+ * `.claude/agents/*.md` only, and tool names are One Code's. The closing
+ * paragraph describes what only One Code has: `task_output` and `task_stop`,
+ * the one-shot print session, run names and `action: "list"`.
+ */
+
+import type { DescriptionForm } from "../lib/tool-variants.ts";
+
+export const AGENT_SHORT_DESCRIPTION = `Launch a new agent to handle complex, multi-step tasks. Each agent type has specific capabilities and tools available to it.
+
+Available agent types are listed in <system-reminder> messages in the conversation.
+
+When using the Agent tool, specify a subagent_type to select an agent: \`"fork"\` forks yourself (the fork inherits your full conversation context and always runs on your model — a \`model\` override is rejected); any other type — or omitting it — starts a fresh agent (general-purpose by default).
+
+## When to use
+
+Reach for this when the task matches an available agent type, when you have independent work to run in parallel, or when answering would mean reading across several files — delegate it and you keep the conclusion, not the file dumps. For a single-fact lookup where you already know the file, symbol, or value, search directly. Once you've delegated a search, don't also run it yourself — wait for the result.
+
+A fork runs in the background and keeps its tool output out of your context. If you are the fork, execute directly — don't re-delegate. Subagents run in the background; you'll be notified when one completes. Never fabricate or predict a pending agent's results — the notification is never something you write yourself; if the user asks before it arrives, say it's still running.
+
+- The agent's final report is not shown to the user — relay what matters.
+- Use SendMessage with the agent's ID or name to continue a previously spawned agent with its context intact; a new Agent call starts fresh (except subagent_type: "fork", which inherits your context).
+- Each agent type's model, reasoning effort, and tools come from its definition (\`.claude/agents/*.md\` frontmatter).
+- \`isolation: "worktree"\` gives the agent its own git worktree (auto-cleaned if unchanged).`;
+
+export const AGENT_LONG_DESCRIPTION = `Launch a new agent to handle complex, multi-step tasks. Each agent type has specific capabilities and tools available to it.
+
+Available agent types are listed in <system-reminder> messages in the conversation.
+
+When using the Agent tool, specify a subagent_type to select an agent: \`"fork"\` forks yourself (the fork inherits your full conversation context and always runs on your model — a \`model\` override is rejected); any other type — or omitting it — starts a fresh agent (general-purpose by default).
+
+## Usage notes
+
+- Always include a short description summarizing what the agent will do
+- When the agent is done, its final report is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result.
+- Trust but verify: an agent's summary describes what it intended to do, not necessarily what it did. When an agent writes or edits code, check the actual changes before reporting the work as done.
+- To continue a previously spawned agent, use SendMessage with the agent's ID or name as the \`to\` field — that resumes it with full context. A new Agent call starts a fresh agent with no memory of prior runs (except subagent_type: "fork"), so the prompt must be self-contained.
+- Each agent type's model, reasoning effort, and tool access are set in its definition (\`.claude/agents/*.md\` frontmatter); the \`model\` parameter here overrides the definition for this one call.
+- Clearly tell the agent whether you expect it to write code or just to do research (search, file reads, web fetches, etc.), since a fresh agent is not aware of the user's intent
+- If the agent description mentions that it should be used proactively, then you should try your best to use it without the user having to ask for it first.
+- If the user specifies that they want you to run agents "in parallel", you MUST send a single message with multiple Agent tool use content blocks. For example, if you need to launch both a build-validator agent and a test-runner agent in parallel, send a single message with both tool calls.
+- With \`isolation: "worktree"\`, the worktree is automatically cleaned up if the agent makes no changes; otherwise the path and branch are returned in the result.
+
+## When to fork
+
+Fork yourself (pass \`subagent_type: "fork"\`) when the intermediate tool output isn't worth keeping in your context. The criterion is qualitative — "will I need this output again" — not task size. Fork open-ended questions. If research can be broken into independent questions, launch parallel forks in one message. A fork beats a fresh subagent for this — it inherits context and shares your cache.
+
+Forks are cheap because they share your prompt cache.
+
+**Don't peek.** The tool result includes an \`output_file\` path — do not read or tail it. You get a completion notification; trust it. Reading the transcript mid-flight pulls the fork's tool noise into your context, which defeats the point of forking.
+
+**Don't race.** After launching, you know nothing about what the fork found. Never fabricate or predict fork results in any format — not as prose, summary, or structured output. The notification arrives as a user-role message in a later turn; it is never something you write yourself. If the user asks a follow-up before the notification lands, tell them the fork is still running — give status, not a guess.
+
+**Writing a fork prompt.** Since the fork inherits your context, the prompt is a *directive* — what to do, not what the situation is. Be specific about scope: what's in, what's out, what another agent is handling. Don't re-explain background.
+
+
+## Writing the prompt
+
+Any agent other than a fork starts with zero context. Brief the agent like a smart colleague who just walked into the room — it hasn't seen this conversation, doesn't know what you've tried, doesn't understand why this task matters.
+- Explain what you're trying to accomplish and why.
+- Describe what you've already learned or ruled out.
+- Give enough context about the surrounding problem that the agent can make judgment calls rather than just following a narrow instruction.
+- If you need a short response, say so ("report in under 200 words").
+- Lookups: hand over the exact command. Investigations: hand over the question — prescribed steps become dead weight when the premise is wrong.
+
+For fresh agents, terse command-style prompts produce shallow, generic work.
+
+**Never delegate understanding.** Don't write "based on your findings, fix the bug" or "based on the research, implement it." Those phrases push synthesis onto the agent instead of doing it yourself. Write prompts that prove you understood: include file paths, line numbers, what specifically to change.
+
+Example usage:
+
+<example>
+user: "What's left on this branch before we can ship?"
+assistant: <thinking>Forking this — it's a survey question. I want the punch list, not the git output in my context.</thinking>
+Agent({
+  subagent_type: "fork",
+  name: "ship-audit",
+  description: "Branch ship-readiness audit",
+  prompt: "Audit what's left before this branch can ship. Check: uncommitted changes, commits ahead of main, whether tests exist, whether the GrowthBook gate is wired up, whether CI-relevant files changed. Report a punch list — done vs. missing. Under 200 words."
+})
+assistant: Ship-readiness audit running.
+<commentary>
+Turn ends here. The coordinator knows nothing about the findings yet. What follows is a SEPARATE turn — the notification arrives from outside, as a user-role message. It is not something the coordinator writes.
+</commentary>
+[later turn — notification arrives as user message]
+assistant: Audit's back. Three blockers: no tests for the new prompt path, GrowthBook gate wired but not in build_flags.yaml, and one uncommitted file.
+</example>
+
+<example>
+user: "so is the gate wired up or not"
+<commentary>
+User asks mid-wait. The audit fork was launched to answer exactly this, and it hasn't returned. The coordinator does not have this answer. Give status, not a fabricated result.
+</commentary>
+assistant: Still waiting on the audit — that's one of the things it's checking. Should land shortly.
+</example>
+
+<example>
+user: "Can you get a second opinion on whether this migration is safe?"
+assistant: <thinking>I'll ask the code-reviewer agent — it won't see my analysis, so it can give an independent read.</thinking>
+<commentary>
+A non-fork subagent_type is specified, so the agent starts fresh. It needs full context in the prompt. The briefing explains what to assess and why.
+</commentary>
+Agent({
+  name: "migration-review",
+  description: "Independent migration review",
+  subagent_type: "code-reviewer",
+  prompt: "Review migration 0042_user_schema.sql for safety. Context: we're adding a NOT NULL column to a 50M-row table. Existing rows get a backfill default. I want a second opinion on whether the backfill approach is safe under concurrent writes — I've checked locking behavior but want independent verification. Report: is this safe, and if not, what specifically breaks?"
+})
+</example>
+`;
+
+/** One Code's own part, after Claude Code's text in both forms. */
+export const AGENT_HOW_AGENTS_RUN = `## How agents run
+
+- Call task_output only if your next step cannot proceed without the result (block=true waits); stop a run with task_stop. Both are deferred — load them with tool_search first.
+- In a one-shot print session the call blocks and returns the report directly — no notification follows.
+- Give a complete, self-contained task: the agent cannot ask follow-up questions.
+- Each run gets a name — SendMessage reaches it live while it runs and continues it after it finishes. \`action: "list"\` re-prints the agent catalog.`;
+
+/** The Agent description for a form, naming the mode's agent folder (`.onecode` in independent mode, lib/config-mode.ts). */
+export function agentDescription(form: DescriptionForm, configDir = ".claude"): string {
+	const base = form === "long" ? AGENT_LONG_DESCRIPTION : AGENT_SHORT_DESCRIPTION;
+	return `${base.trimEnd()}\n\n${AGENT_HOW_AGENTS_RUN}`.replaceAll("`.claude/agents/*.md`", `\`${configDir}/agents/*.md\``);
+}