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/bengous/claude-code-pluginsWrote 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/commands/bengous/claude-code-plugins/null-as-error)<a href="https://agentmods.dev/commands/bengous/claude-code-plugins/null-as-error"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/null-as-error/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/commands/bengous/claude-code-plugins/null-as-error"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/null-as-error.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.00000 | $0.00097 |
| Opus 5.5 | $0.00000 | $0.00039 |
| Sonnet 5.5 | $0.00000 | $0.00019 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
null-as-error 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 1mo 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.
What it actually says
Invoke the null-as-error skill to audit the current project for silent error swallowing in Effect code.
Scan scope: $ARGUMENTS (defaults to src/ if empty).
The skill will:
- Check if Effect is installed (skip if not)
- Run the scanner to find catchAll patterns that collapse errors into sentinel values
- Spawn an auditor agent to classify each finding by severity and prescribe fixes
- Produce a structured report with actionable recommendations
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.
- 1mo ago First seen · 10 lines · 0 tokens per session scan A c49bfb5b08ea
null-as-error is a command published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 97 tokens. 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.
Other commands, from other repositories
cleanup
Systematically clean up code, remove dead code, and optimize project structure.
debug
Systematic debug loop: root cause before any fix. Four phases, an evidence ledger, the 3-fix architecture wall. Use for any bug, defect, regression, test failure, or unexpected behavior before proposing a fix: 'fix this bug', 'why does X fail', 'the test is failing', 'it broke after Y', 'debug X', 'bị lỗi', 'sửa bug'…
fix-ci
Start an iterative CI fix session — resolve the input (build / PR / branch / cwd), then run the fixing-ci skill loop until CI is green or you've hit the iteration cap.
doctor
Diagnose pro-workflow setup and Claude Code configuration.
cleanup
Systematically clean up code, remove dead code, and optimize project structure.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.