log-analyzer

log-analyzer is a skill for Claude Code, Codex from holsee/conjure. It costs 45 tokens per session (777 once invoked), scanned A, original, Apache-2.0.

A tool for collecting, parsing, summarising, and diagnosing application logs. Logs are records that software writes about events, warnings, and errors while it runs.

In plain words
What is it for?
Use it to fetch logs from a REST API, filter them by time or severity, parse JSON or text files, and analyse error patterns and statistics.
Why use it?
It brings log retrieval and analysis into one workflow, making production problems easier to investigate from recorded evidence.

Skill for Claude CodeCodex

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 skills/holsee/conjure/log-analyzer
Any agent
npx skills add holsee/conjure --skill log-analyzer
Clone the repo
git clone --depth 1 https://github.com/holsee/conjure

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for log-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/skills/holsee/conjure/log-analyzer.svg)](https://agentmods.dev/skills/holsee/conjure/log-analyzer)
Your own site
<a href="https://agentmods.dev/skills/holsee/conjure/log-analyzer"><img src="https://agentmods.dev/badge/skills/holsee/conjure/log-analyzer.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 777 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.00045 $0.00777
Opus 5 $0.00023 $0.00388
Sonnet 5 $0.00009 $0.00155
Haiku 4.5 $0.00005 $0.00078

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

Security

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 5d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/analyze.py, scripts/fetch_logs.py, scripts/parse_logs.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

priv/skills/log-analyzer/SKILL.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Log Analyzer Skill

A production monitoring skill for fetching, analyzing, and diagnosing issues from application logs.

Available Scripts

1. Fetch Logs (fetch_logs.py)

Fetches logs from a REST API endpoint.

# Fetch last 100 logs
python3 scripts/fetch_logs.py --endpoint "http://localhost:8080/api/logs" --limit 100

# Fetch logs with time range
python3 scripts/fetch_logs.py --endpoint "http://localhost:8080/api/logs" \
  --start "2024-01-15T00:00:00" --end "2024-01-15T23:59:59"

# Fetch logs by severity
python3 scripts/fetch_logs.py --endpoint "http://localhost:8080/api/logs" \
  --level ERROR

Options:

  • --endpoint - REST API URL for logs (required)
  • --limit - Maximum number of logs to fetch (default: 100)
  • --start - Start time (ISO 8601 format)
  • --end - End time (ISO 8601 format)
  • --level - Filter by log level (DEBUG, INFO, WARN, ERROR)
  • --output - Output file (default: stdout)

2. Parse Logs (parse_logs.py)

Parses log files in various formats.

# Parse JSON logs
python3 scripts/parse_logs.py --format json logs.json

# Parse text logs with pattern
python3 scripts/parse_logs.py --format text --pattern "%(timestamp)s %(level)s %(message)s" app.log

# Parse and filter by level
python3 scripts/parse_logs.py logs.json --level ERROR

Supported Formats:

  • json - JSON lines format
  • text - Plain text with pattern
  • auto - Auto-detect format

3. Analyze Logs (analyze.py)

Analyzes logs for patterns, errors, and anomalies.

# Full analysis
python3 scripts/analyze.py logs.json

# Error analysis only
python3 scripts/analyze.py logs.json --errors-only

# Generate summary
python3 scripts/analyze.py logs.json --summary

# Find patterns
python3 scripts/analyze.py logs.json --patterns

Analysis Types:

  • Error frequency and patterns
  • Response time anomalies
  • Request volume trends
  • Common error messages
  • Suggested diagnostics

Example Workflow

  1. Fetch recent logs:
    python3 scripts/fetch_logs.py --endpoint "http://api.example.com/logs" \
      --limit 500 --output recent_logs.json
    

Read the full file on GitHub · 118 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 5d ago First seen · 118 lines · 45 tokens per session scan A 461a51e19294

Subscribe to this mod's changes

log-analyzer is a skill published in the GitHub repository holsee/conjure (10 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 777 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens