strategieslisted

## Step 0 — resolve the binary No environment variable carries this plugin's path under Codex. Codex lists each skill with the absolute path of its `SKILL.md`; **this file** is at `<plugin-root>/skills/strategies/SKILL.md`, so the binary is two directories above it: ``` <plugin-root>/bin/admin.mjs ``` Resolve that to an absolute path from this file's own location and use it in every command below. Do not write `${CLAUDE_PLUGIN_ROOT}`: Codex sets no plugin-root variable of any spelling, so the shell expands it to nothing and `node /bin/admin.mjs` fails with ENOENT. Run the bundled script — `POST /v2/control/strategies` behind it — and report the strategies it prints in the user's own terms: what the pattern is, and what it was inferred from. Ask for a small number and report all of them; a wall of generalisations is less useful than three good ones. ```bash node <plugin-root>/bin/admin.mjs strategies --max 5 node <plugin-root>/bin/admin.mjs strategies --max 8 --types failure,rule ``` Neither command here is an MCP tool: `mubit_strategies` and `mubit_lessons` left the default tool surface so that a session pays nothing to list them, and this script reaches the same two routes. ## The one thing to be clear about **`strategies` is the pattern *across* lessons. `lessons` reads the individual lessons themselves.** Every other retrieval verb answers with entries. `mcp__mubit__mubit_recall` finds the lessons that match a question, `admin.mjs lessons` lists the catalogue, `mc