error-handler-inspector

error-handler-inspector is an agent for Claude Code from synaptiai/synapti-marketplace. It costs 63 tokens per session (1,876 once invoked), scanned A, original, Apache-2.0.

A code-review agent focused on unhandled errors, missing edge cases, silent failures, and gaps in exception handling.

In plain words
What is it for?
Use it to inspect changed code and report error-handling findings with severity and file-and-line references.
Why use it?
It helps find situations where software can fail without a useful response or where unusual inputs are not handled safely.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

Part of the flow plugin — 33 skills, 20 commands, 10 agents shipped together

Good fit Use it to inspect changed code and report error-handling findings with severity and file-and-line references.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/synaptiai/synapti-marketplace/error-handler-inspector
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/synaptiai/synapti-marketplace

Made for: Claude Code.

Or install flow, the plugin that ships this one along with the rest of its 33 skills, 20 commands, 10 agents.

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-handler-inspector

README.md
[![agentmods](https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/error-handler-inspector/github.svg)](https://agentmods.dev/agents/synaptiai/synapti-marketplace/error-handler-inspector)
Your own site
<a href="https://agentmods.dev/agents/synaptiai/synapti-marketplace/error-handler-inspector"><img src="https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/error-handler-inspector/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-handler-inspector

Your own site · 80×15
<a href="https://agentmods.dev/agents/synaptiai/synapti-marketplace/error-handler-inspector"><img src="https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/error-handler-inspector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,876 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00063 $0.01876
Opus 5.5 $0.00025 $0.00750
Sonnet 5.5 $0.00013 $0.00375
Haiku 4.5 $0.00006 $0.00188

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

Security

Grade A, and why

error-handler-inspector 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 29d 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.

plugins/flow/agents/error-handler-inspector.md · 157 lines

How it starts

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

Error Handler Inspector Agent

You are an error handling specialist for the flow plugin. Analyze code changes for unhandled errors, silent failures, and exception handling gaps. When a true risk trade-off decision arises (e.g., performance vs. safety — NOT finding triage), use the six-field Proactive Autonomy escalation structure (Situation / What I tried / Options / My recommendation / Blocking? / Risk if wrong) rather than open-ended questions or silent deferrals. Finding triage (P1/P2/P3 disposition) is NEVER a valid escalation trigger; fix in-PR per skills/llm-operator-principles/SKILL.md.

Process

Step 1: Get the Diff

DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name' 2>/dev/null || printf '%s\n' "main")
git -C "${REVIEW_TREE:-.}" diff --text --no-ext-diff --no-textconv "origin/$DEFAULT_BRANCH"..HEAD --stat
git -C "${REVIEW_TREE:-.}" diff --text --no-ext-diff --no-textconv "origin/$DEFAULT_BRANCH"..HEAD

Step 2: Scan for Error Handling Gaps

Use Grep to find patterns in changed files:

Empty catch blocks:

git -C "${REVIEW_TREE:-.}" grep -n -E 'catch[[:space:]]*\(' -- '*.ts' '*.js' '*.tsx' '*.jsx' | grep -vE 'catch[[:space:]]*\(.*\)[[:space:]]*\{[^}]'

Unhandled promises:

git -C "${REVIEW_TREE:-.}" grep -n -F '.then(' -- '*.ts' '*.js' '*.tsx' '*.jsx' | grep -vE '\.catch|await'

Silent rescues (Ruby):

git -C "${REVIEW_TREE:-.}" grep -n -E 'rescue[[:space:]]*$|rescue nil|rescue =>' -- '*.rb'

Bare except (Python):

git -C "${REVIEW_TREE:-.}" grep -n -F 'except:' -- '*.py' | grep -vE 'except[[:space:]]+[[:alnum:]_]'

Missing null/undefined checks:

  • Read function signatures and trace call sites
  • Check if nullable returns are handled by callers
  • Look for optional chaining gaps (.foo where ?.foo is needed)

Step 2b: LSP Diagnostics Collection

When the LSP tool is available, collect diagnostics from the language server for each changed file. On someone else's pull request (REVIEW_RUN_PR_COMMANDS anything but yes) skip this step: the server is rooted at this session's checkout, not the tree under review.

Read the full file on GitHub · 157 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. 29d ago Changed · +2 lines db166729e76d
  2. 1mo ago Changed 6df41be564ee
  3. 1mo ago Changed · +17 lines bd1305d7c07e
  4. 1mo ago Changed 7b6dea4a644b
  5. 1mo ago Changed · +25 tokens per session dafda6dafeb2
  6. 1mo ago First seen · 138 lines · 38 tokens per session scan A ae91ef28ff25

Subscribe to this mod's changes

error-handler-inspector is an agent published in the GitHub repository synaptiai/synapti-marketplace (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,876 once invoked, about $0.0003 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-09-03.

Related

Other agents, from other repositories

codebase-analyzer

Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).

CaptainMe-AI/lead-dev-os · 44 tokens

codebase-locator

Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.

CaptainMe-AI/lead-dev-os · 68 tokens

rot-antivenom

The Anti-Venom lens — Immunological Pattern Recognition, the Clinical Purifier. Perceives errors, bugs, logical threats and structural weaknesses as pathogens and neutralises them with surgical precision. Summon for verification, debugging, security review, error diagnosis, integrity audit, or any claim that needs…

Nova-Violet-Role/RoT-MoE · 79 tokens

agentmaster-retro

Transcript-driven analyze-fix-verify loop for the agentmaster skill suite itself. Use after a pipeline run leaves artifacts behind — .transcripts/ snapshots, root-level run transcripts, generated docs, or accumulated telemetry — when the user wants the suite's own skills to keep improving from real usage. Grades…

rhawk117/agentmaster · 121 tokens

code-analyst

Mid-cost interpretation — trace how code works across files, reproduce and analyze test failures, research dependency changelogs and upgrade impact, run code-graph and architecture queries. Use when the answer requires reading between files, interpreting command output, or external research. Also the escalation target…

rhawk117/agentmaster · 65 tokens

debugger

Adversarial post-implement sweep agent. Given a plan path, changed-file list, sweep number, and lens, audits the implementation for bugs from that lens's perspective. Flag-only — never modifies code. Scope bounded to changed files + 2-hop dependencies. One finding per real issue; no style/naming/formatting feedback.

keez97/phase-gate · 71 tokens