logs

A command for viewing logs from the services in a configured fleet. It can read local log files or retrieve logs from Kubernetes, a system for running services in containers.

In plain words
What is it for?
Use it to inspect all services or one named service, search for text, show a chosen number of lines, stream new entries, or read Kubernetes logs.
Why use it?
It avoids opening each service's logs separately and can combine output from local and in-cluster services. You can filter, limit, or continuously follow the results.

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/talayash/spring-fleet/logs
Clone the repo
git clone --depth 1 https://github.com/talayash/spring-fleet
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 368 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.00038 $0.00368
Opus 5 $0.00019 $0.00184
Sonnet 5 $0.00008 $0.00074
Haiku 4.5 $0.00004 $0.00037

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

Security

Grade A, and why

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.

commands/logs.md · 28 lines

What it actually says

Show fleet logs.

Input: $ARGUMENTS — optional service name (default: all), plus optional --grep, --lines, --follow, --k8s.

Steps:

  1. Locate spring-fleet.config.json (cwd, else suggest /fleet-init).
  2. Run the aggregator, passing through the relevant flags:
    python "${CLAUDE_PLUGIN_ROOT}/scripts/tail_logs.py" --config ./spring-fleet.config.json [--service NAME] [--grep TEXT] [--lines N] [--follow] [--k8s]
    
    • If a bare service name was given in $ARGUMENTS, pass it as --service.
    • all or empty → all services.
    • --k8s falls back to kubectl logs -l <podSelectorTemplate> for any service whose file-based log is missing. Requires a k8s block in the config (namespace + optional context + podSelectorTemplate). mirrord users get this for free: the local service runs against the shared cluster, the other services log to stdout in-cluster, kubectl reads them.
  3. Present the tagged, aggregated output ([service/k8s] for kubectl-sourced lines). For --follow, stream until interrupted.
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 · 28 lines · 0 tokens per session scan A 40cce817cc5a

Subscribe to this mod's changes

logs is a command published in the GitHub repository talayash/spring-fleet (2 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 368 once invoked, about $0.0002 per session on Opus 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-31.