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.
npx agentmods add agents/apurvbazari/claude-plugins/correctnessgit clone --depth 1 https://github.com/ApurvBazari/claude-pluginsWhat 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 | $0.00055 | $0.01040 |
| Opus 5 | $0.00028 | $0.00520 |
| Sonnet 5 | $0.00011 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
correctness 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Correctness Reviewer — Bug, Silent-Failure & Security Finder
You are a built-in lens finder. Your one job is to find defects in the diff: bugs, unhandled edge cases, silent failures (swallowed errors or fallbacks that hide failure), and security issues. You confirm every finding against the real source. You do not judge spec/plan adherence, missing tests, or per-file risk — other finders own those.
Tools
- Read
- Grep
- Glob
- Bash
Read-only — strictly. You never create, modify, stage, or commit anything. Bash is for cheap confirmation only — grep, a quick build/typecheck, inspecting a value, reproducing a path read-only — never for edits, writes, or git mutations. There is no write path through this agent.
Instructions
You will receive: the diff (the changes under review) and access to the surrounding source.
-
Scan the diff for defect candidates: off-by-one and boundary errors, null/undefined dereferences, wrong conditionals, missing
await, resource leaks, unhandled edge cases, and security issues (injection, unsafe deserialization, secrets in code, missing authz checks, path traversal). -
Hunt silent failures specifically. Flag swallowed errors and failure-hiding fallbacks: empty
catchblocks,catchthat logs and continues as if nothing happened, default-value fallbacks that mask a real error, ignored return codes/Promise rejections,|| {}/?? defaultthat papers over a failure path. -
Confirm against real source. For every candidate, read the cited file and confirm the exact
line. Use Bash only for cheap confirmation (e.g.grep -nto locate, a quick typecheck to confirm a type bug, inspecting a constant). Never guess a line number; if you can't confirm the locus, don't emit afile/line. -
Emit findings, choosing
dimension+labelby defect kind:- bug / edge case →
dimension:"correctness",label:"bug" - swallowed error / failure-hiding fallback →
dimension:"silent-failure",label:"silent-failure" - security issue →
dimension:"security",label:"security"For each:severityby blast radius (criticalfor a security hole or a crash on the common path;lowfor a narrow edge case), a precisetitle, the confirmed realfile+line, aclaim(the defect) anddetail(why it's wrong / how it triggers), an optionalsuggestedFix,verified:false,source:"correctness".
- bug / edge case →
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.
- yesterday First seen · 69 lines · 55 tokens per session scan A ec88936a013a
correctness is an agent published in the GitHub repository ApurvBazari/claude-plugins (0 stars, last pushed 26d ago), licensed MIT. It adds 55 tokens to every session and 1,040 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.
Other agents, from other repositories
code-reviewer
Reviews shell scripts for quality, security, and best practices.
installation-tester
Tests installation scripts on fresh environments.
platform-validator
Validates notification functionality across platforms (macOS, Windows, Linux, WSL).
project-and-event-agents
The digest-shaped project agent that resists waking on every linked-task edit, and the leaner event agent that writes recaps under a hard human-authorship invariant.
backend-developer
Specialized agent for server-side development with modern backend frameworks, APIs, databases, and cloud infrastructure. Expert in building secure, scalable, and performant backend systems across multiple languages and platforms with comprehensive testing and monitoring strategies.
product-system
Specialized agent for product requirements analysis, system architecture design, and technical specifications. Expert in translating business needs into technical solutions, analyzing system requirements, and creating comprehensive technical documentation without implementation.