@akasecurity/ai-tc-claude-code 0.8.1

package/.claude-plugin/plugin.json

@@ -0,0 +1,7 @@
+{
+  "name": "aka",
+  "version": "0.8.1",
+  "description": "AI Traffic Control — inspect and govern AI prompts in Claude Code. Detection runs locally; events are recorded to a local SQLite store on your machine.",
+  "homepage": "https://github.com/akasecurity/ai-tc",
+  "author": { "name": "AKA Security" }
+}

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 AKA Security
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,46 @@
+# @akasecurity/ai-tc-claude-code — the `aka` plugin for Claude Code
+
+[![npm](https://img.shields.io/npm/v/@akasecurity/ai-tc-claude-code?style=flat-square&labelColor=232F3E&color=00E0B8)](https://www.npmjs.com/package/@akasecurity/ai-tc-claude-code)
+[![Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-232F3E?style=flat-square)](https://github.com/akasecurity/ai-tc/blob/main/LICENSE)
+
+The Claude Code plugin for **[AI Traffic Control](https://github.com/akasecurity/ai-tc)** (`ai-tc`). It hooks into a Claude Code session and inspects its traffic — prompts, tool calls, tool results, file reads — scanning each event against your rule packs and applying inline **warn / redact / block** policies. Every event is recorded to a local SQLite store at `~/.aka/data/aka.db`.
+
+Detection runs entirely on your machine. There's no account and no backend — nothing leaves your computer to be scanned.
+
+## Install
+
+This package is distributed through the **Claude Code plugin marketplace**, not `npm install`. Add the marketplace and install the plugin from inside Claude Code:
+
+```text
+/plugin marketplace add akasecurity/marketplace
+/plugin install aka@akasecurity
+```
+
+Or let the `aka` CLI do it for you:
+
+```bash
+npm install -g @akasecurity/cli
+aka plugins install claude-code
+```
+
+Then run `aka init` to scaffold the local store, and `aka dashboard` to view findings.
+
+## What it registers
+
+The plugin installs Claude Code hooks that run locally with no `node_modules`, and fail open (a hook error never breaks your session):
+
+- **SessionStart** — snapshot the session context.
+- **UserPromptSubmit** — scan prompts before they reach the model.
+- **PreToolUse** — scan tool inputs (Bash, Edit, Write, WebFetch) before they run.
+- **PostToolUse** — scan tool outputs and file reads (Bash, Read, WebFetch) after they return.
+- **Stop** — reconcile token usage and finalize the session record.
+
+It also adds slash commands for reports and setup (`/aka:health`, `/aka:findings`, `/aka:dashboard`, and more).
+
+## Docs
+
+Full documentation and the built-in detection catalog live at **[akasecurity.github.io/ai-tc-docs](https://akasecurity.github.io/ai-tc-docs/)**.
+
+## License
+
+[Apache-2.0](https://github.com/akasecurity/ai-tc/blob/main/LICENSE)

package/commands/audit.md

@@ -0,0 +1,19 @@
+---
+description: Show AKA's recent enforcement decisions
+---
+
+# AKA audit
+
+Run the read script and show the user its output **exactly as printed**. The
+script already prints its content inside a Markdown code fence — reproduce that
+verbatim and do **not** add another code fence, strip the fence, or reformat it.
+The fence is required: it is a space-aligned monospace table that Markdown would
+otherwise collapse. Do not reformat or re-narrate the rows.
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/query.js" audit
+```
+
+This is the decision log: the most recent detections from `~/.aka/data/aka.db`
+with the action AKA took (block / redact / warn / allow), the rule, and where it
+fired (source tool + event kind). It is read-only.

package/commands/dashboard.md

@@ -0,0 +1,26 @@
+---
+description: Launch the AKA web dashboard in your browser (reads your local store)
+---
+
+# AKA dashboard
+
+Launch the AKA web dashboard and relay the short status the script prints **as-is**.
+The command returns immediately: it starts the dashboard server in the background
+and it opens in the browser once ready, so a lack of further output is **not** an
+error — do not wait on it or re-run it. If the script prints install guidance (the
+`aka` CLI isn't installed), relay that verbatim.
+
+If the user asked for a specific port, pass `--port <N>` through unchanged;
+otherwise run it with no arguments.
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/dashboard.js" [--port <N>]
+```
+
+This mirrors the `aka dashboard` CLI command: it serves the OSS web-ui against
+your local store at `~/.aka/data` (no backend) and opens
+`http://localhost:4319/security`. The web server is bundled in the
+`@akasecurity/cli` package — the plugin ships no server of its own — so the
+launcher delegates to the `aka` CLI and, if it isn't installed, prints how to get
+it. For the terminal-only read surfaces, use `/aka:health`, `/aka:findings`,
+`/aka:recommend`, `/aka:audit` or `/aka:tokens` instead.

package/commands/detections.md

@@ -0,0 +1,30 @@
+---
+description: List installed AKA detection packs, versions, and available updates
+---
+
+# AKA detections
+
+Run the read script and show the user its output **exactly as printed**. The
+script already prints its content inside a Markdown code fence — reproduce that
+verbatim and do **not** add another code fence, strip the fence, or reformat it.
+The fence is required: it is a space-aligned monospace table that Markdown would
+otherwise collapse. Do not reformat the columns or restate each row.
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/query.js" detections
+```
+
+This lists the detection packs installed in `~/.aka/data/aka.db` — one row per
+pack with its installed version, the latest version this plugin ships, rule
+count, enabled state, assigned enforcement policy, and whether an update is
+available. These packs are what the plugin actually scans with.
+
+Detection updates are **never applied automatically** — a plugin upgrade only
+records what's newly available; the installed packs keep running unchanged
+until the user updates them. This command is strictly **read-only**: do not
+apply, enable, disable, or re-policy a detection from here. If the user wants
+to update, tell them to run one of these themselves in a terminal:
+
+- `aka detections update --all` — update every pack
+- `aka detections update <pack-id>` — update one pack
+- `aka dashboard` → Detections → **Update** — review and apply in the dashboard

package/commands/exceptions.md

@@ -0,0 +1,26 @@
+---
+description: List active AKA detection exceptions (masked) from the local store
+---
+
+# AKA exceptions
+
+Run the read script and show the user its output **exactly as printed**. The
+script already prints its content inside a Markdown code fence — reproduce that
+verbatim and do **not** add another code fence, strip the fence, or reformat it.
+The fence is required: it is a space-aligned monospace table that Markdown would
+otherwise collapse. Do not reformat the columns or restate each row.
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/query.js" exceptions
+```
+
+This lists the **active** detection exceptions from `~/.aka/data/aka.db` — the
+masked value, rule, scope, relative expiry, use count, and who granted it. The
+approved value is never stored, only a keyed fingerprint and a masked preview.
+
+This command is strictly **read-only**. Do not offer to create, approve, or
+revoke an exception from here — creation and revocation happen only in a
+terminal, out-of-band, via the `aka` CLI (`aka exception approve`,
+`aka exception revoke <id>`; see `aka exception --help`). If the user asks you
+to grant or revoke one, tell them to run those commands themselves in a
+terminal instead.

package/commands/findings.md

@@ -0,0 +1,23 @@
+---
+description: List recent AKA findings (masked) from the local store
+---
+
+# AKA findings
+
+Run the read script and show the user its output **exactly as printed**. The
+script already prints its content inside a Markdown code fence — reproduce that
+verbatim and do **not** add another code fence, strip the fence, or reformat it.
+The fence is required: it is a space-aligned monospace table that Markdown would
+otherwise collapse. Do not reformat the columns or restate each row.
+
+If the user asked to filter by severity — e.g. `--critical`, `--high`,
+`--medium`, `--low`, or `--severity <level>` — pass that flag through to the
+script unchanged. Otherwise run it with no flag.
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/query.js" findings [--severity <critical|high|medium|low>]
+```
+
+This lists the most recent findings from `~/.aka/data/aka.db` with their rule,
+category, severity, action taken, and the **masked** match (raw secrets are
+never stored), narrowed to one severity when a filter is given. It is read-only.

package/commands/health.md

@@ -0,0 +1,20 @@
+---
+description: Show AKA detection activity and local security posture
+---
+
+# AKA health
+
+Run the read script and show the user its output **exactly as printed**. The
+script already prints its content inside a Markdown code fence — reproduce that
+verbatim and do **not** add another code fence, strip the fence, or reformat it.
+The fence is required: it is space-aligned monospace (gauges, bars, a 7-day chart)
+that Markdown would otherwise collapse. Do not reformat or summarize the table;
+you may add at most one short sentence of context after it.
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/query.js" health
+```
+
+This reads the local store at `~/.aka/data/aka.db` (detection activity, action
+breakdown, category coverage, last 7 days). It is read-only. If the store is
+empty, the script says so — relay that as-is; nothing is wrong.

package/commands/recommend.md

@@ -0,0 +1,21 @@
+---
+description: Surface AKA's top recommendations from recent findings
+---
+
+# AKA recommend
+
+Run the read script and show the user its output **exactly as printed**. The
+script already prints its content inside a Markdown code fence — reproduce that
+verbatim and do **not** add another code fence, strip the fence, or reformat it.
+The fence is required: the output is space-aligned monospace whose lines start
+with characters like `1.` and `●`; shown unfenced, Markdown collapses the
+indentation and turns those into auto-numbered lists and bullets. You may expand
+on the suggested next steps if the user asks, but lead with the output as-is.
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/query.js" recommend
+```
+
+This groups recent findings by category (ranked by severity, then frequency) and
+prints a plain-language next step for each. It is read-only over
+`~/.aka/data/aka.db`.

package/commands/scan.md

@@ -0,0 +1,69 @@
+---
+description: Scan working-tree source files for code security flaws
+---
+
+# AKA scan
+
+## Single-repo scan (default)
+
+Run the worktree scan script and show the user its output **exactly as printed**.
+The script already prints its content inside a Markdown code fence — reproduce
+that verbatim and do **not** add another code fence, strip the fence, or reformat it.
+The fence is required: it is space-aligned monospace that Markdown would otherwise
+collapse.
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/filescan.js" --dir "${PWD}"
+```
+
+This scans all source files (`.ts`, `.js`, `.py`, `.java`, `.rb`, `.cs`, `.go`,
+`.rs`, `.php`, and more) under the current project directory for insecure code
+patterns — SQL injection, command injection, XSS, insecure deserialization, weak
+cryptography, hardcoded credentials, dev-mode configuration leaks, and other
+OWASP Top 10 issues.
+
+Results are recorded to the local store (`~/.aka/data/aka.db`) and are visible
+via `/findings`. Re-running `/aka:scan` is safe — files whose content has already
+been recorded are skipped.
+
+Files excluded by the repo's `.gitignore` are **still scanned** — local scratch
+and generated files are a common place for real secrets to hide — but their
+findings are marked as coming from gitignored content and reported as
+informational in the summary.
+
+To exclude paths from scanning entirely, add a `.akaignore` file (gitignore
+syntax, any directory level). Unlike `.gitignore`, `.akaignore` is a **hard
+skip**: matching files are never read and produce no findings. A negation also
+re-includes a directory the scanner skips by default — e.g. `!vendor/` scans
+first-party code living under `vendor/`.
+
+## Multi-repo scan (opt-in)
+
+To scan **all git repositories** found under the current directory (up to 4
+directory levels deep), use the `--discover` flag:
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/filescan.js" --discover
+```
+
+To search from a different directory, pass `--root` (and optionally `--depth`):
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/filescan.js" --discover --root ~/projects --depth 3
+```
+
+Discovery walks the filesystem from the search root looking for `.git`
+directories. It skips large system directories (`Library`, `node_modules`, etc.)
+and stops recursing once a repo root is found (submodules are not separately
+enumerated). The output shows a per-repository breakdown in addition to the
+aggregate totals.
+
+**Scope confirmation:** `--discover` never sweeps the home directory implicitly —
+the default root is the current directory. Before passing a `--root` outside the
+current project (especially `--root ~`, the whole-machine sweep), tell the user
+what will be read and ask for explicit confirmation. Do not assume consent from
+a generic "scan everything" phrasing without naming the scope.
+
+Deduplication is global across all repos in a single `--discover` run — a file
+whose content hash is already recorded (from a previous scan or a live hook
+capture) is skipped regardless of which repo it lives in.

package/commands/setup.md

@@ -0,0 +1,143 @@
+---
+description: Set up the AKA Control Plane plugin — redaction handling and historical access
+---
+
+# AKA setup wizard
+
+You are onboarding the AKA Control Plane plugin for this machine. AKA works
+fully locally with **zero backend and zero Docker**: detection runs in-process
+and findings persist to a local SQLite store at `~/.aka/data/aka.db`. This
+wizard records two preferences. Ask the questions in order, then save once.
+
+## 0. Show the intro card
+
+Run the intro script and show the user its output **exactly as printed** — it is a
+space-aligned monospace card (name, repository, version, what AKA adds). The script
+already prints it inside a Markdown code fence; reproduce that verbatim and do
+**not** add another code fence, strip the fence, or reformat it (unfenced, Markdown
+collapses the indentation and mangles the `●` line). Then continue with the two
+questions below.
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/intro.js" "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json"
+```
+
+## 1. Ask the two questions
+
+Use the **AskUserQuestion** tool — Claude Code's built-in interactive picker — to
+ask both questions. The plugin can't draw its own selectable UI (it can't
+capture keystrokes), so do **not** print a fake option list or ask the user to
+"reply with a number"; let the picker collect the answers.
+
+Ask these two questions (a single AskUserQuestion call with both is fine):
+
+**Sensitive-data handling** — "When AKA detects sensitive data on its way to a model, it should:"
+
+- **Actively redact** → `redact` _(recommended)_ — replace secrets with safe
+  placeholders before the request is sent.
+- **Warn only** → `warn` — flag the request and let the user decide; nothing is
+  modified automatically. (Either mode can be changed per-project later.)
+
+**Historical & memory access** — "Secrets often leak before AKA is installed. May I also review your temp files, agent memory & prior conversation transcripts?"
+
+List **Grant full review** as the first (top) option:
+
+- **Grant full review** → `full` — scan scratch/temp files, agent memory & prior
+  transcripts for leaked secrets (deepest coverage · one-time consent, revocable
+  under Policies).
+- **Current session only** → `session-only` — decline historical access; AKA
+  reviews only what this session already touches. Even if declined, AKA can still
+  review: the **working tree** (all source, config & dotfiles in the repo), **this
+  session** (prompts, tool calls & files Claude reads or writes now), **git
+  history** (commits reachable from HEAD, incl. removed-but-tracked secrets), and
+  **pointed scans** (any path you explicitly hand AKA during a run).
+
+Map the picked labels to the flag values shown above (`redact`/`warn`,
+`full`/`session-only`).
+
+## 2. Save the answers
+
+Run the onboarding writer with the chosen values. Omit a flag to keep its
+default. This validates and persists to `~/.aka/settings/settings.json` (created
+`0600`, owner-only) and stamps the machine as onboarded:
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/onboard.js" --policy <redact|warn> --historical <full|session-only>
+```
+
+## 2.5 Scan history (only if they granted full review)
+
+**Only when the user picked "Grant full review" (`historical=full`)**, run the
+backfill. It sweeps prior Claude Code transcripts (last 30 days, all projects)
+for secrets that leaked before AKA was installed and records them into the local
+store, so they show up in the first-run summary and `/findings`. The scan is
+idempotent — it skips messages already recorded — so re-running `/aka:setup` is
+safe and never duplicates findings. Show its output **exactly as printed** (it
+self-fences; do not add another fence or reformat). Skip this step entirely when
+they chose `session-only`.
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/backfill.js"
+```
+
+## 3. Show the first-run summary
+
+Run the first-run script and show its output **exactly as printed** (the
+install-complete summary with live findings/recommendation counts and the health
+score). The script already prints it inside a Markdown code fence; reproduce that
+verbatim and do **not** add another code fence, strip the fence, or reformat it (it
+is space-aligned monospace that Markdown would otherwise collapse).
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/firstrun.js"
+```
+
+## 3.5 Offer the AKA CLI + local dashboard (opt-in)
+
+Now that the plugin is set up, offer the optional **AKA CLI + local dashboard** —
+a richer, still-fully-local surface over the same `~/.aka` store this plugin
+writes. The plugin works completely on its own; this is additive (and the path to
+future multi-agent support). Use **AskUserQuestion**:
+
+**Add the AKA CLI + dashboard?** — "Install the `aka` CLI for a local web +
+terminal dashboard and on-demand scans? Everything stays on your machine."
+
+- **Yes, install it** _(recommended)_ — adds the `aka` binary: `aka stats`,
+  `aka tui` (terminal dashboard), `aka dashboard` (local web UI), `aka scan`.
+- **Not now** — skip; it can be added anytime with the one-liner below.
+
+If they choose **Yes**, run the bootstrap installer (it ensures Node is available
+and installs the global CLI from the public npm registry). **Ask permission
+before running it**, then run the line for their OS:
+
+```bash
+# macOS / Linux
+curl -fsSL https://raw.githubusercontent.com/akasecurity/ai-tc/cli-latest/tools/installer/install.sh | sh
+
+# Windows (PowerShell)
+irm https://raw.githubusercontent.com/akasecurity/ai-tc/cli-latest/tools/installer/install.ps1 | iex
+```
+
+The one-liner pins to the stable release **tag** (`cli-latest`), never `main` —
+each release points that tag at its published `cli-v*` version, and the bootstrap
+scripts it fetches hold the installer's pinned ref + checksum, so fetching them
+from a mutable branch would defeat the integrity gate. To pin an exact version
+instead, set `AKA_INSTALL_REF=cli-v<version>` before running the line. Until the
+first release is published the one-liner 404s (fail-closed).
+
+After it completes, point them at `aka init` then `aka dashboard`. If they chose
+**Not now**, show the one-liner once so they can add it later, and move on —
+declining keeps the plugin fully functional standalone.
+
+**Fail open.** This install is optional, so it must never derail the session. If
+the installer fails for any reason — Node missing, network/registry error, a
+non-zero exit, or the checksum check rejecting a bad download — briefly report
+what happened, show the one-liner so they can retry later, and continue the
+wizard normally. The plugin is already fully set up and works on its own; a
+failed CLI install changes nothing about that.
+
+## 4. Report the result
+
+- The first-run summary already confirms the saved handling and points at
+  `/health`. Add at most one short sentence: detection runs locally and nothing
+  leaves the machine.