traces

traces is a command for Claude Code from Galbaz1/video-research-mcp. It costs 13 tokens per session (917 once invoked), scanned A, original, MIT.

A command for inspecting MLflow traces from Gemini tool calls. MLflow is a system for recording and reviewing machine-learning runs, including their timing and status.

In plain words
What is it for?
Use it to list recent traces, inspect selected fields, and debug or evaluate calls made by the video-research MCP service.
Why use it?
It helps investigate failed or slow calls without dumping large prompts, responses, video links, or other trace data.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Part of the gr plugin — 27 skills, 17 commands, 7 agents shipped together

Good fit Use it to list recent traces, inspect selected fields, and debug or evaluate calls made by the video-research MCP service.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/galbaz1/video-research-mcp/traces
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.

Clone the repo
git clone --depth 1 https://github.com/Galbaz1/video-research-mcp

Made for: Claude Code.

Or install gr, the plugin that ships this one along with the rest of its 27 skills, 17 commands, 7 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for traces

README.md
[![agentmods](https://agentmods.dev/badge/commands/galbaz1/video-research-mcp/traces/github.svg)](https://agentmods.dev/commands/galbaz1/video-research-mcp/traces)
Your own site
<a href="https://agentmods.dev/commands/galbaz1/video-research-mcp/traces"><img src="https://agentmods.dev/badge/commands/galbaz1/video-research-mcp/traces/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for traces

Your own site · 80×15
<a href="https://agentmods.dev/commands/galbaz1/video-research-mcp/traces"><img src="https://agentmods.dev/badge/commands/galbaz1/video-research-mcp/traces.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 917 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00013 $0.00917
Opus 5.5 $0.00005 $0.00367
Sonnet 5.5 $0.00003 $0.00183
Haiku 4.5 $0.00001 $0.00092

Measured 20d ago against content hash bb7c1be789aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

traces scanned grade A with 0 findings 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 20d ago.

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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/traces.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Traces: $ARGUMENTS

Query and debug MLflow traces captured from video-research-mcp Gemini API calls.

Prerequisites

The MLflow tracking server must be running. If tools are unavailable or connection is refused:

MLFLOW_TRACKING_URI=http://127.0.0.1:5001 mlflow server --port 5001

Then restart Claude Code to reconnect the mlflow-mcp MCP server.

Default Experiment

Use the configured experiment name (video-research-mcp by default). Resolve its ID through an available experiment lookup or the operator; search_traces requires the ID. Do not assume experiment 0.

Context Discipline (mandatory)

  • Always use extract_fields — never pull full traces. Gemini traces contain large payloads (video URIs, cached content, full prompts/responses).
  • Keep output compact: target <= 300 tokens for overview, expand on detail requests.
  • Never print raw JSON blobs or full span attributes.

Argument Routing

No arguments (empty $ARGUMENTS)

Show a recent traces overview:

search_traces({
  experiment_id: "<resolved>",
  max_results: 10,
  extract_fields: "info.trace_id,info.state,info.execution_duration_ms,info.request_time,info.request_preview"
})

Present as a compact table: trace ID (short), status, duration, time, and request preview.

errors

Filter for failed traces:

search_traces({
  experiment_id: "<resolved>",
  filter_string: "status='ERROR'",
  max_results: 20,
  extract_fields: "info.trace_id,info.state,info.execution_duration_ms,info.request_time,info.request_preview"
})

slow

Filter for traces over 5 seconds:

search_traces({
  experiment_id: "<resolved>",
  filter_string: "execution_time_ms > 5000",
  max_results: 20,
  extract_fields: "info.trace_id,info.execution_duration_ms,info.request_time,info.request_preview,data.spans.*.name"
})

Trace ID (starts with tr- or is a hex string)

Get trace detail:

get_trace({
  trace_id: "<id>",
  extract_fields: "info.*,data.spans.*.name,data.spans.*.status_code,data.spans.*.start_time_unix_nano,data.spans.*.end_time_unix_nano"
})

Read the full file on GitHub · 116 lines

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. 20d ago Changed bb7c1be789aa
  2. 26d ago Changed · -1 lines a5c42ef4fa73
  3. 1mo ago First seen · 117 lines · 13 tokens per session scan A afeb6932b0c5

Subscribe to this mod's changes

traces is a command published in the GitHub repository Galbaz1/video-research-mcp (23 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 917 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.