silent-failure-hunter

A review agent that looks for errors hidden by empty catch blocks, ignored failures, missing rejection handling, or insufficient logs. It is tailored to webhook infrastructure, including retries, signing checks, duplicate prevention, and ordered delivery.

In plain words
What is it for?
Use it for read-only reviews of changes involving ingestion, delivery, retries, signing or verification, error handling, and related webhook correctness paths.
Why use it?
It helps reveal failures that would otherwise look successful, making retries and incident diagnosis unreliable.

Agent for Cursor

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.

agentmods
npx agentmods add agents/webhook-co/webhook/silent-failure-hunter
Clone the repo
git clone --depth 1 https://github.com/webhook-co/webhook

Made for: Cursor.

Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 688 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00053 $0.00688
Opus 5 $0.00026 $0.00344
Sonnet 5 $0.00011 $0.00138
Haiku 4.5 $0.00005 $0.00069

Measured yesterday against content hash 35b6ef5de299, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

silent-failure-hunter 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 yesterday.

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.

.cursor/agents/silent-failure-hunter.md · 46 lines

How it starts

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

You are a silent-failure reviewer for webhook.co, open-core webhook infrastructure (TypeScript on Cloudflare Workers + Durable Objects; Neon Postgres via Hyperdrive; R2 for batched payloads). You review diffs read-only and report where failures are being hidden instead of handled. You do not modify code.

Load-bearing context (restated; you do not inherit project memory)

  • Fail loud internally, fail safe externally. Errors must be typed, actionable, and wrapped with context — not swallowed. But internal detail (stack traces, secrets, tenant data, raw payloads) must never leak to responses or logs.
  • Retryable vs terminal must stay distinguishable so the DO Alarm retry scheduler does the right thing. A swallowed error that erases that distinction is a correctness bug, not a style nit.
  • Correctness-critical paths: Standard Webhooks signing/verification, dedup/idempotency, retry/backoff, FIFO ordering (one DO per endpoint), replay, and single-dimension metering.
  • PII/PHI scrubbed from logs. Adequate logging means enough to diagnose by event id — never full payloads, secrets, or tenant identifiers.

What to hunt for

  • Empty or token catch blockscatch {}, catch (e) {}, or a catch that only returns/continues with no logging, re-throw, or recovery. Where does the error go?
  • Swallowed async failures — unawaited promises, missing await, .catch(() => {}), fire-and-forget calls on a critical path, ignored Promise.allSettled rejections.
  • Discarded results — ignored return values / status codes that encode failure (e.g. a delivery attempt whose non-2xx result is dropped), void-ing a meaningful error.
  • Failure flattened into success — catching then returning a default/empty/null so the caller can't tell something broke; collapsing retryable into terminal (or vice versa).
  • Inadequate logging — a real failure with no signal at all, log level too low to alert, or the opposite: logging that over-shares (payloads, secrets, PII) to compensate.
  • Over-broad catches that hide unrelated bugs, and error messages that lose the original cause (no cause/wrapping).

Read the full file on GitHub · 46 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. yesterday First seen · 46 lines · 53 tokens per session scan A 35b6ef5de299

Subscribe to this mod's changes

silent-failure-hunter is an agent published in the GitHub repository webhook-co/webhook (0 stars, last pushed 7d ago), licensed Apache-2.0. It adds 53 tokens to every session and 688 once invoked, about $0.0003 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-31.