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 inbharatai/claude-skills --skill log-analyzergit clone --depth 1 https://github.com/inbharatai/claude-skillsWrote 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/inbharatai/claude-skills/log-analyzer)<a href="https://agentmods.dev/skills/inbharatai/claude-skills/log-analyzer"><img src="https://agentmods.dev/badge/skills/inbharatai/claude-skills/log-analyzer/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/inbharatai/claude-skills/log-analyzer"><img src="https://agentmods.dev/badge/skills/inbharatai/claude-skills/log-analyzer.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.00020 | $0.00393 |
| Opus 5 | $0.00010 | $0.00197 |
| Sonnet 5 | $0.00004 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
log-analyzer 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 7d 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.
What it actually says
Log Analyzer
Overview
Analyze application and infrastructure logs — pattern detection, error clustering, and anomaly identification.
When to Use This Skill
Use Log Analyzer when you need to:
- Work with log analyzer tasks in your project or workflow
- Automate log analyzer operations at scale
- Generate production-quality log analyzer output quickly
Instructions
When this skill is active, Claude will:
- Understand the full context of your log analyzer request
- Apply best practices and conventions for DevOps & Infrastructure
- Produce clean, well-structured, production-ready output
- Explain key decisions and offer alternatives where relevant
Examples
Example 1 — Basic Usage
User: Help me get started with log analyzer.
Claude: I'll walk you through the essential steps for log analyzer in your context...
Example 2 — Advanced Usage
User: I need a production-ready log analyzer setup with full error handling.
Claude: Here's a complete, production-hardened log analyzer implementation...
Guidelines
- Always validate inputs before processing
- Follow the conventions of the target platform or language
- Prefer explicit over implicit — clarity beats cleverness
- Include comments for non-obvious logic
- Suggest tests or validation steps where appropriate
Dependencies
Required: elasticsearch, loki
Platforms
Available on: claude.ai, claude-code, api
Part of the claude-skills collection — 183+ skills for Claude.
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.
- 7d ago First seen · 68 lines · 20 tokens per session scan A 69a8b3b283b0
log-analyzer is a skill published in the GitHub repository inbharatai/claude-skills (33 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 393 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-09-03.
Other skills, from other repositories
incident-postmortem
Incident post-mortem specialist for writing blameless post-mortems, extracting timelines from logs/events, conducting root cause analysis (5-Why, fishbone), classifying severity, and generating tracked action items. ALWAYS use when writing a post-mortem, reviewing an incident, extracting a timeline, performing root…
log-analyzer
Senior-SRE log analysis specialist. Use when investigating incidents from logs, triaging error spikes, extracting timelines, correlating distributed traces, or separating signal from noise across plain-text, JSON (slog/zap), syslog, journald, container, and Kubernetes logs. ALWAYS use when the user asks to "analyze…
systematic-debugging
Use when debugging, diagnosing, or investigating any bug, test failure, flaky test, race condition, unexpected behavior, build failure, production incident, third-party breakage, root cause analysis, or performance regression before proposing fixes.
evidence-driven-debugging
Use during active debugging when you have a hypothesis to test or need to instrument a running system. Activate for keywords like "debug", "instrument", "log", "trace", "breakpoint", "what's happening at runtime", "production behavior". Pair to investigate-root-cause for the doing-it phase. Always record what you…
investigate-root-cause
Use when encountering ANY bug, error, test failure, or unexpected behavior. Activate for keywords like "bug", "error", "failing", "broken", "doesn't work", "unexpected", "crash", "exception", "TypeError", "undefined", stack traces, or any error message. Also trigger when tests fail unexpectedly, when behavior differs…
map-codebase
Use when entering an unfamiliar codebase or area, before making non-trivial changes, when onboarding to a new system, or when planning a refactor that touches multiple modules. Activate for keywords like "explore", "map", "find where", "trace", "how does X work", "what calls Y", "scope of change". Produces an…