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 agentmods add skills/jeremydev87/codingbuddy/error-analysisnpx skills add JeremyDev87/codingbuddy --skill error-analysisgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWhat 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 | $0.00029 | $0.01891 |
| Opus 5 | $0.00015 | $0.00945 |
| Sonnet 5 | $0.00006 | $0.00378 |
| Haiku 4.5 | $0.00003 | $0.00189 |
Grade A, and why
error-analysis 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 2d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Analysis
Overview
Errors are information. Stack traces are maps. Reading them carefully reveals root cause faster than guessing.
Core principle: Classify the error before diagnosing it. Different error classes have different diagnostic approaches.
Relationship to systematic-debugging: Use error-analysis to understand WHAT the error is and WHERE it originates. Use systematic-debugging to find WHY it happens and implement the fix.
Iron Law:
READ THE ENTIRE STACK TRACE BEFORE FORMING ANY HYPOTHESIS
The answer is almost always in the error message. Most debugging failures are reading failures.
When to Use
- Encountering a new error message
- Stack trace from production logs
- Unexpected application behavior (silent failure)
- CI/CD pipeline failures
- Type errors, runtime errors, build errors
Error Classification
First, classify the error type:
| Class | Symptoms | Common Causes |
|---|---|---|
| Syntax Error | Fails at parse/compile time | Typo, missing bracket, wrong syntax |
| Type Error | TypeScript compiler error | Wrong type, missing null check |
| Runtime Error | Fails during execution | Null reference, division by zero |
| Logic Error | Wrong output, no crash | Algorithm mistake, off-by-one |
| Network Error | Connection failures | Service down, timeout, firewall |
| Config Error | App won't start | Missing env var, wrong path |
| Concurrency Error | Intermittent failures | Race condition, deadlock |
| Memory Error | Growing memory, crash | Memory leak, large allocation |
Reading Stack Traces
Anatomy of a Stack Trace
Error: Cannot read properties of undefined (reading 'name') ← Error type + message
at RulesService.getRule (/app/src/rules/rules.service.ts:42:18) ← Closest to error
at McpService.handleTool (/app/src/mcp/mcp.service.ts:87:32)
at McpModule.dispatch (/app/src/mcp/mcp.module.ts:23:12) ← Furthest from error
Reading order:
- Error message — WHAT went wrong
- First frame — WHERE it broke (your code closest to error)
- Subsequent frames — HOW we got there (call chain)
- Last frame — ENTRY POINT that triggered the chain
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.
- 2d ago First seen · 252 lines · 29 tokens per session scan A 9bb49134c644
error-analysis is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 1,891 once invoked, about $0.0001 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-30.
Other skills, from other repositories
om-integration-builder
Build integration provider packages for the Open Mercato Integration Marketplace (payment, shipping, data-sync, webhook). Scaffolds the npm package, adapter, credentials, widget injection, webhook processing, health checks, i18n, tests. Triggers on "build integration", "add provider", "integrate with…
om-ds-guardian
Design System Guardian for Open Mercato. Use for frontend UI work, design-system compliance reviews, semantic token migration, hardcoded color or typography cleanup, DS-compliant page scaffolding, and common DS violations such as arbitrary text sizes, raw color classes, or missing shared states. Prefer this skill…
om-integration-tests
Run and create QA integration tests (Playwright TypeScript), including executing the full suite, converting optional markdown scenarios, and generating new tests from specs or feature descriptions. Defers all environment boot/reuse to the om-prepare-test-env skill and attaches to the shared descriptor it writes. Use…
om-create-agents-md
Create or rewrite AGENTS.md files for Open Mercato packages and modules. Use this skill when adding a new package, creating a new module, or when an existing AGENTS.md needs to be created or refactored. Ensures prescriptive tone, the Always/Ask First/Never/Validation Commands boundary structure, MUST-style rules…
om-smart-test
Run only the tests affected by changed code. Use when the user says "run affected tests", "run smart tests", "test only what changed", "run tests for this PR", "run tests for my changes", "selective tests", or asks to run tests without running the full suite.
om-auto-qa-scenarios
Generate a human QA report for a window of merged PRs (date floor, PR-number floor, or default last 7 days) and ship it as a docs-only PR against develop. Groups work into P0/P1/P2 testing routes with click paths, verification points, and risk callouts. Writes markdown + HTML under .ai/analysis/. Hands off to…