insights

An owner-only command that retrieves an aggregate report about how a Mochi insight server is being used.

In plain words
What is it for?
Reviewing popular tools and MCP servers, error rates, tool combinations, calls per task, task categories, and a ranked list of possible improvements.
Why use it?
It gives the plugin owner a summary of tool usage and errors without exposing message content.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/devzonayed/mochi/insights
Clone the repo
git clone --depth 1 https://github.com/DevZonayed/Mochi
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 233 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00233
Opus 5 $0.00008 $0.00117
Sonnet 5 $0.00003 $0.00047
Haiku 4.5 $0.00002 $0.00023

Measured yesterday against content hash 96db7511c6ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

insights scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsS -H "authorization: Bearer $MOCHI_DASHBOARD_TOKEN" \
plugins/continuum/commands/insights.md · 18 lines

What it actually says

For the plugin owner only. Fetches aggregated, content-free usage insights from the self-hosted ingest server and prints them. Regular users do not have credentials and should use /mochi:telemetry show for their own local view.

  1. Confirm the owner has the dashboard bearer token (or basic-auth) — never hard-code it.
  2. Fetch and pretty-print the summary:
curl -fsS -H "authorization: Bearer $MOCHI_DASHBOARD_TOKEN" \
  https://mochi-insight.nexalance.cloud/v1/summary | python3 -m json.tool

Render the result as: top tools, top MCPs, per-tool error rates, tool co-occurrence, calls-per-task, tools-per-task-category, and the ranked improvement backlog. If the request 401s, the token is missing/wrong; if it times out, check the server health at /v1/health.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 18 lines · 15 tokens per session scan A 96db7511c6ac

Subscribe to this mod's changes

insights is a command published in the GitHub repository DevZonayed/Mochi (3 stars, last pushed 15d ago), licensed MIT. It adds 15 tokens to every session and 233 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.