agentic-reliability-audit

A command that audits infrastructure used by AI agents against an eight-point reliability checklist. It checks for resource leaks, misleading success reports, unsafe network requests, and missing error or timeout handling.

In plain words
What is it for?
It is for reviewing TypeScript and Python agent infrastructure, including memory bounds, response-size limits, SSRF checks, result honesty, and error coverage.
Why use it?
It helps reveal failures that code may hide, such as unbounded memory use, fake healthy responses, unsafe URLs, or route handlers that do not catch errors.

Command for Claude Code

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 commands/homenshum/nodebenchai/agentic-reliability-audit
Clone the repo
git clone --depth 1 https://github.com/HomenShum/NodeBenchAI

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 609 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.00000 $0.00609
Opus 5 $0.00000 $0.00304
Sonnet 5 $0.00000 $0.00122
Haiku 4.5 $0.00000 $0.00061

Measured 2d ago against content hash 9937cdd71278, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agentic-reliability-audit 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 2d 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.

.claude/commands/agentic-reliability-audit.md · 77 lines

How it starts

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

Agentic Reliability Audit

Run a comprehensive audit of agent-facing infrastructure against the 8-point reliability checklist.

Instructions

You are an Agentic Systems Reliability Engineer. Your job is to find where the system lies to itself — where code tells agents everything is fine while silently leaking memory, inflating scores, or masking failures.

Phase 1: Scan (parallel agents)

Launch 3 parallel scan agents:

Agent 1 — Memory & Bounds Scan all TypeScript and Python files for:

  • new Map(), new Set(), const.*=.*[] without corresponding MAX_* + eviction
  • response.text() or response.json() without size limits
  • fetch( where URL is a variable without SSRF validation Report: file, line, pattern, severity (P0/P1/P2)

Agent 2 — Honesty Audit Scan all files for:

  • res.status(2 in catch/fallback/else branches (fake success)
  • passed: true, score:.*1.0, "VERIFIED", "healthy" literals that bypass computation
  • JSON.stringify feeding createHash without sorted keys Report: file, line, pattern, severity

Agent 3 — Error & Timeout Coverage Scan all route handlers for:

  • async.*req.*res without try/catch or asyncHandler wrapper
  • await calls to external services without AbortController/timeout
  • Missing !res.headersSent guards before error responses Report: file, line, pattern, severity

Phase 2: Classify

Merge findings into a single table: | # | File | Line | Check | Finding | Severity | Fix Pattern | Sort by severity (P0 first), then by file.

Phase 3: Fix P0s

For each P0 finding:

  1. Read the file
  2. Apply the fix pattern from .claude/rules/agentic_reliability.md
  3. Verify tsc passes
  4. Move to next P0

Phase 4: Verify

  • Run npx tsc --noEmit on affected packages
  • Run npx vitest run on affected test suites
  • Report: findings count by severity, fixes applied, build status

Output format

## Agentic Reliability Audit Report

**Scope**: [files scanned]
**Findings**: X total (Y P0, Z P1, W P2)
**Fixes applied**: N P0 fixes

### P0 Findings & Fixes
| # | File | Check | Finding | Fix Applied |
...

### P1 Findings (fix in same session)
| # | File | Check | Finding |
...

### P2 Findings (fix when touched)
| # | File | Check | Finding |
...

**Build**: tsc [pass/fail], vitest [X/Y passed]

Read the full file on GitHub · 77 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. 2d ago First seen · 77 lines · 0 tokens per session scan A 9937cdd71278

Subscribe to this mod's changes

agentic-reliability-audit is a command published in the GitHub repository HomenShum/NodeBenchAI (14 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 609 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-30.