agent-logs

A monitoring feature for viewing agent container logs and live resource measurements such as CPU, memory, network traffic, and uptime.

In plain words
What is it for?
Use it to inspect logs, view agent and host telemetry, and review centralized JSON log files.
Why use it?
It helps developers investigate running agents and spot operational problems using their logs and metrics.

Agent

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 agents/abilityai/trinity/agent-logs
Clone the repo
git clone --depth 1 https://github.com/Abilityai/trinity
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 441 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00441
Opus 5 $0.00000 $0.00220
Sonnet 5 $0.00000 $0.00088
Haiku 4.5 $0.00000 $0.00044

Measured 2d ago against content hash b9e7c31999ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-logs 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 2d 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.

docs/user-docs/agents/agent-logs.md · 61 lines

What it actually says

Agent Logs and Telemetry

View container logs for debugging and real-time telemetry metrics in the agent header.

How It Works

Logs

  1. Open the agent detail page and click the Logs tab.
  2. A fixed-height scrollable container displays Docker container stdout/stderr.
  3. Logs auto-refresh with smart auto-scroll: new content scrolls to the bottom automatically, but scrolling stops if you scroll up manually.
  4. API: GET /api/agents/{name}/logs
  5. MCP: get_agent_logs(name)

Live Telemetry (Agent Header)

The agent header bar on the detail page displays live resource metrics:

  • CPU -- usage percentage
  • Memory -- usage in MB
  • Network I/O -- bytes in and out
  • Uptime -- how long the agent container has been running

Metrics auto-refresh every 10 seconds.

API: GET /api/agents/{name}/stats

Host Telemetry (Dashboard Header)

Host-level CPU, memory, and disk usage are shown in the Dashboard header.

API: GET /api/telemetry/host

Centralized Logging via Vector

All container logs are captured by the Vector log aggregator and written to structured JSON files:

  • Platform logs: /data/logs/platform.json
  • Agent logs: /data/logs/agents.json

Logs are enriched with container metadata (name, labels). To query agent logs directly:

docker exec trinity-vector sh -c "tail -50 /data/logs/agents.json" | jq .

OpenTelemetry

Claude Code agents export OTel metrics including cost, token usage, and productivity. These metrics are available on the Dashboard.

For Agents

  • Anything an agent writes to stdout or stderr inside its container will appear in the Logs tab and be captured by Vector.
  • Agents do not need to configure logging -- Vector collects logs automatically from all Trinity containers.
  • OTel metrics export is built into the Claude Code agent runtime.

See Also

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. 2d ago First seen · 61 lines · 0 tokens per session scan A b9e7c31999ea

Subscribe to this mod's changes

agent-logs is an agent published in the GitHub repository Abilityai/trinity (496 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 441 tokens. 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens