superwiki 0.1.3 → 0.1.5

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "sw",
   "description": "An LLM-maintained wiki and task tracker in docs/ for coding agents. Obsidian friendly, with a static viewer.",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "license": "MIT",
   "keywords": [
     "wiki",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "sw",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "description": "An LLM-maintained wiki and task tracker in docs/ for coding agents. Obsidian friendly, with a static viewer.",
   "license": "MIT",
   "skills": "./skills/",

package/README.md

@@ -17,19 +17,23 @@ Then, in a project: `/sw-init`.
 
 ## Why
 
-Superwiki follows the LLM Wiki pattern described by Andrej Karpathy: raw sources you curate, a wiki the agent owns, and a short schema that tells the agent how to maintain it. On top of that it adds what a software project needs: tasks with dependencies, plans, and a record of decisions and lessons.
+Superwiki follows the LLM Wiki pattern described by Andrej Karpathy: raw sources you curate, a wiki the agent owns, and a short schema that tells the agent how to maintain it. On top of that it adds what a software project needs: tasks with dependencies, plans, reviews, and a record of decisions and lessons.
 
-It is built to be cheap for the agent. One small index to read, one file per task, and a script that answers "what is ready?", "what blocks this?" or "is anything broken?" without the agent reading the vault.
+It is built to be cheap for the agent:
+
+- **Little to read.** One small index, one file per task, and a script that answers "what is ready?", "what blocks this?" or "is anything broken?" without the agent reading the vault.
+- **Work in clean contexts.** Planning, implementing and reviewing run in subagents, each on the model you choose for it. The main session only keeps the task's status true, so it stays small.
+- **Cost you can see.** `sw-stats` shows what a session used, per agent; `sw-doctor` shows what every session carries before it starts, and what can go.
 
 Measured on a real project with 165 tasks, converted from a single markdown index:
 
 | | Before | After |
 | --- | --- | --- |
-| Read at the start of every session | 197 KB index | 94-byte catalog + 1.7 KB of rules |
+| Read at the start of every session | 197 KB index | 94-byte catalog + 2.7 KB of rules |
 | Read to start one task | the index, then the task's section | one file, 2 KB at the median |
 | Marking a task done | a status cell, plus a ✅ at every reference to it (median 12 places) | one frontmatter line |
 
-> Status: early. The CLI, the viewer, `sw-init` and the migration script are tested, and the planning flow has been run in all three agents; some skills have only been exercised once. [DESIGN.md](DESIGN.md) lists what has and has not been proven.
+> Status: early. The CLI, the viewer, `sw-init` and the migration script are tested. Planning, implementing and reviewing have been run end to end on real projects in Claude Code, and the planning flow in Codex and Copilot CLI; some skills have only been exercised once. [DESIGN.md](DESIGN.md) lists what has and has not been proven.
 
 ## What you get
 
@@ -84,9 +88,13 @@ git clone https://github.com/mhmtsrfglu/superwiki ~/.superwiki
 
 A linked install follows the clone: `git pull` updates every agent. `install.sh --copy` copies instead, `--uninstall` removes.
 
-All three agents below were checked the same way: the agent found the skills, refused to start a task with an unfinished dependency, and ran `sw-plan` end to end with the planner subagent.
+### Per agent
+
+All three agents were checked the same way: the agent found the skills, refused to start a task with an unfinished dependency, and ran `sw-plan` end to end with the planner subagent.
+
+The model for each role (planning, implementing, reviewing) is set with `sw-config`, which writes one agent file per role into the project. The skills dispatch those agents by name.
 
-### Claude Code
+#### Claude Code
 
 ```bash
 npx superwiki install claude
@@ -94,11 +102,11 @@ npx superwiki install claude
 
 Invoke with a slash: `/sw-init`, `/sw-plan T-01`.
 
-Claude Code reads `~/.claude/skills/` (and a project's `.claude/skills/`); it does not read `~/.agents/skills/`, so `global` is not enough for it.
+- Claude Code reads `~/.claude/skills/` (and a project's `.claude/skills/`). It does not read `~/.agents/skills/`, so `global` is not enough for it.
+- `sw-plan` enters plan mode when the session offers it.
+- Agent files: `.claude/agents/sw-planner.md`, `sw-implementer.md` and `sw-reviewer.md`. They load when a session starts; in a session that began before they existed, the skills fall back to built-in agents with the same model.
 
-`sw-plan` enters plan mode when the session offers it. A model set with `sw-config` for `claude` applies to the planner and implementer subagents, written to `.claude/agents/`; if those agents are not loaded, the skills fall back to built-in agents with the same model.
-
-### Codex CLI
+#### Codex CLI
 
 ```bash
 npx superwiki install codex
@@ -106,9 +114,10 @@ npx superwiki install codex
 
 Invoke with a dollar sign, or by name in a sentence: `$sw-init`, `$sw-plan T-01`, "use the sw-plan skill for T-01". Checked with CLI 0.153.
 
-A skill cannot switch Codex into plan mode; start planning yourself with `/plan` if you want the mode, or let `sw-plan` proceed without it (it changes no file before you approve). A model set with `sw-config` for `codex` is written to `.codex/agents/sw-planner.toml` and `sw-implementer.toml`, and the skills spawn those agents by name. Subagents must be enabled (they are by default in current releases).
+- A skill cannot switch Codex into plan mode. Start planning yourself with `/plan` if you want the mode, or let `sw-plan` proceed without it: it changes no file before you approve.
+- Agent files: `.codex/agents/sw-planner.toml`, `sw-implementer.toml` and `sw-reviewer.toml`. Subagents must be enabled; they are by default in current releases.
 
-### GitHub Copilot CLI
+#### GitHub Copilot CLI
 
 ```bash
 npx superwiki install copilot
@@ -116,11 +125,11 @@ npx superwiki install copilot
 
 Invoke with a slash, or by name in a sentence: `/sw-init`, "use the sw-plan skill for T-01". Checked with CLI 1.0.31.
 
-Copilot CLI also reads `~/.agents/skills/`, so if you installed `codex` or `global` it already has the skills.
-
-A skill cannot switch Copilot into plan mode; start with `copilot --mode plan` or `/plan` if you want it. A model set with `sw-config` for `copilot` is written to `.github/agents/sw-planner.agent.md` and `sw-implementer.agent.md`; the skills dispatch them with the `task` tool. Whether Copilot honours the `model:` field of those files has not been checked.
+- Copilot CLI also reads `~/.agents/skills/`, so if you installed `codex` or `global` it already has the skills.
+- A skill cannot switch Copilot into plan mode. Start with `copilot --mode plan` or `/plan` if you want it.
+- Agent files: `.github/agents/sw-planner.agent.md`, `sw-implementer.agent.md` and `sw-reviewer.agent.md`, dispatched with the `task` tool. Whether Copilot honours the `model:` field of those files has not been checked.
 
-### Other agents
+#### Other agents
 
 ```bash
 npx superwiki install global
@@ -128,8 +137,9 @@ npx superwiki install global
 
 Agents that load `SKILL.md` folders from `~/.agents/skills` pick the skills up from there. For an agent with its own skills folder (Cursor, Gemini CLI, OpenCode and others), copy the `skills/sw-*` folders from a clone into it by hand. Nothing has been run in these agents. What will differ:
 
-- the skills name Claude Code, Codex and Copilot tools when they dispatch subagents; elsewhere they fall back to doing the planning or implementing in the main session, and say so;
-- `sw-config` writes agent files only for `claude`, `codex` and `copilot`, so a per-role model cannot be set.
+- the skills name Claude Code, Codex and Copilot tools when they dispatch subagents; elsewhere they fall back to doing the work in the main session, and say so;
+- `sw-config` writes agent files only for `claude`, `codex` and `copilot`, so a per-role model cannot be set;
+- `sw-stats` and `sw-doctor` read the session records of those three tools only.
 
 Everything else (the vault, the CLI, the viewer, ingest, lint, explain, triage) depends only on Node and on the agent following the skill text.
 
@@ -147,7 +157,7 @@ npx superwiki@latest install claude      # update: same command, newest release
 npx superwiki uninstall all
 ```
 
-After an update, run `sw-init` again in each project: it replaces `docs/.sw/sw.mjs`, the templates and `docs/viewer.html` with the new version and keeps your content.
+After an update, run `sw-init` again in each project: it replaces `docs/.sw/sw.mjs`, the templates and `docs/viewer.html` with the new version and keeps your content. Until then the project keeps the script it was set up with, and a skill that needs a newer command says so.
 
 A project's `docs/` folder is plain markdown and keeps working as an Obsidian vault without Superwiki.
 
@@ -156,7 +166,7 @@ A project's `docs/` folder is plain markdown and keeps working as an Obsidian va
 | Skill | What it does |
 | --- | --- |
 | `sw-init` | set up `docs/` in the current project, or upgrade it |
-| `sw-migrate` | convert an existing table-based task index, on a new git branch |
+| `sw-migrate` | convert an existing table-based task index, on a git branch of its own |
 | `sw-ingest` | file a source into the wiki |
 | `sw-plan` | plan a task with the planner subagent and get your approval |
 | `sw-implement` | run a task with the implementer subagent, have it reviewed if the task asks for that, and record the result |
@@ -164,6 +174,8 @@ A project's `docs/` folder is plain markdown and keeps working as an Obsidian va
 | `sw-triage` | for a problem: seen before? lessons, likely causes |
 | `sw-lint` | structural checks by script, semantic review on request |
 | `sw-visualize` | open the viewer |
+| `sw-stats` | what the current session has cost: tokens, context, steps and tool calls, per agent |
+| `sw-doctor` | what a session carries before any work, and what to remove to make every step cheaper |
 | `sw-config` | the model each tool uses for planning, implementing and reviewing; task areas |
 
 ### Examples
@@ -191,6 +203,8 @@ Shown as typed in Claude Code. In Codex, write `$sw-plan` instead of `/sw-plan`.
 /sw-config plan with opus, implement with sonnet, review with opus
 /sw-lint                          check links, frontmatter and task dependencies
 /sw-visualize                     open the task board and the wiki in the browser
+/sw-stats                         what this session has cost so far, per agent
+/sw-doctor                        what fills the context before any work, and what can go
 ```
 
 You do not have to type a command. The rules `sw-init` adds to `AGENTS.md` tell the agent which skill fits, so a plain request should reach the same skill:
@@ -204,6 +218,40 @@ Users get the magic-link email twice. Have we seen this before?
 
 A filled-in example vault is in [examples/demo/docs](examples/demo/docs).
 
+### What a session cost
+
+`sw-stats` reads the record your agent keeps of the session and prints one row for the main session and one for each subagent. It writes nothing. `sw-implement` ends its report with the same table. This one is a real task: planned, implemented and reviewed in 37 minutes.
+
+```text
+session  claude  fe4cbd6c-8abf-4db6-9755-469dc7321dc7  2026-10-05 10:27 to 11:04, 37 min
+agent           model              steps  first  peak   sent  cached  output  tools  min
+main            claude-opus-5-5       27    79k  126k   2.8M     96%     18k     23   37
+sw-planner      claude-opus-5-5       31    59k  154k   3.5M     96%      8k     32    6
+sw-implementer  claude-sonnet-5-5     68    59k  252k  12.2M     96%     16k     76   26
+sw-reviewer     claude-opus-5-5       23    60k  137k   2.4M     89%     372     24   12
+total                                149      -     -  20.9M     95%     43k    155
+```
+
+`first` and `peak` are the tokens sent with one request. `sent` is that, summed over every step: each step sends the whole context again, which is why a long session in one context is expensive. In Copilot CLI the token columns fill in once the session has closed.
+
+### What a session starts with
+
+Every agent above began at 59k to 79k tokens before it had read anything, and paid for that on each of its steps. `sw-doctor` shows what that start is made of, from the same session record, and proposes what to switch off for this project. The same session:
+
+```text
+context at session start  claude  fe4cbd6c-8abf-4db6-9755-469dc7321dc7
+first request: 79k tokens
+part                             size  holds
+rule and memory files           30 KB  memory/MEMORY.md 18 KB, my-app/AGENTS.md 11 KB, ...
+skill list                      29 KB  213: marketing-skills 41, (none) 37, claude-seo 25, claude-ads 23, +11 more
+tool names (loaded on demand)   17 KB  381: claude_ai_higgsfield 116, claude_ai_meta_ads 98, +9 more
+agent list                      14 KB  46: claude-seo 18, (none) 12, claude-ads 10, +4 more
+MCP server instructions        8.3 KB  claude.ai higgsfield 2.0 KB, notebooklm 2.0 KB, ...
+session-start hooks            3.3 KB
+```
+
+Here most of the skills, agents and tools came from advertising and SEO plugins that this project never uses. The skill proposes changes and asks before making any; it touches project-local settings only, and never uninstalls a plugin or deletes a memory. Sizes are characters of text: a skill cannot run your agent's own context command (`/context` in Claude Code and Copilot CLI, `/status` in Codex), which shows the same in tokens.
+
 ### The CLI
 
 The skills call a small script that answers questions without the agent reading the vault. You can run it yourself, from the project root:
@@ -211,11 +259,13 @@ The skills call a small script that answers questions without the agent reading
 ```bash
 node docs/.sw/sw.mjs status                 # counts per area
 node docs/.sw/sw.mjs ready                  # tasks that can start now
-node docs/.sw/sw.mjs check P-15             # can it start or finish, and what is open
+node docs/.sw/sw.mjs check P-15             # can it start or finish, what is open, is a review required
 node docs/.sw/sw.mjs explain P-15           # dependencies, what it unblocks, plan, area guide
 node docs/.sw/sw.mjs search sync timeout    # where something is mentioned
 node docs/.sw/sw.mjs next-id P              # next free id in an area
 node docs/.sw/sw.mjs lint                   # broken links, bad frontmatter, dependency errors
+node docs/.sw/sw.mjs stats                  # tokens, context and steps of the agent session here
+node docs/.sw/sw.mjs doctor                 # what that session carried before it read anything
 node docs/.sw/sw.mjs serve --open           # the viewer, reading files live
 node docs/.sw/sw.mjs snapshot               # or: freeze the vault into docs/viewer.html, no server
 ```
@@ -223,14 +273,25 @@ node docs/.sw/sw.mjs snapshot               # or: freeze the vault into docs/vie
 ## Develop
 
 ```bash
-npm test       # builds skills/sw-init/assets/sw.mjs, then runs the tests
+npm test       # builds skills/sw-init/assets/sw.mjs and viewer.html, then runs the tests
 ```
 
-Releases are cut by the `Release` workflow (Actions → Release → Run workflow): it tests, bumps the version in `package.json` and the plugin manifests, publishes to npm, tags, and creates a GitHub release. It publishes through npm trusted publishing, so no token is stored: the package's settings on npmjs.com name this repository and `release.yml` as its trusted publisher.
+Edit sources in `src/`:
+
+| File | What it is |
+| --- | --- |
+| `src/core.js` | the vault model, derived task state, lint and search; shared by the CLI and the viewer |
+| `src/sessions.js` | finds the record an agent keeps of a session |
+| `src/stats.js` | reduces a session record to cost per agent |
+| `src/doctor.js` | reduces a session record to what the session started with |
+| `src/cli.js` | the commands |
+| `src/viewer.html` | the viewer |
+
+`scripts/build.mjs` bundles them into `skills/sw-init/assets/sw.mjs` and `viewer.html`. Those two files are generated: do not edit them.
 
 `node scripts/build-demo.mjs` builds the public demo into `site/` (the viewer with the example vault baked in); the Pages workflow deploys it on every push to `main`.
 
-`src/core.js` is shared by the CLI and the viewer. Edit sources in `src/`; the files in `skills/sw-init/assets/` named `sw.mjs` and `viewer.html` are generated.
+Releases are cut by the `Release` workflow (Actions → Release → Run workflow): it tests, bumps the version in `package.json` and the plugin manifests, publishes to npm, tags, and creates a GitHub release. It publishes with the repository secret `NPM_TOKEN`, an npm access token allowed to publish `superwiki`.
 
 ## License
 

package/commands/doctor.md

@@ -0,0 +1,5 @@
+---
+description: Show what fills the context before any work (rules, memory, skills, plugins, tools) and propose what to remove
+---
+
+Use the sw-doctor skill. User arguments: $ARGUMENTS

package/commands/stats.md

@@ -0,0 +1,5 @@
+---
+description: Show what this session has cost so far: tokens, context, steps and tool calls per agent
+---
+
+Use the sw-stats skill. User arguments: $ARGUMENTS

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "superwiki",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "description": "Agent skills that turn docs/ into an LLM-maintained wiki and task tracker. Obsidian-friendly. Works with Claude Code, Codex and Copilot CLI.",
   "keywords": [
     "claude-code",

package/skills/sw-doctor/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: sw-doctor
+description: Use when the user wants to make agent sessions lighter or cheaper to start, asks what fills the context window before any work (rules, memory, skills, plugins, MCP tools), why a session starts with so many tokens, or invokes sw-doctor or sw:doctor.
+---
+
+# sw-doctor
+
+Shows what a session carries before it has read anything, and proposes what to remove. Rule and memory files, the lists of skills, agents and tools, and what plugins and hooks add are sent again with every step of every agent, subagents included, so a smaller start makes every step cheaper.
+
+You cannot run the tool's own context command: it is typed by the user. A script reads the same blocks from the record the tool keeps of this session. You read nothing yourself and write no report.
+
+Run from the project root:
+
+```bash
+node docs/.sw/sw.mjs doctor
+```
+
+It reports the session it runs in. `--session <id or its first characters>` picks another session of this project, `--tool claude|codex|copilot` looks only at one tool's sessions.
+
+## Steps
+
+1. **Show the table as printed**, in a code block. Sizes are characters of text, not tokens.
+2. **Propose changes**, largest saving first, at most five. For each: the part and its size from the table, what to change, and where. Use the table under "What to propose". Propose only what the output supports, and say plainly when a part cannot be made smaller.
+3. **Ask before changing anything**, one proposal at a time. Which plugin or server a project needs is the user's call: say what a group appears to be for and let them decide.
+4. **Apply what the user approved**, within the limits under "Limits".
+5. **Have it measured.** A change takes effect in a new session. Ask the user to open one and run the tool's own command there: `/context` in Claude Code and Copilot CLI, `/status` in Codex. Compare its figures with the ones from before; a setting that changed nothing is reported as such and taken out again.
+
+If the user pastes the output of that command, use its token figures in place of the character sizes; the parts are the same.
+
+## What to propose
+
+| In the table | Propose | What it saves |
+| --- | --- | --- |
+| `rule and memory files`: one file is most of the part | name the file. A rules file (`AGENTS.md`, `CLAUDE.md`): move sections that are needed only for some work into a document the agent opens on demand, and leave a one-line pointer. A memory index: one line per entry holding one lesson; dates, counts and status belong in the entry's own file | its full size |
+| `agent list`: groups that have nothing to do with this project | switch those plugins off for this project (how: "Limits"). The group label is the plugin's name; `(none)` is the user's own and built-in entries | the lines of those agents |
+| `skill list`: groups that have nothing to do with this project | the same switch. Say what to expect: the tool gives the list a fixed budget and shortens descriptions to fit, so fewer skills usually means fuller descriptions for the rest, not a smaller list. Worth doing so the agent picks skills better; not a token saving | little or nothing |
+| `tool names (loaded on demand)`: servers the project does not use | the user disables those MCP servers for this project. Only names are loaded, so the saving is the size shown, not the size of the tool definitions | the names of those tools |
+| `MCP server instructions` | goes away with the server; no separate change | with the server |
+| `session-start hooks` | name the hook and the plugin it belongs to, if the user can say; it goes away with that plugin | its full size |
+| Codex: `skills instructions` is large | skills are listed from `~/.agents/skills` and from plugins; remove or move the ones this user does not use | not measured |
+| Copilot CLI: `custom instruction` is large | the project's instruction files; same advice as for a rules file | its full size |
+| `first request` is far above what the parts add up to | the rest is the tool's own system prompt and built-in tool definitions. Say so; it cannot be changed from here | nothing |
+
+Give a saving as the size in the table. Do not turn it into a token or money figure unless the user pasted token numbers.
+
+## Limits
+
+- **Project-local settings only.** Never edit the user's global settings, and never uninstall a plugin or remove a server: switching it off for this project is enough and is undone by deleting a line.
+- **Claude Code**:
+  - a plugin off: in `.claude/settings.local.json` (personal, normally git-ignored; keep what is already there), `"enabledPlugins": { "<plugin>@<marketplace>": false }`. The full key is in `~/.claude/settings.json` under `enabledPlugins`; read only that key.
+  - an MCP server or a claude.ai connector off: the user does it with `/mcp` in the session. Do not edit `~/.claude.json`, and do not set environment variables for it in the project's settings: that was tried and changed nothing.
+  - plugins synced from the user's claude.ai account are not in that settings file; they are removed in the account's settings.
+- **Codex and Copilot CLI**: propose, and let the user change their configuration; this skill does not edit it.
+- **Memory and rule files are the user's.** Shorten an index or move a section only when asked, keep a copy of the previous version next to the file, and never delete an entry.
+- If the project's own rules forbid a change, they win.
+
+## If it fails
+
+| Output | Do |
+| --- | --- |
+| `unknown command doctor` | the project's `docs/.sw/sw.mjs` is older than this skill; offer to run sw-init, which updates it |
+| `no agent session record found` | say so and ask the user to run the tool's context command and paste the output; work from that |
+| a note that the session has not made a request yet | another session of this project is newer than yours; run again with `--session` and the id of the one you mean |
+| a note that Copilot has not counted its tool definitions | pass it on; the other parts are valid |

package/skills/sw-implement/SKILL.md

@@ -7,7 +7,7 @@ description: Use when the user wants to implement, build, execute, start or cont
 
 Runs one task. You keep the task's status true and judge the result. The work is done by subagents that start from a clean context, on the models set in sw-config: an implementer, and a reviewer when the task asks for one. You do not read the code or the plan: their reports are your input.
 
-That split is what keeps a task cheap. A long session re-sends its whole context on every step; work done in a fresh context does not carry yours, and yours stays small because the work never enters it.
+That split is what keeps a task cheap. A long session sends its whole context again on every step; work done in a fresh context does not carry yours, and yours stays small because the work never enters it.
 
 Run commands from the project root. `<skill-dir>` is the directory this SKILL.md is in.
 
@@ -15,12 +15,16 @@ Run commands from the project root. `<skill-dir>` is the directory this SKILL.md
 
 1. **Pick the task.** Id given: use it. Otherwise `node docs/.sw/sw.mjs ready` and let the user choose; tasks already in progress come first.
 2. **Gate**: `node docs/.sw/sw.mjs check <ID>`.
-   - `can start: no  open deps: ...`: stop. Tell the user which tasks block it and offer to run the first blocker instead; do not run it unasked. Do not start the task anyway, and do not edit `deps` to get past this.
-   - `can start: n/a, status is in-progress`: this is a continuation; skip step 3.
-   - `can start: n/a, status is done` or `cancelled`: stop and ask what the user wants.
-   - `plan: ... (draft, not approved)`: stop; the plan needs the user's approval (sw-plan).
-   - `plan: none`: fine for a small task (one area, three "Done when" items or fewer, nothing open in its notes, a few files). For anything larger, recommend sw-plan first and let the user choose.
-   - `review: required (...)`: remember it for step 7.
+
+   | `check` says | Do |
+   | --- | --- |
+   | `can start: no  open deps: ...` | stop. Tell the user which tasks block it and offer to run the first blocker instead; do not run it unasked. Do not start the task anyway, and do not edit `deps` to get past this |
+   | `can start: n/a, status is in-progress` | this is a continuation; skip step 3 |
+   | `can start: n/a, status is done` or `cancelled` | stop and ask what the user wants |
+   | `plan: ... (draft, not approved)` | stop; the plan needs the user's approval (sw-plan) |
+   | `plan: none` | fine for a small task: one area, three "Done when" items or fewer, nothing open in its notes, a few files. For anything larger, recommend sw-plan first and let the user choose |
+   | `review: required (...)` | remember it for step 7 |
+
 3. **Mark it started** before any work: in the frontmatter of `docs/tasks/<ID>.md` set `status: in-progress` and `started:` today. Append `## [date] task | <ID> started` to `docs/log.md`, in the layout its last entries use.
 4. **Checks that need the environment.** If the task has a plan, look for `needs:` in it: `grep -n 'needs:' docs/plans/<ID>-plan.md`. Each hit is a check that starts services or changes data. Ask the user which of them may run; without a yes, none.
 5. **Dispatch the implementer** (how: "Dispatching" below). Its prompt is the task id, the project root if it is not your working directory, and which `needs:` checks it may run. Do not paste the plan into the prompt; it reads the files.
@@ -43,8 +47,18 @@ Run commands from the project root. `<skill-dir>` is the directory this SKILL.md
 9. **Keep the area guide, if the area has one.** `node docs/.sw/sw.mjs explain <ID>` prints `area guide:` with a path or `none`.
    - A guide exists: add the reports' `Guide:` lines to it, one line per fact under Layout, Patterns, Verify or Gotchas. Replace a line the new fact corrects, and keep the page under 60 lines.
    - No guide: do nothing. A guide is worth starting once several tasks in an area have needed the same facts; if the user asks for one, create `docs/wiki/guide-<area, lowercase>.md` from `docs/.sw/templates/guide.md` and list it in `index.md`.
-10. **File what else was learned.** If a report held a decision or constraint the wiki should keep, offer to save it as a wiki page (`type: decision` or `concept`) and add it to `index.md`. If the task fixed a problem whose cause is now known, or the review caught a defect worth remembering, offer a `type: lesson` page (Symptom, Cause, Fix, How to notice it earlier); sw-triage finds these later. If a report named follow-up work, offer to create the tasks. These are separate offers: act on each only when the user says yes to that one.
-11. **Report** to the user: outcome, each requirement with its evidence, the review verdict and findings, anything that differs from the task, files changed, and which tasks this unblocked (`node docs/.sw/sw.mjs ready`). Commit only if the user asks. End with one line: the task is recorded, so the next task is cheapest in a new session.
+10. **File what else was learned.** These are separate offers: act on each only when the user says yes to that one.
+    - A report held a decision or constraint the wiki should keep: offer a wiki page (`type: decision` or `concept`), added to `index.md`.
+    - The task fixed a problem whose cause is now known, or the review caught a defect worth remembering: offer a `type: lesson` page (Symptom, Cause, Fix, How to notice it earlier); sw-triage finds these later.
+    - A report named follow-up work: offer to create the tasks.
+11. **Report** to the user, in this order. Commit only if the user asks.
+    - the outcome;
+    - each requirement with its evidence, and anything that differs from the task;
+    - the review verdict and its findings;
+    - the files changed;
+    - the tasks this unblocked (`node docs/.sw/sw.mjs ready`);
+    - what the task cost: run `node docs/.sw/sw.mjs stats` and show its table as printed;
+    - one last line: the task is recorded, so the next task is cheapest in a new session.
 
 ## Dispatching
 

package/skills/sw-init/assets/sw.mjs

@@ -1,5 +1,11 @@
 #!/usr/bin/env node
-// Generated by scripts/build.mjs from src/core.js and src/cli.js. Do not edit.
+// Generated by scripts/build.mjs from src/core.js, src/sessions.js, src/stats.js, src/doctor.js, src/cli.js. Do not edit.
+import { existsSync, mkdirSync, readFileSync, readdirSync, realpathSync, statSync, writeFileSync } from 'node:fs';
+import { homedir } from 'node:os';
+import { basename, dirname, join, resolve as resolvePath, sep } from 'node:path';
+import { spawn } from 'node:child_process';
+import { createServer } from 'node:http';
+import { fileURLToPath } from 'node:url';
 // Superwiki core: vault model, derived task state and lint. Pure: no fs, no DOM.
 // Runs in Node (docs/.sw/sw.mjs) and inlined in the viewer, so both report the same findings.
 
@@ -316,13 +322,588 @@ export function guideFor(vault, area) {
   return vault.pages.find(p => p.folder === 'wiki' && p.data.type === 'guide' && key(p.data.area ?? '') === key(area)) || null;
 }
 
+// Finds the record an agent tool keeps of the session working in a project.
+// Claude Code, Codex and Copilot CLI each write every session to disk in their own layout; this
+// lists a project's sessions as { tool, id, modified, current, source } and picks one. What a
+// record means is left to the readers in stats.js and doctor.js.
+
+export const SESSION_TOOLS = ['claude', 'codex', 'copilot'];
+
+// Codex keeps every project's sessions in one tree; only the most recent files are opened.
+const CODEX_FILES_SCANNED = 100;
+
+// A record still being written can end in half a line; lines that do not parse are skipped.
+export function jsonLines(path) {
+  const records = [];
+  for (const line of readFileSync(path, 'utf8').split('\n')) {
+    if (!line) continue;
+    try {
+      records.push(JSON.parse(line));
+    } catch {}
+  }
+  return records;
+}
+
+export function jsonFile(path) {
+  try {
+    return JSON.parse(readFileSync(path, 'utf8'));
+  } catch {
+    return {};
+  }
+}
+
+const modifiedAt = path => statSync(path).mtimeMs;
+
+// The project root as typed and as resolved: tools record the working directory either way.
+function rootForms(root) {
+  const forms = new Set([root]);
+  try {
+    forms.add(realpathSync(root));
+  } catch {}
+  return [...forms];
+}
+
+const isWithin = (roots, dir) => Boolean(dir) && roots.some(root => dir === root || dir.startsWith(root + sep));
+
+// ---------- Claude Code ----------
+// ~/.claude/projects/<working directory, non-alphanumerics as dashes>/<session>.jsonl, and next to
+// it <session>/subagents/agent-<id>.jsonl with a .meta.json naming the agent type.
+// source: { path, subagentDir }
+
+const claudeHome = () => process.env.CLAUDE_CONFIG_DIR || join(homedir(), '.claude');
+
+function claudeSessions(root) {
+  const sessions = [];
+  for (const form of rootForms(root)) {
+    const dir = join(claudeHome(), 'projects', form.replace(/[^A-Za-z0-9]/g, '-'));
+    if (!existsSync(dir)) continue;
+    for (const name of readdirSync(dir)) {
+      if (!name.endsWith('.jsonl')) continue;
+      const id = name.slice(0, -'.jsonl'.length);
+      const path = join(dir, name);
+      sessions.push({
+        tool: 'claude',
+        id,
+        modified: modifiedAt(path),
+        current: id === process.env.CLAUDE_CODE_SESSION_ID,
+        source: { path, subagentDir: join(dir, id, 'subagents') },
+      });
+    }
+  }
+  return sessions;
+}
+
+// ---------- Codex ----------
+// ~/.codex/sessions/<year>/<month>/<day>/rollout-*.jsonl. The first line is the session's meta:
+// its working directory and, for a subagent, the session that spawned it and its role.
+// source: { files: [{ meta, records }] }, one file per agent
+
+const codexHome = () => process.env.CODEX_HOME || join(homedir(), '.codex');
+
+function rolloutFiles(dir, found = []) {
+  if (!existsSync(dir)) return found;
+  for (const entry of readdirSync(dir, { withFileTypes: true })) {
+    const path = join(dir, entry.name);
+    if (entry.isDirectory()) rolloutFiles(path, found);
+    else if (entry.name.endsWith('.jsonl')) found.push({ path, modified: modifiedAt(path) });
+  }
+  return found;
+}
+
+function codexSessions(root) {
+  const roots = rootForms(root);
+  const recent = rolloutFiles(join(codexHome(), 'sessions')).sort((a, b) => b.modified - a.modified).slice(0, CODEX_FILES_SCANNED);
+  const byId = new Map();
+  for (const { path, modified } of recent) {
+    const records = jsonLines(path);
+    const meta = records[0]?.type === 'session_meta' ? records[0].payload : null;
+    if (!meta || !isWithin(roots, meta.cwd)) continue;
+    const id = meta.session_id || meta.id;
+    if (!byId.has(id)) byId.set(id, { modified: 0, files: [] });
+    const group = byId.get(id);
+    group.modified = Math.max(group.modified, modified);
+    group.files.push({ meta, records });
+  }
+  return [...byId].map(([id, { modified, files }]) => ({ tool: 'codex', id, modified, current: false, source: { files } }));
+}
+
+// ---------- Copilot CLI ----------
+// ~/.copilot/session-state/<session>/events.jsonl, with the working directory in workspace.yaml.
+// source: { path }
+
+const copilotHome = () => join(homedir(), '.copilot');
+
+function copilotSessions(root) {
+  const roots = rootForms(root);
+  const base = join(copilotHome(), 'session-state');
+  if (!existsSync(base)) return [];
+  const sessions = [];
+  for (const id of readdirSync(base)) {
+    const path = join(base, id, 'events.jsonl');
+    const workspace = join(base, id, 'workspace.yaml');
+    if (!existsSync(path) || !existsSync(workspace)) continue;
+    const cwd = (readFileSync(workspace, 'utf8').match(/^cwd: (.*)$/m) || [])[1];
+    if (!isWithin(roots, cwd)) continue;
+    sessions.push({ tool: 'copilot', id, modified: modifiedAt(path), current: false, source: { path } });
+  }
+  return sessions;
+}
+
+// ---------- Choosing ----------
+
+const LISTERS = { claude: claudeSessions, codex: codexSessions, copilot: copilotSessions };
+
+// The session to report: the one named by `id` (a prefix is enough), else the session this command
+// runs in when the tool says which one that is, else the most recently written one.
+export function findSession(root, { tool, id } = {}) {
+  let sessions = (tool ? [tool] : SESSION_TOOLS).flatMap(name => LISTERS[name](root));
+  if (id) sessions = sessions.filter(session => session.id.startsWith(id));
+  sessions.sort((a, b) => b.modified - a.modified);
+  return (!id && sessions.find(session => session.current)) || sessions[0] || null;
+}
+
+// Session statistics: what an agent session has cost so far, as one row per agent: the main
+// session and each subagent it started. Reads the session record found by sessions.js.
+
+const MAIN = 'main';
+
+// ---------- The summary being built ----------
+
+const newStats = session => ({ tool: session.tool, id: session.id, agents: [], tools: {}, note: '' });
+
+// Token fields stay null when the record does not hold them, so "unknown" never prints as 0.
+const newAgent = name => ({
+  name, model: '', steps: 0, first: null, peak: null, sent: null, cached: null, output: null, toolCalls: 0, start: null, end: null,
+});
+
+const plus = (sum, n) => (sum ?? 0) + (n || 0);
+
+// One model request. `context` is everything sent with it, `cached` the part read from the cache.
+function addStep(agent, { context, cached, output }) {
+  agent.steps++;
+  agent.first ??= context;
+  agent.peak = Math.max(agent.peak ?? 0, context);
+  agent.sent = plus(agent.sent, context);
+  agent.cached = plus(agent.cached, cached);
+  agent.output = plus(agent.output, output);
+}
+
+function addToolCall(stats, agent, name) {
+  agent.toolCalls++;
+  stats.tools[name] = (stats.tools[name] || 0) + 1;
+}
+
+// Widens the agent's working period to include this record.
+function touch(agent, timestamp) {
+  const time = Date.parse(timestamp);
+  if (Number.isNaN(time)) return;
+  agent.start = Math.min(agent.start ?? time, time);
+  agent.end = Math.max(agent.end ?? time, time);
+}
+
+// Subagents are listed in the order they were started.
+const byStart = (a, b) => (a.start ?? 0) - (b.start ?? 0);
+
+// ---------- Claude Code ----------
+
+function claudeAgent(stats, name, path) {
+  const agent = newAgent(name);
+  // A reply is written as one line per content block. Each line repeats the reply's usage, and
+  // only the last one has the final output count, so the last line of a reply is the one kept.
+  const replies = new Map();
+  for (const record of jsonLines(path)) {
+    touch(agent, record.timestamp);
+    const message = record.type === 'assistant' && record.message;
+    if (!message) continue;
+    for (const block of message.content || []) {
+      if (block.type === 'tool_use') addToolCall(stats, agent, block.name);
+    }
+    if (message.usage) replies.set(message.id, message);
+  }
+  for (const { model, usage } of replies.values()) {
+    agent.model = model || agent.model;
+    const cached = usage.cache_read_input_tokens || 0;
+    addStep(agent, {
+      context: (usage.input_tokens || 0) + cached + (usage.cache_creation_input_tokens || 0),
+      cached,
+      output: usage.output_tokens,
+    });
+  }
+  return agent;
+}
+
+function claudeStats(session) {
+  const { path, subagentDir } = session.source;
+  const stats = newStats(session);
+  stats.agents.push(claudeAgent(stats, MAIN, path));
+  if (!existsSync(subagentDir)) return stats;
+  const subagents = readdirSync(subagentDir)
+    .filter(name => name.endsWith('.jsonl'))
+    .map(name => {
+      const meta = jsonFile(join(subagentDir, name.replace(/\.jsonl$/, '.meta.json')));
+      return claudeAgent(stats, meta.agentType || 'subagent', join(subagentDir, name));
+    });
+  stats.agents.push(...subagents.sort(byStart));
+  return stats;
+}
+
+// ---------- Codex ----------
+
+function codexAgent(stats, name, records) {
+  const agent = newAgent(name);
+  let lastTotal = null;
+  for (const record of records) {
+    touch(agent, record.timestamp);
+    const payload = record.payload || {};
+    if (record.type === 'turn_context') agent.model = payload.model || agent.model;
+    if (record.type === 'response_item' && /_call$/.test(payload.type || '')) addToolCall(stats, agent, payload.name || payload.type);
+    if (record.type !== 'event_msg' || payload.type !== 'token_count' || !payload.info) continue;
+    // The count is also repeated when only the rate limits change; a new request moves the total.
+    const total = payload.info.total_token_usage?.total_tokens;
+    if (total === lastTotal) continue;
+    lastTotal = total;
+    const last = payload.info.last_token_usage || {};
+    addStep(agent, { context: last.input_tokens || 0, cached: last.cached_input_tokens, output: last.output_tokens });
+  }
+  return agent;
+}
+
+function codexStats(session) {
+  const stats = newStats(session);
+  const subagents = [];
+  for (const { meta, records } of session.source.files) {
+    if (meta.thread_source === 'subagent') subagents.push(codexAgent(stats, meta.agent_role || meta.agent_nickname || 'subagent', records));
+    else stats.agents.push(codexAgent(stats, MAIN, records));
+  }
+  stats.agents.push(...subagents.sort(byStart));
+  return stats;
+}
+
+// ---------- Copilot CLI ----------
+// Events of a subagent carry its agentId. Token counts are written only when the session closes.
+
+function copilotStats(session) {
+  const stats = newStats(session);
+  const agents = new Map();
+  const agentOf = key => {
+    if (!agents.has(key)) agents.set(key, newAgent(key));
+    return agents.get(key);
+  };
+  agentOf(MAIN);
+  let closed = false;
+  for (const event of jsonLines(session.source.path)) {
+    const data = event.data || {};
+    const agent = agentOf(event.agentId || MAIN);
+    touch(agent, event.timestamp);
+    if (event.type === 'subagent.started') {
+      agent.name = data.agentName || agent.name;
+    } else if (event.type === 'assistant.message') {
+      agent.steps++;
+      agent.model = data.model || agent.model;
+    } else if (event.type === 'tool.execution_start') {
+      addToolCall(stats, agent, data.toolName);
+    } else if (event.type === 'session.shutdown' && data.agentMetrics) {
+      // A resumed session closes more than once; each close reports the run that ended with it.
+      closed = true;
+      for (const [key, metrics] of Object.entries(data.agentMetrics)) {
+        const reported = agentOf(key);
+        for (const { usage = {} } of Object.values(metrics.modelMetrics || {})) {
+          reported.sent = plus(reported.sent, usage.inputTokens);
+          reported.cached = plus(reported.cached, usage.cacheReadTokens);
+          reported.output = plus(reported.output, usage.outputTokens);
+        }
+      }
+    }
+  }
+  stats.agents = [...agents.values()];
+  if (!closed) stats.note = 'Copilot writes token counts when the session closes; until then /usage shows them.';
+  return stats;
+}
+
+const STATS_READERS = { claude: claudeStats, codex: codexStats, copilot: copilotStats };
+
+export const sessionStats = session => STATS_READERS[session.tool](session);
+
+// ---------- Printing ----------
+
+const COLUMNS = ['agent', 'model', 'steps', 'first', 'peak', 'sent', 'cached', 'output', 'tools', 'min'];
+const TEXT_COLUMNS = 2; // agent and model align left; the numbers after them align right
+const LEGEND = 'first, peak: tokens sent with one request. sent: that, summed over every step. cached: the share of sent read from the cache.';
+
+export function tokenCount(n) {
+  if (n == null) return '-';
+  if (n < 1000) return String(n);
+  if (n < 1e6) return `${Math.round(n / 1000)}k`;
+  return `${(n / 1e6).toFixed(1)}M`;
+}
+
+const cachedShare = agent => (agent.sent ? `${Math.round((100 * (agent.cached || 0)) / agent.sent)}%` : '-');
+const minutes = (start, end) => Math.round((end - start) / 60000);
+
+function clock(time) {
+  const d = new Date(time);
+  const two = n => String(n).padStart(2, '0');
+  return `${d.getFullYear()}-${two(d.getMonth() + 1)}-${two(d.getDate())} ${two(d.getHours())}:${two(d.getMinutes())}`;
+}
+
+// "2026-10-05 10:27 to 11:04, 37 min"; the end repeats the date only when it is another day.
+function period(start, end) {
+  const [from, to] = [clock(start), clock(end)];
+  const sameDay = from.slice(0, 10) === to.slice(0, 10);
+  return `${from} to ${sameDay ? to.slice(11) : to}, ${minutes(start, end)} min`;
+}
+
+function sessionPeriod(agents) {
+  const timed = agents.filter(agent => agent.start != null);
+  if (!timed.length) return '';
+  return period(Math.min(...timed.map(agent => agent.start)), Math.max(...timed.map(agent => agent.end)));
+}
+
+// The sum of the agents. It has no context of its own and no period, so those cells stay empty.
+function totalOf(agents) {
+  const total = newAgent('total');
+  for (const agent of agents) {
+    total.steps += agent.steps;
+    total.toolCalls += agent.toolCalls;
+    for (const field of ['sent', 'cached', 'output']) {
+      if (agent[field] != null) total[field] = plus(total[field], agent[field]);
+    }
+  }
+  return total;
+}
+
+const cells = agent => [
+  agent.name, agent.model, String(agent.steps), tokenCount(agent.first), tokenCount(agent.peak), tokenCount(agent.sent), cachedShare(agent),
+  tokenCount(agent.output), String(agent.toolCalls), agent.start == null ? '' : String(minutes(agent.start, agent.end)),
+];
+
+// Rows of text cells as aligned lines: the first `textColumns` align left, the rest right.
+export function alignedRows(rows, textColumns) {
+  const widths = rows[0].map((_, column) => Math.max(...rows.map(row => row[column].length)));
+  const pad = (cell, column) => (column < textColumns ? cell.padEnd(widths[column]) : cell.padStart(widths[column]));
+  return rows.map(row => row.map(pad).join('  ').trimEnd());
+}
+
+export function formatStats(stats) {
+  const { agents } = stats;
+  const rows = [COLUMNS, ...agents.map(cells)];
+  if (agents.length > 1) rows.push(cells(totalOf(agents)));
+  const calls = Object.entries(stats.tools).sort((a, b) => b[1] - a[1]).map(([name, count]) => `${name} ${count}`);
+  return [
+    ['session', stats.tool, stats.id, sessionPeriod(agents)].filter(Boolean).join('  '),
+    ...alignedRows(rows, TEXT_COLUMNS),
+    `tool calls  ${calls.join('  ') || 'none'}`,
+    LEGEND,
+    ...(stats.note ? [stats.note] : []),
+  ].join('\n');
+}
+
+// Start context: what an agent session carries before it has read anything. Rule and memory
+// files, the lists of skills, agents and tools, and what plugins and hooks add are sent again with
+// every step of every agent, so this is the cheapest place to make a session lighter.
+// Reads the session record found by sessions.js and reduces it to parts with a size and a source.
+
+// The command that shows the same context in tokens, in each tool.
+const CONTEXT_COMMANDS = { claude: '/context', codex: '/status', copilot: '/context' };
+const SMALL_PART_CHARS = 512; // smaller parts are summed into "other"
+const SOURCES_SHOWN = 6;
+const UNGROUPED = '(none)';
+const NOT_STARTED = 'This session has not made a request yet; its context is recorded with the first one.';
+
+// ---------- The report being built ----------
+
+const newReport = session => ({ tool: session.tool, id: session.id, firstRequest: null, parts: [], note: '' });
+
+// A part's sources are either texts with a size or groups with a count: { label, amount }.
+// `chars` is null for a part the record counts in tokens instead.
+const newPart = (name, measure) => ({ name, chars: 0, tokens: null, count: null, measure, sources: [] });
+
+// A part made of texts, each from a named source.
+function sized(name, texts) {
+  const part = newPart(name, 'size');
+  for (const [label, text] of texts) {
+    part.chars += text.length;
+    part.sources.push({ label, amount: text.length });
+  }
+  return part;
+}
+
+// A part that is one list of names, grouped by where each name comes from.
+function listed(name, names, text, groupOf) {
+  const part = newPart(name, 'count');
+  part.chars = text.length;
+  part.count = names.length;
+  const groups = new Map();
+  for (const item of names) groups.set(groupOf(item), (groups.get(groupOf(item)) || 0) + 1);
+  part.sources = [...groups].map(([label, amount]) => ({ label, amount }));
+  return part;
+}
+
+// "plugin:skill" and "plugin:agent" belong to the plugin; "mcp__server__tool" to the server.
+const pluginOf = name => (name.includes(':') ? name.slice(0, name.indexOf(':')) : UNGROUPED);
+const serverOf = name => (name.match(/^mcp__(.+?)__/) || [])[1] || UNGROUPED;
+
+// "memory/MEMORY.md": the last folder says which of several same-named files this is.
+const shortPath = path => `${basename(dirname(path))}/${basename(path)}`;
+
+// ---------- Claude Code ----------
+// Before the first reply the record holds one "attachment" per block of context the session was
+// given: the instruction files, the skill, agent and tool lists, server instructions, hook output.
+
+function claudePart(attachment) {
+  switch (attachment.type) {
+    case 'instructions':
+      return sized('rule and memory files', (attachment.files || []).map(file => [shortPath(file.path), file.content || '']));
+    case 'skill_listing':
+      return listed('skill list', attachment.names || [], attachment.content || '', pluginOf);
+    case 'agent_listing_delta':
+      return listed('agent list', attachment.addedTypes || [], (attachment.addedLines || []).join('\n'), pluginOf);
+    case 'deferred_tools_delta':
+      return listed('tool names (loaded on demand)', attachment.addedNames || [], (attachment.addedLines || []).join('\n'), serverOf);
+    case 'mcp_instructions_delta':
+      return sized('MCP server instructions', (attachment.addedNames || []).map((name, i) => [name, attachment.addedBlocks?.[i] || '']));
+    case 'hook_additional_context':
+      return sized('session-start hooks', [[attachment.hookName || 'hook', [attachment.content].flat().join('\n')]]);
+    default:
+      return null;
+  }
+}
+
+function claudeStart(session) {
+  const report = newReport(session);
+  for (const record of jsonLines(session.source.path)) {
+    if (record.type === 'attachment') {
+      const part = claudePart(record.attachment || {});
+      if (part) report.parts.push(part);
+    }
+    const usage = record.type === 'assistant' && record.message?.usage;
+    if (!usage) continue;
+    report.firstRequest = (usage.input_tokens || 0) + (usage.cache_read_input_tokens || 0) + (usage.cache_creation_input_tokens || 0);
+    break;
+  }
+  if (report.firstRequest == null) report.note = NOT_STARTED;
+  return report;
+}
+
+// ---------- Codex ----------
+// The session meta holds the base instructions. The messages before the first request hold the
+// rest, one tagged block each: <skills_instructions>, <plugins_instructions>, the AGENTS.md text.
+
+function codexBlockName(text) {
+  if (text.startsWith('# AGENTS.md')) return 'AGENTS.md';
+  const tag = (text.match(/^<([a-z_ ]+)>/) || [])[1];
+  return tag ? tag.replace(/_/g, ' ') : null; // untagged text is the user's own request
+}
+
+function codexStart(session) {
+  const report = newReport(session);
+  const main = session.source.files.find(file => file.meta.thread_source !== 'subagent') || session.source.files[0];
+  report.parts.push(sized('base instructions', [['codex', main.meta.base_instructions?.text || '']]));
+  for (const record of main.records) {
+    const payload = record.payload || {};
+    if (record.type === 'response_item' && payload.type === 'message') {
+      for (const block of payload.content || []) {
+        const name = codexBlockName(block.text || '');
+        if (name) report.parts.push(sized(name, [[payload.role, block.text]]));
+      }
+    }
+    if (record.type !== 'event_msg' || payload.type !== 'token_count' || !payload.info) continue;
+    report.firstRequest = payload.info.last_token_usage?.input_tokens ?? null;
+    break;
+  }
+  if (report.firstRequest == null) report.note = NOT_STARTED;
+  return report;
+}
+
+// ---------- Copilot CLI ----------
+// The first system message holds the context as tagged blocks (<tools>, <custom_instruction>).
+// A usage checkpoint, written later in the session, counts the tool definitions in tokens.
+
+function copilotStart(session) {
+  const report = newReport(session);
+  const events = jsonLines(session.source.path);
+  const system = events.find(event => event.type === 'system.message')?.data?.content || '';
+  for (const [, tag, body] of system.matchAll(/<([a-z_]+)>(.*?)<\/\1>/gs)) report.parts.push(sized(tag.replace(/_/g, ' '), [['system', body]]));
+  const checkpoint = events.find(event => event.type === 'session.usage_checkpoint')?.data?.promptCacheBreakState?.[0]?.models;
+  const usage = checkpoint && Object.values(checkpoint)[0];
+  if (usage?.tool_tokens == null) {
+    report.note = 'Copilot counts its tool definitions at the first usage checkpoint; this session has not reached one.';
+    return report;
+  }
+  report.parts.push({ ...newPart('tool definitions', 'count'), chars: null, tokens: usage.tool_tokens, count: usage.tool_count ?? null });
+  return report;
+}
+
+const START_READERS = { claude: claudeStart, codex: codexStart, copilot: copilotStart };
+
+// ---------- Tidying ----------
+
+// Blocks with the same name become one part.
+function mergedByName(parts) {
+  const byName = new Map();
+  for (const part of parts) {
+    const known = byName.get(part.name);
+    if (!known) {
+      byName.set(part.name, part);
+      continue;
+    }
+    known.chars += part.chars;
+    known.sources.push(...part.sources);
+  }
+  return [...byName.values()];
+}
+
+// Largest first; parts too small to matter are summed into "other", which comes last.
+function ranked(parts) {
+  const other = newPart('other', 'size');
+  const kept = [];
+  for (const part of parts) {
+    if (part.chars == null || part.chars >= SMALL_PART_CHARS) kept.push(part);
+    else other.chars += part.chars;
+  }
+  kept.sort((a, b) => (b.chars ?? 0) - (a.chars ?? 0));
+  return other.chars ? [...kept, other] : kept;
+}
+
+export function startContext(session) {
+  const report = START_READERS[session.tool](session);
+  report.parts = ranked(mergedByName(report.parts));
+  for (const part of report.parts) part.sources.sort((a, b) => b.amount - a.amount);
+  return report;
+}
+
+// ---------- Printing ----------
+
+const kilobytes = chars => `${(chars / 1024).toFixed(chars < 10 * 1024 ? 1 : 0)} KB`;
+const sizeOf = part => (part.chars == null ? `${tokenCount(part.tokens)} tokens` : kilobytes(part.chars));
+
+// "213: marketing-skills 41, claude-seo 25, +9 more" for a list, "MEMORY.md 18 KB, AGENTS.md 11 KB"
+// for texts. A part that is a single text says nothing its name and size have not said.
+function sourcesOf(part) {
+  if (part.measure === 'size' && part.sources.length < 2) return '';
+  const amount = source => (part.measure === 'size' ? kilobytes(source.amount) : String(source.amount));
+  const shown = part.sources.slice(0, SOURCES_SHOWN).map(source => `${source.label} ${amount(source)}`);
+  const hidden = part.sources.length - shown.length;
+  const list = shown.join(', ') + (hidden > 0 ? `, +${hidden} more` : '');
+  return part.count == null ? list : [String(part.count), list].filter(Boolean).join(': ');
+}
+
+export function formatStartContext(report) {
+  const rows = [['part', 'size', 'holds'], ...report.parts.map(part => [part.name, sizeOf(part), sourcesOf(part)])];
+  const [nameWidth, sizeWidth] = [0, 1].map(column => Math.max(...rows.map(row => row[column].length)));
+  return [
+    `context at session start  ${report.tool}  ${report.id}`,
+    ...(report.firstRequest == null ? [] : [`first request: ${tokenCount(report.firstRequest)} tokens`]),
+    ...rows.map(([name, size, holds]) => `${name.padEnd(nameWidth)}  ${size.padStart(sizeWidth)}  ${holds}`.trimEnd()),
+    `sizes are characters of text; ${CONTEXT_COMMANDS[report.tool]} shows this session's context in tokens`,
+    ...(report.note ? [report.note] : []),
+  ].join('\n');
+}
+
 // Superwiki CLI. Lives in a project at docs/.sw/sw.mjs and prints short answers,
 // so agents do not have to read the vault to get them.
-import { spawn } from 'node:child_process';
-import { existsSync, mkdirSync, readFileSync, readdirSync, realpathSync, writeFileSync } from 'node:fs';
-import { createServer } from 'node:http';
-import { basename, dirname, join, resolve as resolvePath } from 'node:path';
-import { fileURLToPath } from 'node:url';
+
+const SESSION_FLAGS = `[--session <id>] [--tool ${SESSION_TOOLS.join('|')}]`;
 
 const HELP = `sw <command> [--docs <dir>] [--json]
 
@@ -333,6 +914,9 @@ const HELP = `sw <command> [--docs <dir>] [--json]
   search <words>  pages and log entries that mention the words, best match first
   next-id <AREA>  next free task id for an area (numbers are never reused)
   lint            structural checks; exit code 1 on errors
+  stats           what the agent session here has cost so far: steps, context and tokens per agent
+  doctor          what that session carried before it read anything: rule files, skill and tool lists
+                  both take ${SESSION_FLAGS} to look at another session of this project
   serve [--open]  start (or reuse) a local viewer at http://127.0.0.1:<port>/ that reads the files live
   snapshot        write docs/.sw/data.js so docs/viewer.html opens as a file, frozen at this moment`;
 
@@ -393,9 +977,9 @@ export function vaultData(docs) {
 // "<" is escaped so page text can never close the script element the viewer loads this with.
 export const dataScript = data => `window.SW_DATA = ${JSON.stringify(data).replace(/</g, '\\u003c')};\n`;
 
-// ---------- Commands ----------
-// Each command gets { docs, vault, args, flags } and returns { data, text, code? }.
-// `data` is what --json prints; `text` is the default output.
+// ---------- Vault commands ----------
+// Each command gets { docs, vault, args, flags } and returns { data, text, code? } or
+// { error, code? }. `data` is what --json prints; `text` is the default output.
 
 function status({ vault }) {
   const s = summary(vault);
@@ -565,6 +1149,31 @@ function snapshot({ docs }) {
   return { data: { files: data.files.length }, text };
 }
 
+// ---------- Session commands ----------
+// These read the record an agent tool keeps of a session, not the vault. Tools file a session
+// under the folder it ran in: the project root, which holds docs/.
+
+function sessionArg(command, { docs, flags }) {
+  if (flags.tool && !SESSION_TOOLS.includes(flags.tool)) return { error: `usage: sw ${command} ${SESSION_FLAGS}` };
+  const root = dirname(docs);
+  const session = findSession(root, { tool: flags.tool, id: flags.session });
+  return session || { error: `no ${flags.tool || 'agent'} session record found for ${root}`, code: 1 };
+}
+
+function statsCommand(ctx) {
+  const session = sessionArg('stats', ctx);
+  if (session.error) return session;
+  const stats = sessionStats(session);
+  return { data: stats, text: formatStats(stats) };
+}
+
+function doctorCommand(ctx) {
+  const session = sessionArg('doctor', ctx);
+  if (session.error) return session;
+  const report = startContext(session);
+  return { data: report, text: formatStartContext(report) };
+}
+
 // ---------- Viewer server ----------
 // A file:// page cannot read local files unless the user picks a folder. Served from localhost it
 // can: every Refresh asks this process, which reads the files as they are now.
@@ -664,20 +1273,25 @@ const COMMANDS = {
   search: { run: searchCommand, needsVault: true },
   'next-id': { run: nextIdCommand, needsVault: true },
   lint: { run: lintCommand, needsVault: true },
+  stats: { run: statsCommand, needsVault: false },
+  doctor: { run: doctorCommand, needsVault: false },
   snapshot: { run: snapshot, needsVault: false },
   serve: { run: serve, needsVault: false },
 };
 
+// Flags that are on or off, and flags that take the next argument as their value.
+const SWITCHES = ['json', 'open', 'foreground'];
+const OPTIONS = ['docs', 'tool', 'session'];
+
+// Anything that is not a known flag is positional, so search words may start with dashes.
 function parseArgs(argv) {
-  const flags = { json: false, open: false, foreground: false, docs: null };
+  const flags = Object.fromEntries([...SWITCHES.map(name => [name, false]), ...OPTIONS.map(name => [name, null])]);
   const positional = [];
   for (let i = 0; i < argv.length; i++) {
-    const arg = argv[i];
-    if (arg === '--docs') flags.docs = argv[++i] || '.';
-    else if (arg === '--json') flags.json = true;
-    else if (arg === '--open') flags.open = true;
-    else if (arg === '--foreground') flags.foreground = true;
-    else positional.push(arg);
+    const name = argv[i].startsWith('--') ? argv[i].slice(2) : null;
+    if (SWITCHES.includes(name)) flags[name] = true;
+    else if (OPTIONS.includes(name)) flags[name] = argv[++i] ?? null;
+    else positional.push(argv[i]);
   }
   return { command: positional[0], args: positional.slice(1), flags };
 }

package/skills/sw-stats/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: sw-stats
+description: Use when the user asks what the current agent session has cost or used (tokens, context size, steps, tool calls, time, per subagent), wants a session summary or statistics, or invokes sw-stats or sw:stats.
+---
+
+# sw-stats
+
+Shows what this session has cost so far: one row for the main session and one for each subagent it started. A script reads the record your tool keeps of the session; you read nothing yourself and write no file.
+
+Run from the project root:
+
+```bash
+node docs/.sw/sw.mjs stats
+```
+
+It reports the session it runs in. For another session of this project, add `--session <id or its first characters>`; to look only at one tool's sessions, `--tool claude|codex|copilot`.
+
+## Answer
+
+1. **Show the table as printed**, in a code block. Do not round, reorder or translate it.
+2. **Add at most three observations**, in the user's language, each one a number from the table and what it means. Pick the ones that apply:
+
+   | In the table | Say |
+   | --- | --- |
+   | one agent's `sent` is most of the total | which agent, and its share. That is where the session's cost is |
+   | an agent's `peak` is several times its `first` | its context grew during the work; `steps` times a large context is what makes `sent` large |
+   | `first` is large, for `main` or for the subagents | every agent starts heavy before it reads anything: rules, memory, and the lists of skills and tools. sw-doctor shows what fills it and what can go |
+   | `cached` is well below the others for one agent | much of what it sent was not served from the cache, which costs more per token. Long pauses do that |
+   | `main` has many `steps` or a `peak` far above its `first` | work is running in the main session that a subagent could do in a clean context |
+
+3. Nothing else: no advice the table does not support, and no price. The table counts tokens; what a token costs depends on the user's plan.
+
+## Columns
+
+So that you can answer a question about them:
+
+- `steps`: model requests. `tools`: tool calls. `min`: minutes between the agent's first and last record.
+- `first`, `peak`: tokens sent with the first request and with the largest one.
+- `sent`: tokens sent, summed over every step. A step sends the whole context again, so this is far larger than `peak`.
+- `cached`: the share of `sent` that was read from the cache.
+- `output`: tokens the model wrote.
+- `-`: the tool's record does not hold that number.
+
+## If it fails
+
+| Output | Do |
+| --- | --- |
+| `unknown command stats` | the project's `docs/.sw/sw.mjs` is older than this skill; offer to run sw-init, which updates it |
+| `no agent session record found` | say so, and name the tool's own command instead: `/cost` or `/context` (Claude Code), `/status` (Codex), `/usage` (Copilot CLI). A session started in a subfolder of the project is recorded under that folder and is not found |
+| a note that Copilot has not written token counts yet | pass the note on; steps and tool calls are still valid |