error-analysis

error-analysis is a command for Claude Code from HermeticOrmus/LibreUIUX-Claude-Code. It costs 10 tokens per session (8,287 once invoked), scanned A, original, MIT.

A workflow for investigating errors across development and production, including stack traces, logs, incidents, and failures involving multiple services.

In plain words
What is it for?
Use it to classify errors, analyze logs and traces, investigate production incidents, improve error handling, and plan corrective measures.
Why use it?
It helps connect symptoms to root causes and identify steps that can prevent similar incidents.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the error-debugging plugin — 3 commands shipped together

Good fit Use it to classify errors, analyze logs and traces, investigate production incidents, improve error handling, and plan corrective measures.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hermeticormus/libreuiux-claude-code/error-analysis
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.

Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code

Made for: Claude Code.

Or install error-debugging, the plugin that ships this one along with the rest of its 3 commands.

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 error-analysis

README.md
[![agentmods](https://agentmods.dev/badge/commands/hermeticormus/libreuiux-claude-code/error-analysis/github.svg)](https://agentmods.dev/commands/hermeticormus/libreuiux-claude-code/error-analysis)
Your own site
<a href="https://agentmods.dev/commands/hermeticormus/libreuiux-claude-code/error-analysis"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreuiux-claude-code/error-analysis/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.

agentmods 80×15 button for error-analysis

Your own site · 80×15
<a href="https://agentmods.dev/commands/hermeticormus/libreuiux-claude-code/error-analysis"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreuiux-claude-code/error-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 8,287 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00010 $0.08287
Opus 5.5 $0.00004 $0.03315
Sonnet 5.5 $0.00002 $0.01657
Haiku 4.5 $0.00001 $0.00829

Measured 19d ago against content hash 785d1df80703, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

error-analysis scanned grade A with 1 finding 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 19d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

return axios.post(url, data, {
Origin

Copies of this mod

2 near-identical copies found in the catalogue:

plugins/error-debugging/commands/error-analysis.md · 1,159 lines

How it starts

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

Error Analysis and Resolution

You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.

Context

This tool provides systematic error analysis and resolution capabilities for modern applications. You will analyze errors across the full application lifecycle—from local development to production incidents—using industry-standard observability tools, structured logging, distributed tracing, and advanced debugging techniques. Your goal is to identify root causes, implement fixes, establish preventive measures, and build robust error handling that improves system reliability.

Requirements

Analyze and resolve errors in: $ARGUMENTS

The analysis scope may include specific error messages, stack traces, log files, failing services, or general error patterns. Adapt your approach based on the provided context.

Error Detection and Classification

Error Taxonomy

Classify errors into these categories to inform your debugging strategy:

By Severity:

  • Critical: System down, data loss, security breach, complete service unavailability
  • High: Major feature broken, significant user impact, data corruption risk
  • Medium: Partial feature degradation, workarounds available, performance issues
  • Low: Minor bugs, cosmetic issues, edge cases with minimal impact

By Type:

  • Runtime Errors: Exceptions, crashes, segmentation faults, null pointer dereferences
  • Logic Errors: Incorrect behavior, wrong calculations, invalid state transitions
  • Integration Errors: API failures, network timeouts, external service issues
  • Performance Errors: Memory leaks, CPU spikes, slow queries, resource exhaustion
  • Configuration Errors: Missing environment variables, invalid settings, version mismatches
  • Security Errors: Authentication failures, authorization violations, injection attempts

By Observability:

  • Deterministic: Consistently reproducible with known inputs
  • Intermittent: Occurs sporadically, often timing or race condition related
  • Environmental: Only happens in specific environments or configurations
  • Load-dependent: Appears under high traffic or resource pressure

Read the full file on GitHub · 1,159 lines

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. 19d ago Changed · +5 lines · +10 tokens per session 785d1df80703
  2. 1mo ago First seen · 1,154 lines · 0 tokens per session scan A 9e8f3cd0b0bd

Subscribe to this mod's changes

error-analysis is a command published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (115 stars, last pushed 15d ago), licensed MIT. It adds 10 tokens to every session and 8,287 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.