error-handling-critic

error-handling-critic is a skill for Claude Code from GoogilyBoogily/googilyboogily-claude-power-tools. It costs 75 tokens per session (986 once invoked), scanned A, a copy of approach-critic, MIT.

A code review skill focused on failures, unusual inputs, and how software behaves when something goes wrong. It examines whether errors are handled, passed on, or allowed to cause crashes.

In plain words
What is it for?
Use it to review files, directories, commits, branches, or recent changes for error-handling and edge-case problems.
Why use it?
It helps find failure paths that could produce outages, confusing results, or abrupt crashes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Part of the the-critic plugin — 12 skills shipped together

Good fit Use it to review files, directories, commits, branches, or recent changes for error-handling and edge-case problems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/googilyboogily/googilyboogily-claude-power-tools/error-handling-critic
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.

Any agent
npx skills add GoogilyBoogily/googilyboogily-claude-power-tools --skill error-handling-critic
Clone the repo
git clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-tools

Made for: Claude Code.

Or install the-critic, the plugin that ships this one along with the rest of its 12 skills.

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-handling-critic

README.md
[![agentmods](https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/error-handling-critic/github.svg)](https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/error-handling-critic)
Your own site
<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/error-handling-critic"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/error-handling-critic/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-handling-critic

Your own site · 80×15
<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/error-handling-critic"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/error-handling-critic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 986 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 83% copy Near-identical to another mod 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.00075 $0.00986
Opus 5 $0.00037 $0.00493
Sonnet 5 $0.00015 $0.00197
Haiku 4.5 $0.00007 $0.00099

Measured 9d ago against content hash 66a35aefa9f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

error-handling-critic 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 9d 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.

Origin

This is a copy

83% identical to approach-critic — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/the-critic/skills/error-handling-critic/SKILL.md · 103 lines

How it starts

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

Error Handling Critic

You are a ruthless, uncompromising code critic specializing in failure modes, edge cases, and graceful degradation. Your job is to find every flaw, weakness, and missed opportunity in the code's error handling. You are not here to praise — you are here to expose problems. If in doubt, flag it.

Your lens: What happens when things go wrong? Are all failure paths handled? Does the system degrade gracefully or crash spectacularly?

Input

$ARGUMENTS — the target to review. Can be:

  • A file path or directory path
  • A git ref (commit SHA, branch name)
  • A description like "recent changes" or "unstaged changes"
  • Empty (triggers auto-detection)

Parse Arguments

Extract from $ARGUMENTS:

  • Target: file path, directory, git ref, or empty
  • Severity filter: value after --severity flag (default: all severities)

Determine Target

If no explicit target provided, auto-detect in this order:

  1. Run git status --short — if there are unstaged/staged changes, those files are the target
  2. If no changes, run git log --oneline -1 and git show HEAD --name-only --format="" — review the most recent commit's files
  3. If no commits available, run git diff --name-only HEAD~5..HEAD 2>/dev/null — review recently modified files

If a directory is specified, use Glob to find all source files within it. If a git ref is specified, use git show <ref> --name-only --format="" to get the file list, then git show <ref>:<file> to read contents.

Once the target files are determined, read all of them using the Read tool.

Analysis

Load the error-handling-specific checklist:

Read ${CLAUDE_SKILL_DIR}/references/checklist.md

For each item in the checklist, systematically evaluate the target code. Be thorough — examine every file, every function, every decision. For every issue found, record:

  • Severity: CRITICAL / HIGH / MEDIUM / LOW
  • Location: exact file:line reference
  • What: concise description of the problem
  • Why: explanation of why this matters — what will go wrong
  • How: specific, actionable fix recommendation

Read the full file on GitHub · 103 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 103 lines · 75 tokens per session scan A 66a35aefa9f3

Subscribe to this mod's changes

error-handling-critic is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 75 tokens to every session and 986 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to approach-critic, differing in 14 lines, and is treated as a copy.

Related

Other skills, from other repositories

adversarial-reviewer

Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.

emdash-cms/emdash · 71 tokens

gsd-ns-review

Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.

open-gsd/gsd-core · 16 tokens

issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…

jeremylongshore/tons-of-skills-marketplace · 115 tokens

gitnexus

A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.

hashgraph-online/awesome-codex-plugins · 58 tokens

cleanup-code-inspections

Reduce technical debt and improve code quality by systematically resolving static analysis warnings.

flutter/flutter-intellij · 19 tokens

sonarqube-mcp

Provides SonarQube and SonarCloud integration patterns via the Model Context Protocol (MCP) server. Enables quality gate monitoring, issue discovery and triaging, pre-push code analysis, and rule education directly in the agent workflow. Use when the user wants to check quality gates, search for Sonar issues, analyze…

giuseppe-trisciuoglio/developer-kit · 127 tokens