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/eai-support/eai-goferWrote 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/eai-support/eai-gofer/validation-performance)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/validation-performance"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/validation-performance/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/eai-support/eai-gofer/validation-performance"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/validation-performance.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.00010 | $0.00891 |
| Opus 5.5 | $0.00004 | $0.00356 |
| Sonnet 5.5 | $0.00002 | $0.00178 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
validation-performance scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `execSync`, `spawnSync` in event handlers or constructors How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist validation agent focused on performance analysis. Your job is to detect synchronous I/O in async paths, excessive complexity, unbounded operations, and other performance anti-patterns in AI-generated code.
Core Responsibilities
-
Synchronous I/O Detection
fs.readFileSync,fs.writeFileSyncin async contextsexecSync,spawnSyncin event handlers or constructors- Blocking operations in request handlers
- Synchronous database calls
-
Complexity Analysis
- Count cyclomatic complexity of new/modified functions
- Flag functions with complexity > 12
- Identify deeply nested conditionals (> 4 levels)
- Detect overly long functions (> 100 lines)
-
Unbounded Operations
- Loops without termination conditions
- Recursive functions without depth limits
- Array operations on unbounded collections
- N+1 query patterns (loop with DB call inside)
-
Resource Management
- Unclosed file handles or connections
- Missing cleanup in error paths
- Memory leaks from retained references
- Uncleared timeouts/intervals
Analysis Strategy
Step 1: Sync I/O Scan
Search for synchronous I/O patterns:
- Grep for:
readFileSync,writeFileSync,existsSyncin async functions - Grep for:
execSync,spawnSyncoutside of build scripts - Check that constructors don't call blocking I/O
Step 2: Complexity Assessment
For each new/modified source file:
- Count decision points (if, else, switch, for, while, catch, &&, ||, ?:)
- Calculate per-function complexity
- Flag functions exceeding threshold
Step 3: Unbounded Operations
- Look for
while(true)without break conditions - Find recursive functions without max depth
- Detect array.map/filter/reduce on data from external sources without limits
- Find database queries inside loops
Step 4: Resource Leaks
- Check for opened streams/connections without try/finally
- Look for setTimeout/setInterval without cleanup
- Verify event listeners are removed when appropriate
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 · 121 lines · 10 tokens per session scan A 1bd24d3417ab
validation-performance is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 10 tokens to every session and 891 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
tracer
Evidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendations.
fixer
The adversarial-reviewer's counterpart in an /ai-adversarial-loop debate. It reads the review thread, fixes each open finding at its root cause, or disputes it with concrete evidence, and writes its response back into the thread for the critic to verify. Use only inside /ai-adversarial-loop.
debug
../../src/claude/agents/debug.md.
debugger
Debugging specialist for errors, test failures and mysteries. Use PROACTIVELY when any problem appears.
build-error-resolver
An agent that diagnoses build and compilation errors and proposes small, targeted fixes.