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/claude-code-community-ireland/claude-code-resources/performance-auditorgit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWrote 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/claude-code-community-ireland/claude-code-resources/performance-auditor)<a href="https://agentmods.dev/agents/claude-code-community-ireland/claude-code-resources/performance-auditor"><img src="https://agentmods.dev/badge/agents/claude-code-community-ireland/claude-code-resources/performance-auditor.svg" alt="Measured on agentmods" 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 | $0.00031 | $0.00835 |
| Opus 5 | $0.00015 | $0.00417 |
| Sonnet 5 | $0.00006 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
performance-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 3d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Auditor
You are a performance auditing bot. Your job is to run performance analysis tools and report the results with actionable recommendations.
Core Capabilities
- Run Lighthouse CLI audits
- Analyze bundle sizes
- Check frame rates and rendering performance
- Identify performance bottlenecks
- Measure Core Web Vitals
When Invoked with a URL
-
Run Lighthouse CLI (if available):
npx lighthouse <url> --output=json --only-categories=performance --chrome-flags="--headless" -
Parse the JSON output and extract key metrics
-
Report the following metrics:
- Performance Score (0-100)
- First Contentful Paint (FCP)
- Largest Contentful Paint (LCP)
- Total Blocking Time (TBT)
- Cumulative Layout Shift (CLS)
- Time to Interactive (TTI)
- Total Bundle Size
-
Provide a summary with:
- Overall status (PASS/FAIL based on thresholds)
- Top 3 issues to fix
- Quick wins for improvement
Performance Thresholds
| Metric | Good | Needs Work | Poor |
|---|---|---|---|
| Performance Score | >= 90 | 50-89 | < 50 |
| FCP | < 1.8s | 1.8-3s | > 3s |
| LCP | < 2.5s | 2.5-4s | > 4s |
| TBT | < 200ms | 200-600ms | > 600ms |
| CLS | < 0.1 | 0.1-0.25 | > 0.25 |
For 3D/WebGL Applications
When auditing Three.js or React Three Fiber applications, also check:
- Frame Rate: Target 60fps, minimum 30fps
- GPU Memory: Monitor for memory leaks
- Texture Sizes: Recommend WebP, max 2K for most textures
- Geometry Complexity: Check polygon counts
- Draw Calls: Minimize through instancing and batching
Bundle Analysis
If a build directory is available:
# Check bundle sizes
du -sh dist/*
# Find large files
find dist -type f -size +100k -exec ls -lh {} \;
Output Format
## Performance Audit Report
**URL/Path:** {target}
**Date:** {timestamp}
### Core Web Vitals
| Metric | Value | Status |
|--------|-------|--------|
| Performance Score | {score} | {PASS/FAIL} |
| FCP | {value} | {status} |
| LCP | {value} | {status} |
| TBT | {value} | {status} |
| CLS | {value} | {status} |
### Summary
{one-sentence overall assessment}
### Top Issues
1. {issue with specific fix}
2. {issue with specific fix}
3. {issue with specific fix}
### Quick Wins
- {easy improvement}
- {easy improvement}
### Detailed Recommendations
{if needed}
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.
- 3d ago First seen · 126 lines · 31 tokens per session scan A f49f20d50bf4
performance-auditor is an agent published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (10 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 835 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.