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 skills add Notysoty/openagentskills --skill error-log-summarizergit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/error-log-summarizer)<a href="https://agentmods.dev/skills/notysoty/openagentskills/error-log-summarizer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/error-log-summarizer.svg" alt="Measured on agentmods" 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.00026 | $0.01777 |
| Opus 5 | $0.00013 | $0.00889 |
| Sonnet 5 | $0.00005 | $0.00355 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
Error Log Summarizer 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 6d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Log Summarizer
What this skill does
This skill directs the agent to ingest raw error logs — from a server, application, CI pipeline, or any other source — and produce a structured, de-duplicated summary. It groups repeated errors, counts occurrences, identifies the most frequent and most severe issues, and provides a root cause hint for each unique error type. The output gives you a clear picture of what's actually wrong without needing to scroll through thousands of log lines.
Use this when you have a dump of logs from a production incident, a CI failure, an error monitoring alert, or a server that's behaving oddly.
How to use
Claude Code / Cline
Copy this file to .agents/skills/error-log-summarizer/SKILL.md in your project root.
Then ask:
- "Use the Error Log Summarizer skill on these logs."
- "Summarize this error output from our production server using the Error Log Summarizer skill."
Paste the raw logs directly into the message, or provide a file path if the logs are in the repo.
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane, then paste your raw logs.
Codex
Paste the logs directly in your message and ask Codex to follow the instructions below.
The Prompt / Instructions for the Agent
When asked to summarize error logs, follow these steps:
Step 1 — Parse and classify each log entry
Read through the entire log. For each line or entry, extract:
- Timestamp (if present)
- Severity level: ERROR, WARN, FATAL, CRITICAL, or inferred from context
- Error message: the actual error text, not the full stack trace
- Source: the file, service, or module where the error originated
- Stack trace identifier: if a stack trace is present, note the top application-code frame (not framework internals)
Step 2 — De-duplicate and group
Group log entries that represent the same underlying error. Two entries are the same error if:
- The error message is identical or differs only in dynamic values (IDs, timestamps, paths)
- They originate from the same source location
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.
- 6d ago First seen · 165 lines · 26 tokens per session scan A 5d7c7f6b0a76
Error Log Summarizer is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 23d ago), licensed MIT. It adds 26 tokens to every session and 1,777 once invoked, about $0.0001 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 skills, from other repositories
log-diagnostic
A log-analysis tool that detects JSON, syslog, and Nginx formats and reports grouped errors, occurrence counts, severity levels, and time distribution. It can filter entries by level or time range and export JSON.
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…
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…
kol-content-monitor
Track what key opinion leaders (KOLs) in your space are posting on LinkedIn and Twitter/X. Surfaces trending narratives, high-engagement topics, and early signals of emerging conversations before they peak. Chains linkedin-profile-post-scraper and twitter-mention-tracker. Use when a marketing team wants to ride trends…
newsletter-signal-scanner
Subscribe to and scan industry newsletters for buying signals, competitor mentions, ICP pain-point language, and market shifts. Parses incoming newsletter emails via AgentMail, matches against keyword campaigns, and delivers a weekly digest of actionable signals. Use when a marketing team wants to turn newsletter…
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.