claude-code-modes 0.4.0 → 0.4.1

package/README.md

@@ -147,11 +147,10 @@ prompts/
   chill/        Alternative base (emotion-research-informed, leaner)
   flow/         Alternative base (chill's calm + restored engagement)
   axis/         Behavioral prompts organized by three axes
-  style/        Writing styles (declaudified)
   modifiers/    Behavioral layers (bold, debug, methodical, director, readonly, context-pacing, speak-plain, tdd, muse, flow, playful)
 ```
 
-Each base has a `base.json` manifest — a flat JSON array declaring fragment order with `"axes"` and `"modifiers"` as reserved insertion points. The standard base is validated against Claude Code **v2.1.198**.
+Each base has a `base.json` manifest — a flat JSON array declaring fragment order with `"axes"` and `"modifiers"` as reserved insertion points. The standard base is validated against Claude Code **v2.1.217**.
 
 The behavioral layer is composed from three independent axes — **agency** (how much initiative), **quality** (what code standard), and **scope** (how far beyond the request). Presets are just named combinations of these three values.
 
@@ -186,15 +185,6 @@ claude-mode create --quality ./team-quality.md     # Use a custom quality fragme
 claude-mode create --quality team-standard          # Resolve from config
 ```
 
-Set a writing style — a single fragment that shapes how Claude writes to you (answers, summaries, commit messages), independent of the behavioral axes:
-
-```bash
-claude-mode create --style declaudified            # Built-in: lead with the answer, cut filler and stock phrases
-claude-mode create --style ./house-style.md        # Or a custom fragment / config-defined name
-```
-
-No style is applied unless you pass `--style`, set `defaultStyle` in config, or use a preset that declares one.
-
 Add modifiers:
 
 ```bash
@@ -208,9 +198,12 @@ claude-mode create --append-system-prompt "Use Rust, not TypeScript"
 Pass flags through to Claude Code:
 
 ```bash
-claude-mode create -- --verbose --model sonnet
+claude-mode create --model sonnet          # model choice also lands in the prompt's environment info
+claude-mode create -- --verbose            # anything after -- goes to claude verbatim
 ```
 
+The environment section of the assembled prompt reports the model claude will actually run: from `--model` (before or after `--`), else the `ANTHROPIC_MODEL` env var, else Claude settings files (`.claude/settings.local.json`, `.claude/settings.json`, `~/.claude/settings.json`), else the newest known model.
+
 Debug the assembled prompt:
 
 ```bash
@@ -259,9 +252,6 @@ Example `.claude-mode.json`:
   "modifiers": {
     "team-rules": "./prompts/team-rules.md"
   },
-  "styles": {
-    "house": "./prompts/house-style.md"
-  },
   "axes": {
     "quality": {
       "team-standard": "./prompts/team-quality.md"
@@ -272,7 +262,6 @@ Example `.claude-mode.json`:
       "agency": "collaborative",
       "quality": "team-standard",
       "scope": "adjacent",
-      "style": "house",
       "modifiers": ["team-rules"]
     }
   }
@@ -281,15 +270,13 @@ Example `.claude-mode.json`:
 
 - **`defaultModifiers`** — always applied to every invocation (no flag needed)
 - **`modifiers`** — named modifiers referencing markdown files
-- **`styles`** — named writing styles referencing markdown files
 - **`axes`** — custom axis values (replace built-in fragments)
 - **`presets`** — named presets composing built-in and custom values
 
-Config also supports bases and a default style:
+Config also supports bases:
 
 - **`defaultBase`** — base to use when `--base` isn't specified
 - **`bases`** — named bases referencing directories with `base.json` manifests
-- **`defaultStyle`** — style to apply when `--style` isn't specified
 
 Config searches `.claude-mode.json` in the current directory first, then `~/.config/claude-mode/config.json` as a global fallback. All commands accept `--global` to target the global config.
 
@@ -302,8 +289,6 @@ claude-mode config add-default <name-or-path>        # Add to defaultModifiers
 claude-mode config remove-default <name>             # Remove from defaultModifiers
 claude-mode config add-modifier <name> <path>        # Register named modifier
 claude-mode config remove-modifier <name>            # Unregister named modifier
-claude-mode config add-style <name> <path>           # Register named style
-claude-mode config remove-style <name>               # Unregister named style
 claude-mode config add-axis <axis> <name> <path>     # Register custom axis value
 claude-mode config remove-axis <axis> <name>         # Unregister custom axis value
 claude-mode config add-preset <name> [flags]         # Create custom preset

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-modes",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Behaviorally-tuned system prompts for Claude Code",
   "license": "MIT",
   "type": "module",

package/prompts/base/actions.md

@@ -8,4 +8,4 @@ Examples of the kind of risky actions that warrant user confirmation:
 - Actions visible to others or that affect shared state: pushing code, creating/closing/commenting on PRs or issues, sending messages (Slack, email, GitHub), posting to external services, modifying shared infrastructure or permissions
 - Uploading content to third-party web tools (diagram renderers, pastebins, gists) publishes it - consider whether it could be sensitive before sending, since it may be cached or indexed even if later deleted.
 
-When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. If you're unsure whether the user would want something kept, prefer a reversible step (move it aside, rename it, or stash it) over deleting; files you created yourself this session (scratch outputs, experiment intermediates) are yours to clean up freely. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In a git repository, run `git status` before any command that could discard uncommitted work (git checkout/restore/reset/clean, rm -rf on a repo path, restoring from a snapshot), and stash (with `-u` for untracked) or commit anything you find first. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.
+When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. If you're unsure whether the user would want something kept, prefer a reversible step (move it aside, rename it, or stash it) over deleting; files you created yourself this session (scratch outputs, experiment intermediates) are yours to clean up freely. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In a git repository, run `git status` before any command that could discard uncommitted work (git checkout/restore/reset/clean, rm -rf on a repo path, restoring from a snapshot), and stash (with `-u` for untracked) or commit anything you find first. And when staging or committing: review what's included (`git status` after a broad `git add`), and if you see anything suspicious that might reveal secrets — even if the filename looks innocuous — double-check the file's contents before pushing. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.

package/src/args.ts

@@ -18,10 +18,22 @@ export interface ParsedArgs {
   forwarded: {
     appendSystemPrompt?: string;
     appendSystemPromptFile?: string;
+    model?: string;
   };
+  /** Model claude will run — from --model, or peeked from after `--`; drives env detection */
+  modelHint: string | null;
   passthroughArgs: string[];
 }
 
+// After `--` everything is passed verbatim, but the model choice still shapes
+// the environment section — peek without disturbing the passthrough list
+function peekModelAfterDashDash(args: string[]): string | null {
+  const flagIdx = args.indexOf("--model");
+  if (flagIdx >= 0 && flagIdx + 1 < args.length) return args[flagIdx + 1];
+  const inline = args.find((arg) => arg.startsWith("--model="));
+  return inline ? inline.slice("--model=".length) : null;
+}
+
 export function parseCliArgs(argv: string[]): ParsedArgs {
   // Split at -- separator
   const dashDashIdx = argv.indexOf("--");
@@ -42,6 +54,7 @@ export function parseCliArgs(argv: string[]): ParsedArgs {
       "context-pacing": { type: "boolean" },
       "append-system-prompt": { type: "string" },
       "append-system-prompt-file": { type: "string" },
+      model: { type: "string" },
       "system-prompt": { type: "string" },
       "system-prompt-file": { type: "string" },
       help: { type: "boolean" },
@@ -81,7 +94,7 @@ export function parseCliArgs(argv: string[]): ParsedArgs {
   // Collect unknown flags for passthrough
   const knownFlags = new Set([
     "base", "agency", "quality", "scope", "style", "modifier", "readonly", "print", "context-pacing",
-    "append-system-prompt", "append-system-prompt-file",
+    "append-system-prompt", "append-system-prompt-file", "model",
     "system-prompt", "system-prompt-file", "help", "version",
   ]);
   const unknownPassthrough: string[] = [];
@@ -115,7 +128,9 @@ export function parseCliArgs(argv: string[]): ParsedArgs {
     forwarded: {
       appendSystemPrompt: values["append-system-prompt"] as string | undefined,
       appendSystemPromptFile: values["append-system-prompt-file"] as string | undefined,
+      model: values.model as string | undefined,
     },
+    modelHint: (values.model as string | undefined) ?? peekModelAfterDashDash(afterDashDash),
     passthroughArgs,
   };
 }

package/src/build-info.ts

@@ -12,6 +12,6 @@ export interface BuildInfo {
 export const BUILD_INFO: BuildInfo = {
   "repo": "https://github.com/nklisch/claude-code-modes",
   "branch": null,
-  "commit": "91f6069",
+  "commit": "6303b59",
   "dirty": false
 };

package/src/build-prompt.ts

@@ -98,7 +98,7 @@ function main(): void {
   }
 
   // Detect environment and build template vars
-  const env = detectEnv();
+  const env = detectEnv(parsed.modelHint);
   const templateVars = buildTemplateVars(env);
 
   // Assemble the prompt
@@ -127,6 +127,9 @@ function main(): void {
   if (parsed.forwarded.appendSystemPromptFile) {
     claudeArgs.push("--append-system-prompt-file", parsed.forwarded.appendSystemPromptFile);
   }
+  if (parsed.forwarded.model) {
+    claudeArgs.push("--model", parsed.forwarded.model);
+  }
 
   // Add passthrough args
   claudeArgs.push(...parsed.passthroughArgs);

package/src/cli.ts

@@ -119,7 +119,7 @@ async function main(): Promise<void> {
   }
 
   // Detect environment and build template vars
-  const env = detectEnv();
+  const env = detectEnv(parsed.modelHint);
   const templateVars = buildTemplateVars(env);
 
   // Assemble the prompt
@@ -150,6 +150,9 @@ async function main(): Promise<void> {
   if (parsed.forwarded.appendSystemPromptFile) {
     claudeArgs.push("--append-system-prompt-file", parsed.forwarded.appendSystemPromptFile);
   }
+  if (parsed.forwarded.model) {
+    claudeArgs.push("--model", parsed.forwarded.model);
+  }
 
   // Add passthrough args
   claudeArgs.push(...parsed.passthroughArgs);

package/src/embedded-prompts.ts

@@ -45,7 +45,7 @@ Examples of the kind of risky actions that warrant user confirmation:
 - Actions visible to others or that affect shared state: pushing code, creating/closing/commenting on PRs or issues, sending messages (Slack, email, GitHub), posting to external services, modifying shared infrastructure or permissions
 - Uploading content to third-party web tools (diagram renderers, pastebins, gists) publishes it - consider whether it could be sensitive before sending, since it may be cached or indexed even if later deleted.
 
-When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. If you're unsure whether the user would want something kept, prefer a reversible step (move it aside, rename it, or stash it) over deleting; files you created yourself this session (scratch outputs, experiment intermediates) are yours to clean up freely. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In a git repository, run \`git status\` before any command that could discard uncommitted work (git checkout/restore/reset/clean, rm -rf on a repo path, restoring from a snapshot), and stash (with \`-u\` for untracked) or commit anything you find first. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.
+When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. If you're unsure whether the user would want something kept, prefer a reversible step (move it aside, rename it, or stash it) over deleting; files you created yourself this session (scratch outputs, experiment intermediates) are yours to clean up freely. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In a git repository, run \`git status\` before any command that could discard uncommitted work (git checkout/restore/reset/clean, rm -rf on a repo path, restoring from a snapshot), and stash (with \`-u\` for untracked) or commit anything you find first. And when staging or committing: review what's included (\`git status\` after a broad \`git add\`), and if you see anything suspicious that might reveal secrets — even if the filename looks innocuous — double-check the file's contents before pushing. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.
 `,
   "base/tools.md": `# Using your tools
  - Use your dedicated tools instead of shell equivalents. Read works better than cat or grep. Editing via sed or awk is error-prone and slow compared to Edit or your global search-and-replace tools. Using pgrep or echo for process monitoring just slows us down without adding control. Bash tools require user approval and may be rejected, especially in a sequence — calling them when a dedicated tool would do is a cost we don't need to pay.

package/src/env.ts

@@ -1,6 +1,8 @@
 import { execSync } from "node:child_process";
-import { basename } from "node:path";
-import type { EnvInfo, TemplateVars } from "./types.js";
+import { readFileSync } from "node:fs";
+import { homedir } from "node:os";
+import { basename, join } from "node:path";
+import type { EnvInfo, ModelInfo, TemplateVars } from "./types.js";
 
 function exec(command: string): string | null {
   try {
@@ -18,7 +20,77 @@ function exec(command: string): string | null {
   }
 }
 
-export function detectEnv(): EnvInfo {
+// Model metadata table extracted from the Claude Code binary — update when Claude Code updates.
+// Extraction: grep the native binary for `{id:"claude-...,display_name:...,knowledge_cutoff:...`
+const MODEL_TABLE: readonly ModelInfo[] = [
+  { id: "claude-fable-5", name: "Fable 5", cutoff: "January 2026" },
+  { id: "claude-mythos-5", name: "Mythos 5", cutoff: "January 2026" },
+  { id: "claude-opus-4-8", name: "Opus 4.8", cutoff: "January 2026" },
+  { id: "claude-opus-4-7", name: "Opus 4.7", cutoff: "January 2026" },
+  { id: "claude-opus-4-6", name: "Opus 4.6", cutoff: "May 2025" },
+  { id: "claude-opus-4-5", name: "Opus 4.5", cutoff: "May 2025" },
+  { id: "claude-opus-4-1", name: "Opus 4.1", cutoff: "January 2025" },
+  { id: "claude-opus-4-0", name: "Opus 4", cutoff: "January 2025" },
+  { id: "claude-sonnet-5", name: "Sonnet 5", cutoff: "January 2026" },
+  { id: "claude-sonnet-4-6", name: "Sonnet 4.6", cutoff: "August 2025" },
+  { id: "claude-sonnet-4-5", name: "Sonnet 4.5", cutoff: "January 2025" },
+  { id: "claude-sonnet-4-0", name: "Sonnet 4", cutoff: "January 2025" },
+  { id: "claude-haiku-4-5", name: "Haiku 4.5", cutoff: "February 2025" },
+] as const;
+
+// Aliases resolve to the newest model of the family; opusplan executes on opus
+const MODEL_ALIASES: Record<string, string> = {
+  opus: "claude-opus-4-8",
+  opusplan: "claude-opus-4-8",
+  sonnet: "claude-sonnet-5",
+  haiku: "claude-haiku-4-5",
+  fable: "claude-fable-5",
+};
+
+const DEFAULT_MODEL: ModelInfo = MODEL_TABLE[0];
+
+export function resolveModel(raw: string | null | undefined): ModelInfo {
+  if (!raw || raw === "default") return DEFAULT_MODEL;
+
+  const has1m = raw.endsWith("[1m]");
+  const base = has1m ? raw.slice(0, -"[1m]".length) : raw;
+  const id = MODEL_ALIASES[base] ?? base;
+
+  // Exact id first, then dated variants like claude-haiku-4-5-20251001
+  const entry =
+    MODEL_TABLE.find((m) => m.id === id) ?? MODEL_TABLE.find((m) => id.startsWith(`${m.id}-`));
+  if (!entry) {
+    // Unknown model — likely newer than the table; surface the id as the name
+    // and keep the newest known cutoff rather than inventing one
+    return { name: id, id: has1m ? `${id}[1m]` : id, cutoff: DEFAULT_MODEL.cutoff };
+  }
+
+  return {
+    name: has1m ? `${entry.name} (1M context)` : entry.name,
+    id: has1m ? `${id}[1m]` : id,
+    cutoff: entry.cutoff,
+  };
+}
+
+// Claude Code reads its model setting from these files, most specific first
+function readConfiguredModel(cwd: string): string | null {
+  const candidates = [
+    join(cwd, ".claude", "settings.local.json"),
+    join(cwd, ".claude", "settings.json"),
+    join(homedir(), ".claude", "settings.json"),
+  ];
+  for (const path of candidates) {
+    try {
+      const settings = JSON.parse(readFileSync(path, "utf8"));
+      if (typeof settings.model === "string" && settings.model !== "") return settings.model;
+    } catch {
+      // Missing or malformed settings file — try the next candidate
+    }
+  }
+  return null;
+}
+
+export function detectEnv(modelArg?: string | null): EnvInfo {
   const cwd = process.cwd();
   const isGit = exec("git rev-parse --is-inside-work-tree") === "true";
 
@@ -39,15 +111,11 @@ export function detectEnv(): EnvInfo {
   const platform = exec("uname -s")?.toLowerCase() ?? "unknown";
   const shell = basename(process.env.SHELL || "bash");
   const osVersion = exec("uname -sr") ?? "unknown";
+  const model = resolveModel(modelArg ?? process.env.ANTHROPIC_MODEL ?? readConfiguredModel(cwd));
 
-  return { cwd, isGit, isWorktree, gitBranch, gitStatus, gitLog, platform, shell, osVersion };
+  return { cwd, isGit, isWorktree, gitBranch, gitStatus, gitLog, platform, shell, osVersion, model };
 }
 
-// Hardcoded model info — update when Claude Code updates
-const MODEL_NAME = "Fable 5";
-const MODEL_ID = "claude-fable-5";
-const KNOWLEDGE_CUTOFF = "January 2026";
-
 export function buildTemplateVars(env: EnvInfo): TemplateVars {
   let gitStatusBlock = "";
   if (env.isGit) {
@@ -73,9 +141,9 @@ export function buildTemplateVars(env: EnvInfo): TemplateVars {
     PLATFORM: env.platform,
     SHELL: env.shell,
     OS_VERSION: env.osVersion,
-    MODEL_NAME,
-    MODEL_ID,
-    KNOWLEDGE_CUTOFF,
+    MODEL_NAME: env.model.name,
+    MODEL_ID: env.model.id,
+    KNOWLEDGE_CUTOFF: env.model.cutoff,
     GIT_STATUS: gitStatusBlock,
     WORKTREE_NOTICE: worktreeNotice,
   };

package/src/types.ts

@@ -80,6 +80,13 @@ export interface ModeConfig {
   modifiers: string[]; // ordered list of modifier fragment paths (embedded keys or absolute paths)
 }
 
+/** Resolved model metadata for env.md substitution */
+export interface ModelInfo {
+  name: string;
+  id: string;
+  cutoff: string;
+}
+
 export interface EnvInfo {
   cwd: string;
   isGit: boolean;
@@ -90,6 +97,7 @@ export interface EnvInfo {
   platform: string;
   shell: string;
   osVersion: string;
+  model: ModelInfo;
 }
 
 /** Template variables for env.md substitution */

package/src/usage.ts

@@ -56,6 +56,8 @@ Modifiers:
 Forwarded to claude:
   --append-system-prompt <text>
   --append-system-prompt-file <path>
+  --model <alias|id>      Also sets the model info in the prompt's environment section.
+  Without --model, model info comes from ANTHROPIC_MODEL or Claude settings files.
 
 Config: .claude-mode.json (project) or ~/.config/claude-mode/config.json (global)