error-trace

error-trace is a command for Claude Code from HermeticOrmus/claude-code-game-development. It costs 0 tokens per session (8,395 once invoked), scanned A, a copy of error-trace, MIT.

An error-monitoring command for setting up tracking, alerts, structured logs, error grouping, and performance monitoring in production systems.

In plain words
What is it for?
Use it to review existing error handling, configure monitoring, create alerts, group related failures, and improve production troubleshooting.
Why use it?
It helps teams notice failures quickly and organize enough context to diagnose and fix them.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to review existing error handling, configure monitoring, create alerts, group related failures, and improve production troubleshooting.

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

Made for: Claude Code.

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-trace

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/hermeticormus/claude-code-game-development/error-trace"><img src="https://agentmods.dev/badge/commands/hermeticormus/claude-code-game-development/error-trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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,395 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 100% copy Near-identical to another mod 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.00000 $0.08395
Opus 5 $0.00000 $0.04197
Sonnet 5 $0.00000 $0.01679
Haiku 4.5 $0.00000 $0.00839

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

Security

Grade A, and why

error-trace 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 5d 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.

const response = await fetch(this.config.endpoint, {
Origin

This is a copy

100% identical to error-trace — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/error-debugging/commands/error-trace.md · 1,367 lines

How it starts

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

Error Tracking and Monitoring

You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging, and ensure teams can quickly identify and resolve production issues.

Context

The user needs to implement or improve error tracking and monitoring. Focus on real-time error detection, meaningful alerts, error grouping, performance monitoring, and integration with popular error tracking services.

Requirements

$ARGUMENTS

Instructions

1. Error Tracking Analysis

Analyze current error handling and tracking:

Error Analysis Script

import os
import re
import ast
from pathlib import Path
from collections import defaultdict

class ErrorTrackingAnalyzer:
    def analyze_codebase(self, project_path):
        """
        Analyze error handling patterns in codebase
        """
        analysis = {
            'error_handling': self._analyze_error_handling(project_path),
            'logging_usage': self._analyze_logging(project_path),
            'monitoring_setup': self._check_monitoring_setup(project_path),
            'error_patterns': self._identify_error_patterns(project_path),
            'recommendations': []
        }
        
        self._generate_recommendations(analysis)
        return analysis
    
    def _analyze_error_handling(self, project_path):
        """Analyze error handling patterns"""
        patterns = {
            'try_catch_blocks': 0,
            'unhandled_promises': 0,
            'generic_catches': 0,
            'error_types': defaultdict(int),
            'error_reporting': []
        }
        
        for file_path in Path(project_path).rglob('*.{js,ts,py,java,go}'):
            content = file_path.read_text(errors='ignore')
            
            # JavaScript/TypeScript patterns
            if file_path.suffix in ['.js', '.ts']:
                patterns['try_catch_blocks'] += len(re.findall(r'try\s*{', content))
                patterns['generic_catches'] += len(re.findall(r'catch\s*\([^)]*\)\s*{\s*}', content))
                patterns['unhandled_promises'] += len(re.findall(r'\.then\([^)]+\)(?!\.catch)', content))
            
            # Python patterns
            elif file_path.suffix == '.py':
                try:
                    tree = ast.parse(content)
                    for node in ast.walk(tree):
                        if isinstance(node, ast.Try):
                            patterns['try_catch_blocks'] += 1
                            for handler in node.handlers:
                                if handler.type is None:
                                    patterns['generic_catches'] += 1
                except:
                    pass
        
        return patterns
    
    def _analyze_logging(self, project_path):
        """Analyze logging patterns"""
        logging_patterns = {
            'console_logs': 0,
            'structured_logging': False,
            'log_levels_used': set(),
            'logging_frameworks': []
        }
        
        # Check for logging frameworks
        package_files = ['package.json', 'requirements.txt', 'go.mod', 'pom.xml']
        for pkg_file in package_files:
            pkg_path = Path(project_path) / pkg_file
            if pkg_path.exists():
                content = pkg_path.read_text()
                if 'winston' in content or 'bunyan' in content:
                    logging_patterns['logging_frameworks'].append('winston/bunyan')
                if 'pino' in content:
                    logging_patterns['logging_frameworks'].append('pino')
                if 'logging' in content:
                    logging_patterns['logging_frameworks'].append('python-logging')
                if 'logrus' in content or 'zap' in content:
                    logging_patterns['logging_frameworks'].append('logrus/zap')
        
        return logging_patterns

Read the full file on GitHub · 1,367 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. 5d ago First seen · 1,367 lines · 0 tokens per session scan A d05ec7e920d3

Subscribe to this mod's changes

error-trace is a command published in the GitHub repository HermeticOrmus/claude-code-game-development (62 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 8,395 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to error-trace, differing in 0 lines, and is treated as a copy.