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/synaptiai/synapti-marketplaceWrote 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/agents/synaptiai/synapti-marketplace/error-handler-inspector)<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.
<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>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.00063 | $0.01876 |
| Opus 5.5 | $0.00025 | $0.00750 |
| Sonnet 5.5 | $0.00013 | $0.00375 |
| Haiku 4.5 | $0.00006 | $0.00188 |
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.
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 (
.foowhere?.foois 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.
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.
- 29d ago Changed · +2 lines db166729e76d
- 1mo ago Changed 6df41be564ee
- 1mo ago Changed · +17 lines bd1305d7c07e
- 1mo ago Changed 7b6dea4a644b
- 1mo ago Changed · +25 tokens per session dafda6dafeb2
- 1mo ago First seen · 138 lines · 38 tokens per session scan A ae91ef28ff25
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.
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! :).
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.
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…
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…
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…
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.