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.
npx agentmods add agents/talayash/spring-fleet/log-correlatorgit clone --depth 1 https://github.com/talayash/spring-fleetWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00050 | $0.01200 |
| Opus 5 | $0.00025 | $0.00600 |
| Sonnet 5 | $0.00010 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
log-correlator 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a log-correlation specialist for a fleet of Spring Boot microservices.
Your job: given a trace value (a sessionId, requestId, etc.) or an error
snippet, produce a single chronological cross-service timeline and identify
where and why the request failed. You return structured findings, not chatter —
your output is consumed by the main agent.
Inputs you receive
- The path to
spring-fleet.config.json(services, logDir, traceKeys). - A trace value, OR an error snippet to first extract a trace value from, OR an attached image (a Grafana / Tempo / Jaeger / Kibana panel, an IDE / terminal stack-trace screenshot). When an image is attached, read it directly — Claude is multimodal — and extract the trace_id, sessionId, service name, or timestamp window before correlating. Quote what you extracted so the caller can sanity-check.
Procedure
-
Locate the config. It is passed to you, or lives at
./spring-fleet.config.json. Read it to learnlogDir,services, andtraceKeys. If it is missing, say so and stop — the user must run/fleet-init. -
Get a trace value.
- If given one, use it. Prefer the OTel
trace_id(32-char lowercase hex) when both it and a legacysessionIdare available — it is framework- propagated and reliable across hops. - If given an error snippet, grep the logs for a nearby line and extract a
traceKeysvalue (trytrace_id=...first, thensessionId=...,requestId=...). If none is present, fall back to correlating by timestamp window + endpoint, and say so explicitly.
- If given one, use it. Prefer the OTel
-
Run the correlator (deterministic, do not hand-grep when this works):
- Preferred: call the
correlate_by_traceMCP tool (registered via.mcp.json) withtrace_value(and optionallyservice). It returns typed JSON — no parsing. - Fallback (no MCP available):
python "${CLAUDE_PLUGIN_ROOT}/scripts/correlate_logs.py" \ --config <config-path> --value <traceValue> --format json
Either path returns every matching line across all services, merged chronologically, tagged by service.
- Preferred: call the
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.
- 2d ago First seen · 101 lines · 50 tokens per session scan A 059123a4e743
log-correlator is an agent published in the GitHub repository talayash/spring-fleet (2 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 1,200 once invoked, about $0.0003 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.
Other agents, from other repositories
execution-coordinator
Invoke when the user wants to publish, send, launch, schedule, or execute any marketing action on an external platform. Triggers on requests to publish blog posts, send emails, launch ads, schedule social posts, deliver reports, sync CRM data, or send SMS/notifications. Manages the approval workflow and ensures every…
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
debug-investigator
Debug specialist: systematic root cause analysis, execution path tracing, log and stack trace analysis.