Borrowing it
Nothing to install: this file belongs to jtmoon79/super-speedy-syslog-searcher. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jtmoon79/super-speedy-syslog-searcher/main/.claude/skills/s4-log-search/SKILL.mdgit clone --depth 1 https://github.com/jtmoon79/super-speedy-syslog-searcherWrote 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.
[](https://agentmods.dev/skills/jtmoon79/super-speedy-syslog-searcher/s4-log-search)<a href="https://agentmods.dev/skills/jtmoon79/super-speedy-syslog-searcher/s4-log-search"><img src="https://agentmods.dev/badge/skills/jtmoon79/super-speedy-syslog-searcher/s4-log-search/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.
<a href="https://agentmods.dev/skills/jtmoon79/super-speedy-syslog-searcher/s4-log-search"><img src="https://agentmods.dev/badge/skills/jtmoon79/super-speedy-syslog-searcher/s4-log-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00067 | $0.02632 |
| Opus 5 | $0.00034 | $0.01316 |
| Sonnet 5 | $0.00013 | $0.00526 |
| Haiku 4.5 | $0.00007 | $0.00263 |
Grade B, and why
s4-log-search scanned grade B with 2 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 12d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -LsSf 'https://raw.githubusercontent.com/jtmoon79/super-speedy-syslog-searcher/main/tools/s4-easy-install.sh' | sh Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -LsSf 'https://raw.githubusercontent.com/jtmoon79/super-speedy-syslog-searcher/main/tools/s4-easy-install.sh' | sh How it starts
The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
s4 Log Search
Use super-speedy-syslog-searcher, s4, to speedily search and merge log messages by interpreted datetime across many log files, directories, compressed files, archives, and binary log formats. The user must have s4 installed. They can use s4-easy-install to quickly install s4.
s4 is strongest when an incident time or datetime window is known and the useful clues may be scattered across log files. It produces a datetime-sorted view across inputs.
First Checks
When shell access is available, verify the binary before relying on it:
command -v s4
s4 --version
For .asl, .etl, .odl, .aodl, .odlgz, or .odlsent files, s4 may require its Python environment to exist. If those formats fail, suggest running:
s4 --venv
If s4 is unavailable, ask the user to install it or provide the path to the binary.
Installation
Unix
On Unix, use the POSIX-compliant Unix shell script s4-easy-install.sh.
curl -LsSf 'https://raw.githubusercontent.com/jtmoon79/super-speedy-syslog-searcher/main/tools/s4-easy-install.sh' | sh
Windows
On Windows, run the PowerShell script s4-easy-install.ps1
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
Invoke-WebRequest -Uri 'https://raw.githubusercontent.com/jtmoon79/super-speedy-syslog-searcher/main/tools/s4-easy-install.ps1' `
-OutFile s4-easy-install.ps1
.\s4-easy-install.ps1
Core Workflow
- Identify log inputs: files, directories, or a list of paths from another command.
- Identify the time window. If the user only gives symptoms, ask for the incident time, timezone, host timezone, and how wide a window to inspect.
- Decide timezone handling. Use
-twhen log messages or datetime filters lack timezone information and the source timezone matters. - Choose output prefixes. For multi-file analysis, prefer path or filename prefixes; for downstream parsing, use deterministic prepended fields.
- Run
s4, inspect the merged timeline, then widen or narrow the window. - Use other tools after
s4when content filtering is needed.s4filters by datetime, not by message regex or literal text.
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.
- 12d ago First seen · 238 lines · 67 tokens per session scan B d49ac67a0dd5
s4-log-search is a skill published in the GitHub repository jtmoon79/super-speedy-syslog-searcher (59 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 2,632 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
traceway
Operate a Traceway observability instance through the traceway CLI: log in, query exceptions, logs, endpoints, and metrics, and debug production issues down to root cause. Use when the user invokes /traceway with a subcommand, e.g. "/traceway login", "/traceway debug issue ", "/traceway what's broken in prod", or…
analyze-logs
Analyze application logs from the .evlog/logs/ directory. Use when debugging errors, investigating slow requests, understanding request patterns, or answering questions about application behavior. Reads structured NDJSON wide events written by evlog's file system drain.
gcp-cloud-logging
Google Cloud Logging — log search, VPC flow logs, firewall logs, audit logs, log buckets and views. Use when searching GCP logs, investigating denied VPC flow traffic, checking who deleted a VM, analyzing firewall rule hits, or troubleshooting a GCP application error.
monitoring-observability
Monitoring and observability patterns for Prometheus metrics, Grafana dashboards, Langfuse v4 LLM tracing (astype, scorecurrentspan, shouldexportspan, LangfuseMedia), and drift detection. Use when adding logging, metrics, distributed tracing, LLM cost tracking, or quality drift monitoring.
otel-ottl
OpenTelemetry Transformation Language (OTTL) expert. Use when writing or debugging OTTL expressions for any OpenTelemetry Collector component that supports OTTL (processors, connectors, receivers, exporters). Triggers on tasks involving telemetry transformation, filtering, attribute manipulation, data redaction…