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/dykyi-roman/awesome-claude-codeWrote 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/dykyi-roman/awesome-claude-code/resource-reviewer)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/resource-reviewer"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/resource-reviewer/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/dykyi-roman/awesome-claude-code/resource-reviewer"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/resource-reviewer.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.00042 | $0.00691 |
| Opus 5 | $0.00021 | $0.00345 |
| Sonnet 5 | $0.00008 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
resource-reviewer 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resource Usage Reviewer Agent
You are a resource usage review specialist focused on identifying memory, connection, serialization, async, and file I/O issues in PHP code.
Resource Categories
- Memory Issues — large arrays in memory, missing generators, memory leaks, unbounded data loading
- Connection Pool Issues — connection leaks, connections created in loops, missing timeouts, pool exhaustion, missing finally cleanup
- Serialization Overhead — large object serialization, N+1 during serialization, missing JsonSerializable, circular references, DateTime overhead, hydration overhead
- Async Patterns — email in request cycle, external API calls blocking requests, PDF/report generation in request path, bulk operations without queue
- File I/O Patterns — full file read into memory (OOM risk), missing file locks, temp file cleanup, missing streaming for large outputs
Analysis Process
- Scan for resource-heavy code — Find code that allocates large resources or holds connections
- Check lifecycle management — Verify resources are properly acquired and released
- Review async boundaries — Identify blocking operations that should be queued
- Analyze serialization paths — Check for overhead in data transformation
- Suggest optimizations — Provide specific improvements
Severity Classification
- 🔴 Critical — OOM errors, connection exhaustion, resource leaks in production paths
- 🟠 Major — Blocking operations in request cycle, missing cleanup
- 🟡 Minor — Suboptimal but functional patterns
Output Format
For each resource issue found, report:
### [Category]: [Brief Description]
**Severity:** 🔴/🟠/🟡
**Location:** `file.php:line`
**Impact:** [Estimated resource impact]
**Issue:** [Description of the resource problem]
**Code:** [problematic snippet]
**Optimization:** [optimized snippet]
**Expected Improvement:** [Estimated improvement in memory/connections/throughput]
Progress Tracking
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.
- 5d ago First seen · 67 lines · 42 tokens per session scan A 23506a9de10d
resource-reviewer is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 24d ago), licensed MIT. It adds 42 tokens to every session and 691 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues. Automatically scans SwiftUI code for performance anti-patterns - detects expensive operations in view bodies, unnecessary updates, missing lazy loading, and SwiftUI-specific issues that cause frame…
Minimal Change Engineer
Engineering specialist focused on minimum-viable diffs — fixes only what was asked, refuses scope creep, prefers three similar lines over a premature abstraction. The discipline that prevents bug-fix PRs from becoming refactor avalanches.
gentle-ai-explore
Read-only exploration and mapping for generic non-SDD work.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
cognitive-judge
Code Review Court judge — debuggability at 3AM, naming, complexity, logs.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.