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 skills/huzaifa525/claude-code-optimizer/perf-checknpx skills add huzaifa525/claude-code-optimizer --skill perf-checkgit clone --depth 1 https://github.com/huzaifa525/claude-code-optimizerWrote 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/skills/huzaifa525/claude-code-optimizer/perf-check)<a href="https://agentmods.dev/skills/huzaifa525/claude-code-optimizer/perf-check"><img src="https://agentmods.dev/badge/skills/huzaifa525/claude-code-optimizer/perf-check.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.00025 | $0.00446 |
| Opus 5 | $0.00013 | $0.00223 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
perf-check 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 4d 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.
What it actually says
Analyze $ARGUMENTS for performance issues.
Check Categories
Database & Queries
- N+1 query patterns (loop with query inside)
- Missing indexes on frequently queried columns
- SELECT * instead of specific columns
- Missing pagination on list endpoints
- Unoptimized joins or subqueries
Memory & Resources
- Unclosed connections, streams, file handles
- Growing arrays/maps without limits
- Event listeners not removed on cleanup
- Large objects held in memory unnecessarily
- Missing cleanup in useEffect (React)
Frontend Performance
- Unnecessary re-renders (missing useMemo, useCallback, React.memo)
- Large bundle imports (import entire library vs specific module)
- Images without lazy loading or optimization
- Missing code splitting
- Synchronous operations blocking UI thread
- Missing virtualization for long lists
API & Network
- Missing caching (Redis, in-memory, HTTP cache headers)
- Redundant API calls
- Missing request deduplication
- Large payloads without compression
- Missing connection pooling
General
- O(n²) or worse algorithms where O(n) is possible
- Synchronous file I/O in async context
- Regex backtracking (catastrophic regex)
- Unnecessary deep cloning
Output Format
## Performance Report: [target]
### Critical (fix now)
- [file:line] [issue] [impact] [fix]
### Warning (should fix)
- [file:line] [issue] [impact] [fix]
### Suggestion (optimization)
- [file:line] [issue] [impact] [fix]
### Good Patterns Found
- [what's already well-optimized]
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.
- 4d ago First seen · 69 lines · 25 tokens per session scan A b9932aa1cfa3
perf-check is a skill published in the GitHub repository huzaifa525/claude-code-optimizer (9 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 446 once invoked, about $0.0001 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 skills, from other repositories
throughline
Use when the user asks to use Throughline from Codex, continue or restore Throughline memory, export read-only handoff context for a local launcher, prepare a new Codex thread handoff, summarize a captured Codex session, or check whether the Throughline Codex Stop hook captured the current session. Hide long…
critical-review
Use when you want structured feedback on a plan or document before implementation.
save
Save all session progress to status tracking files. Use when you want to checkpoint work mid-session or before ending.
code-review
Use when you want a thorough code review of files, changes, or the entire project before shipping.
implement-batch
Use when you want to implement the next batch of a plan. Handles module implementation, testing, and validation.
audit-orchestrator
Universal Pre-Scan → Analysis → Optimization → Report orchestrator for ANY project type — web apps (Astro/SvelteKit/Next), infrastructure/homelab repos, CLI tools, libraries, backend services, monorepos, data/ML projects, docs. Self-detects project type and runs the matching analysis track. Session state lives in…