@moda-ai/cli 1.55.35 → 1.55.37

package/dist/{prompts-propose-8feadk2t.js → prompts-propose-cbenbk8w.js}

@@ -7,20 +7,20 @@ import {
   formatVerdict,
   rerunWithYes,
   resolvePromptArmSpec
-} from "./cli-602yx84w.js";
-import"./cli-6j8h2ave.js";
-import"./cli-yz8xcpyk.js";
+} from "./cli-xkcy9wns.js";
+import"./cli-npkb08xt.js";
+import"./cli-nzx7rqjs.js";
 import"./cli-mm48br00.js";
-import"./cli-dr6x0zv7.js";
-import"./cli-n2hng3gv.js";
+import"./cli-4d92a450.js";
+import"./cli-cdx6yd7m.js";
 import {
   callControlAPI
-} from "./cli-e23g9ywa.js";
+} from "./cli-s72pph9c.js";
 import {
   resolveApiTenantId,
   shellArg,
   validateConfig
-} from "./cli-99p2jh28.js";
+} from "./cli-wg6e2a1g.js";
 import {
   CliInputError
 } from "./cli-k4tqwah4.js";

package/dist/{provision-y5bdbh4y.js → provision-8c4s6vgg.js}

@@ -1,17 +1,17 @@
 import {
   selectTenantAndCreateKey
-} from "./cli-9bgk5jeh.js";
-import"./cli-97jew729.js";
+} from "./cli-w3ckvma5.js";
+import"./cli-ef9eagsc.js";
 import {
   loadAuthSession
-} from "./cli-9bgnvth2.js";
+} from "./cli-gjzr7jq5.js";
 import {
   stringOption
-} from "./cli-dr6x0zv7.js";
+} from "./cli-4d92a450.js";
 import {
   resolveIngestUrl,
   resolveModaBaseUrl
-} from "./cli-99p2jh28.js";
+} from "./cli-wg6e2a1g.js";
 import {
   CliAuthError
 } from "./cli-k4tqwah4.js";

package/dist/{registry-ctnn8e26.js → registry-qvjyvbk8.js}

@@ -1,13 +1,13 @@
 import {
   assertFlags
-} from "./cli-n2hng3gv.js";
+} from "./cli-cdx6yd7m.js";
 import {
   callControlAPI
-} from "./cli-e23g9ywa.js";
+} from "./cli-s72pph9c.js";
 import {
   explicitOutputMode,
   resolveApiKey
-} from "./cli-99p2jh28.js";
+} from "./cli-wg6e2a1g.js";
 import {
   CliInputError
 } from "./cli-k4tqwah4.js";

package/dist/{skills-96z55tj4.js → skills-z7w5x7jj.js}

@@ -3,14 +3,14 @@ import {
   pullSkills,
   runSkillSync,
   runSkillsCommand
-} from "./cli-k007ztbs.js";
+} from "./cli-wh83c3ss.js";
 import"./cli-qm5b1vck.js";
 import"./cli-rjav0vj1.js";
 import"./cli-hcwdz9sd.js";
-import"./cli-dr6x0zv7.js";
-import"./cli-n2hng3gv.js";
-import"./cli-e23g9ywa.js";
-import"./cli-99p2jh28.js";
+import"./cli-4d92a450.js";
+import"./cli-cdx6yd7m.js";
+import"./cli-s72pph9c.js";
+import"./cli-wg6e2a1g.js";
 import"./cli-k4tqwah4.js";
 import"./cli-ns5fcnkz.js";
 import"./cli-0v6na3yp.js";

package/dist/{sync-drz7req6.js → sync-r32tgpar.js}

@@ -1,24 +1,24 @@
 import {
   runSkillsCommand
-} from "./cli-k007ztbs.js";
+} from "./cli-wh83c3ss.js";
 import"./cli-qm5b1vck.js";
 import"./cli-rjav0vj1.js";
 import"./cli-hcwdz9sd.js";
 import {
   runPromptsCommand
-} from "./cli-6j8h2ave.js";
+} from "./cli-npkb08xt.js";
 import"./cli-mm48br00.js";
 import {
   runHarnessCommand
-} from "./cli-x9cwat4a.js";
+} from "./cli-x605txan.js";
 import"./cli-xq45etg1.js";
 import"./cli-97fnztpy.js";
 import"./cli-cesds766.js";
 import"./cli-qpq84eee.js";
-import"./cli-dr6x0zv7.js";
-import"./cli-n2hng3gv.js";
-import"./cli-e23g9ywa.js";
-import"./cli-99p2jh28.js";
+import"./cli-4d92a450.js";
+import"./cli-cdx6yd7m.js";
+import"./cli-s72pph9c.js";
+import"./cli-wg6e2a1g.js";
 import {
   CliInputError
 } from "./cli-k4tqwah4.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moda-ai/cli",
-  "version": "1.55.35",
+  "version": "1.55.37",
   "description": "CLI for Moda: production monitoring and evals for AI agents.",
   "type": "module",
   "bin": {

package/skills/integration/index.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "moda.skill_index.v1",
-  "bundled_at": "2026-10-17T14:15:17.680Z",
-  "cli_version": "1.55.35",
+  "bundled_at": "2026-10-18T00:25:21.733Z",
+  "cli_version": "1.55.37",
   "skills": [
     {
       "id": "integration-cloudflare-think",

package/skills/moda-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: moda-cli
-version: 3.0.2
+version: 3.0.3
 description: Investigate a production AI agent with the Moda CLI (`moda`) - find where something happened in real traces (traces search, then traces get), check agent health, rank what to fix (investigate, problems), and dig into tool failures, user frustration, and hallucinations. Also prompt registry sync/promote, replays, custom signals, and false-positive marking. Use when the user mentions Moda, production traces or conversations of their agent, agent failures, or asks what to fix.
 ---
 
@@ -10,7 +10,7 @@ description: Investigate a production AI agent with the Moda CLI (`moda`) - find
 run: every message, tool call, and step sharing one `conversation_id` (older
 names: "conversation"; `moda conversations` is an alias of `moda traces list`).
 Analytics commands are read-only. Commands are `moda <noun> <verb>` (`traces`,
-`problems`, `detections`, `review`); older names such as `moda context` still
+`problems`, `detections`, `tools`, `review`); older names such as `moda context` still
 work but warn (`meta.deprecated`), so use the forms below. Detailed guides live
 in `references/`; read one only when the task needs it.
 
@@ -62,6 +62,7 @@ Details: `references/output-protocol.md`.
 | Is the agent healthy? | `moda overview --days-back=7` | `moda investigate` |
 | What to fix first? | `moda investigate` or `moda problems` (free) | `moda problems get <problem_id>`, then `--evidence` / `--traces` |
 | Why is tool T failing? | `moda detections tools` | `moda detections tools <T>` (use each row's `anchor`) |
+| How often is tool T called / what is its schema? | `moda tools list` (every tool: calls, failed calls, success rate; `--sort=failure_rate`) | `moda tools get <T>` (registered schema, observed payload fields, usage over time, top failure categories) |
 | What frustrates users? | `moda detections list --family=frustration --limit=10` | `moda traces get <anchor.conversation_id> --msg-index=<anchor.msg_index>` |
 | Other emotions, laziness, hallucinations | `moda detections list --family=emotion:<f>`, `moda detections list --family=laziness`, `moda detections list --family=hallucination --kind=contradicted` | context on the row's anchor |
 | Read one whole trace | `moda traces get <id> --all` (pages of up to 500 messages) | `moda traces spans <id>` for raw spans |

package/skills/moda-cli/references/commands.md

@@ -27,6 +27,8 @@ Loaded on demand from the moda-cli skill. This table can lag the CLI: `moda <com
 | `moda detections list --family=hallucination` | Grounding detections: contradicted/verified outputs, rule breakdown (`--kind=contradicted\|verified`, `--conversation-id=ID`) |
 | `moda detections tools` | Tool failure overview |
 | `moda detections tools <tool_name>` | Per-tool failure breakdown + examples |
+| `moda tools list` | Tool catalog: every tool called in the window with calls, failed calls, success rate, traces, effect direction, last seen (`--sort=calls\|failure_rate\|failures\|traces\|last_seen`, `--search`, `--direction`, `--limit` 1-200, `--offset`) |
+| `moda tools get <tool_name>` | One tool: call stats, registered description and schema, observed payload fields, usage over time, top failure categories with the newest failure (`--days-back`, `--full`) |
 | `moda problems` | Rank cross-signal Problems by root cause (what to fix first); takes only `--days-back`/`--limit`. Filter by family with `moda problems unexplained --family=F` or `moda problems get <problem_id> --traces --family=F` |
 | `moda problems get <problem_id>` | One Problem: dossier, or `--evidence`/`--reports`/`--traces`/`--feedback` pages (`--conversations` is a legacy alias of `--traces`) (`--limit` 1–50, `--cursor` verbatim keyset token) |
 | `moda problems feedback <problem_id>` | Write: `--action=mark_fixed\|dismiss\|flag_attribution\|rename`. `--reason` required for flag_attribution, optional for dismiss; `--new-name` for rename; `--attribution-id` (UUID) required for flag_attribution |

package/skills/moda-cli/references/dashboard-parity.md

@@ -12,6 +12,7 @@ Writes listed here accept `--dry-run`: it validates the call, prints the exact r
 | Traces list: sort, page | `moda traces --sort=recent\|longest\|slowest --offset=N` |
 | Trace detail: whole transcript | `moda traces get <id> --all` (ordered, with tool calls/results) |
 | Users page / user profile | `moda users [--window --cohort --sort --order --health-status]`, `moda user <id>` |
+| Tool catalog: every tool, its schema and usage | `moda tools list [--sort=calls\|failure_rate\|failures\|traces\|last_seen --search --direction --offset]`, `moda tools get <tool_name>` |
 | Problems: unexplained remainder | `moda problems unexplained [--family=emotion\|tool_failure\|laziness\|… --cursor]` |
 | Reopen a problem marked fixed | `moda problems reopen <problem_id> --reason="…"` (resolved ones return only via re-detection) |
 | Custom signals: create | `moda signals draft --note="…"`, then `moda signals create --name --description --pass-criteria --fail-criteria [--tool-names=a,b]` or `--file=body.json` |

package/skills/moda-cli/references/detections.md

@@ -77,3 +77,43 @@ Examples default to `--limit=5` (max 20). Example text is returned whole; if
 the agent envelope goes over its byte limit, whole trailing examples are
 dropped and `truncation.data.full_output_path` holds every example. Agent output lists the 20 most frequent
 `subtypes` (`subtypes_total` has the full count); `--json` lists all.
+`next_commands` include `moda tools get <tool_name>` for the tool's call
+count, success rate and schema.
+
+### 7. Tool catalog: calls, success rate and schema
+
+`moda detections tools` lists failing tools only. For the call denominator of
+every tool, healthy ones included, and for what a tool takes as input, use the
+Tool catalog (the same figures as the dashboard Tool catalog page):
+
+```bash
+moda tools list                                   # every tool, most called first
+moda tools list --sort=failure_rate --limit=10    # calls, failed calls, success rate
+moda tools list --search=calendar --direction=write
+moda tools get <tool_name>                        # stats, schema, usage, failure categories
+moda tools get <tool_name> --days-back=30 --full  # observed values and inputs uncut
+```
+
+`tools list` pages with `--limit` (1-200, default 25) and `--offset`; when
+`pagination.has_more` is true, `next_commands` holds the next page. Sorts are
+`calls`, `failure_rate`, `failures`, `traces`, `last_seen` (all descending).
+
+`tools get` returns `stats`, `definition.registered` (the description and
+schema pushed with `moda registry push` or added in the dashboard, else `null`),
+`definition.observed_fields` (keys seen in recorded call inputs, with types and
+common values), `usage` (calls and failed calls per day, or per hour under 7
+days), `tool_classes`, `effect_profile`, `failure_categories` and
+`recent_calls`. Each failure category carries `latest_failure`, a
+`context_command` that opens it, and an `examples_command`
+(`moda detections tools <tool_name> --subtype=<category>`). Agent output keeps
+20 observed fields with 3 common values each and 5 recent calls, and cuts
+inputs and sample errors at 200 characters (`*_total` fields give the full
+counts); `--full` keeps everything. The registered schema is never cut. A tool with no calls in the window is
+`not_found`.
+
+Two failure counts, from two sources: `calls`, `failed_calls` and
+`success_rate_pct` count recorded tool receipts (what the catalog shows);
+`stats.failure_detections` and `failure_categories` count classified tool
+failures, the same rows as `moda detections tools`. A call can succeed on its
+receipt and still be classified as a failure (wrong content, a policy block),
+so the second count can be higher. `metric_note` in each response says the same.