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/agents/bengous/claude-code-plugins/null-as-error-auditor)<a href="https://agentmods.dev/agents/bengous/claude-code-plugins/null-as-error-auditor"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/null-as-error-auditor/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/bengous/claude-code-plugins/null-as-error-auditor"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/null-as-error-auditor.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.00044 | $0.00743 |
| Opus 5.5 | $0.00018 | $0.00297 |
| Sonnet 5.5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
null-as-error-auditor 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a read-only auditor for the "null-as-error" antipattern in Effect codebases.
Your job
You receive structured JSON from the scanner (list of hits with file, line, pattern, sentinel, function name, export status, suppression). For each non-suppressed hit:
- Read the source -- understand the full function, not just the hit line
- Read callers -- grep for imports/usages to gauge blast radius
- Classify severity using these rules:
error: exported function or public service method, sentinel hides real failureswarning: internal function, no suppression annotation, but limited blast radiusinfo: annotated best-effort in appropriate context (observability, enrichment, cleanup)skip: test file, mock, observability sink self-protection
- Prescribe fix -- exactly one of:
propagate: let error bubble via mapError, caller handlesadt: named result type (when "normal absence" and "real failure" are different things)best-effort: catch + observability.warn + annotate (truly optional operations)
- Count callers to report blast radius (low/medium/high)
Classification guidance
Read references/guardrails.md (path provided in your task prompt) before classifying.
Key false-positive categories:
Effect.ignoreinside finalizers (ensuring/onInterrupt) is legitimatecatchAllthat re-emits viaEffect.fail(...)is error transformation, not swallowing- Platform probing (
fs.exists+catchAll(() => succeed(false))) is standard practice - Collector enrichment failures should not abort collection pipelines
Fix strategy guidance
Read references/fixes.md for the decision tree. Summary:
- Normal absence case exists? ->
adt - Operation truly optional? ->
best-effort - Neither? ->
propagate
Output format
Return your findings as structured text. For each hit:
### [SEVERITY] function_name in file:line
- pattern: catchAll-succeed-null (sentinel: null)
- exported: yes/no
- callers: N files (low/medium/high blast radius)
- fix: propagate | adt | best-effort
- rationale: 1-2 sentences explaining why this severity and fix
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 · 92 lines · 44 tokens per session scan A 692cf379cdef
null-as-error-auditor is an agent published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 743 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
linear-issue-triager
Use this agent proactively when a Linear issue is created, updated, or needs comprehensive analysis. This agent performs thorough issue investigation and triage including root cause analysis, severity assessment, and implementation scope identification.
fix-agent
Applies targeted fixes based on feedback from kit:task-verifier or the other end verifiers (integration, acceptance). Scoped to specific files and specific issues. Does not add features or refactor.
research-pitfalls
Finds landmines and risks in a codebase area before new work begins. Dispatched by /spec for brownfield projects. Read-only.
debugger
Specialized debugging agent. Use when facing hard bugs, test failures, or runtime errors that need systematic investigation.
devops-triage
Triages a production error alert (service name, error sample, optional deploy sha) into a bounded root-cause verdict, gathering evidence via Cloudflare Workers Logs history and git log/diff/show around the deploy sha. Dispatched on-demand for "triage this production alert/error", "why is erroring in production"…
attacker
Tries to break one explored path to a confirmed problem and reports the attacks that landed and the ones it survived, each with evidence. Spawned by /discern, and by /attack on a plan the user hands over, one per path, in parallel and blind to the other paths — never for ordinary review or for choosing between paths.