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.
git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-CodeWrote 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/commands/hermeticormus/libreuiux-claude-code/error-trace)<a href="https://agentmods.dev/commands/hermeticormus/libreuiux-claude-code/error-trace"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreuiux-claude-code/error-trace.svg" alt="Measured on agentmods" 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.00000 | $0.08395 |
| Opus 5 | $0.00000 | $0.04197 |
| Sonnet 5 | $0.00000 | $0.01679 |
| Haiku 4.5 | $0.00000 | $0.00839 |
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, { Copies of this mod
2 near-identical copies found in the catalogue:
- error-trace — 100% identical, 0 lines differ
- error-trace — 100% identical, 0 lines differ
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
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.
- 5d ago First seen · 1,367 lines · 0 tokens per session scan A d05ec7e920d3
error-trace is a command published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (101 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
bootstrap
Verifies and repairs the Claude Code Toolkit installation.
hades-show-traces
Point the user to Charon, Hades' trace explorer.
backprop
Trace a bug back to a spec gap and generate regression tests.
resolve-codeql
Analyze and resolve CodeQL alerts systematically.
performance-audit
Find performance bottlenecks across the stack — queries, rendering, bundle size, memory.
reasoning-chain-validate
Validate the logical consistency and coherence of reasoning chains to ensure sound conclusions.