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 holsee/conjure --skill log-analyzergit clone --depth 1 https://github.com/holsee/conjureWrote 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/holsee/conjure/log-analyzer)<a href="https://agentmods.dev/skills/holsee/conjure/log-analyzer"><img src="https://agentmods.dev/badge/skills/holsee/conjure/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/holsee/conjure/log-analyzer"><img src="https://agentmods.dev/badge/skills/holsee/conjure/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.00045 | $0.00777 |
| Opus 5.5 | $0.00018 | $0.00311 |
| Sonnet 5.5 | $0.00009 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00078 |
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 1mo 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 — 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 formattext- Plain text with patternauto- 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
- Fetch recent logs:
python3 scripts/fetch_logs.py --endpoint "http://api.example.com/logs" \ --limit 500 --output recent_logs.json
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.
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.
- 1mo ago First seen · 118 lines · 45 tokens per session scan A 461a51e19294
log-analyzer is a skill published in the GitHub repository holsee/conjure (10 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 777 once invoked, about $0.0002 per session on Opus 5.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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
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…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.