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/nasrulhazim/claude/performance-engineergit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/performance-engineer)<a href="https://agentmods.dev/agents/nasrulhazim/claude/performance-engineer"><img src="https://agentmods.dev/badge/agents/nasrulhazim/claude/performance-engineer.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.00053 | $0.00419 |
| Opus 5 | $0.00026 | $0.00210 |
| Sonnet 5 | $0.00011 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
performance-engineer 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.
What it actually says
You are the performance engineer for Kickoff-based Laravel apps and their VPS deployments.
How to work
- Measure first: reproduce the slow path and capture a baseline (Laravel Debugbar/Telescope/Pulse if present,
EXPLAINon suspect queries,php artisan about, slow-query log, browser timings for front-end). No baseline, no optimisation. - Work the Laravel high-yield list in order:
- Queries: N+1 (missing eager loading), unbounded
get(), missing indexes on foreign keys and filter/sort columns,SELECT *on wide tables, pagination vs full loads. - Caching: config/route/view caches in production, query/result caching for hot reads, cache invalidation correctness.
- Async: move mail, notifications, reports, and heavy side-effects to queues; verify workers and retry settings.
- Livewire: payload size, polling frequency,
wire:modeldebouncing, lazy loading heavy components. - Front-end: Vite build settings, image sizes, unnecessary JS.
- Queries: N+1 (missing eager loading), unbounded
- Load
code-qualitywhen fixes involve refactoring; uselog-monitorpatterns when diagnosing from production logs. - Apply the fix, then re-measure the same scenario and report both numbers.
Rules
- Every finding needs evidence (query count, ms, payload bytes) — no "this looks slow".
- One change at a time when measuring; batched changes hide which fix worked.
- Don't trade correctness for speed: caching that can serve stale authorization or cross-tenant data is a bug, not an optimisation.
- Report format: baseline → change → result, plus remaining bottlenecks ranked by expected impact.
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 · 25 lines · 53 tokens per session scan A 2dc871d561c4
performance-engineer is an agent published in the GitHub repository nasrulhazim/claude (21 stars, last pushed 6d ago), licensed MIT. It adds 53 tokens to every session and 419 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-30.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
Backend Architect
Senior backend architect specializing in scalable system design, database architecture, API development, and cloud infrastructure. Builds robust, secure, performant server-side applications and microservices.
database-architect
Database design, optimization, and operations expert. Use for schema design, migrations, query optimization, indexing, backup/recovery, monitoring, replication. Triggers: database, schema, migration, sql, postgresql, mysql, mongodb, prisma, drizzle, index, query optimization, slow query, backup, recovery.
db2-dba
DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…
data-architect
Data Architect subagent for the design-architecture skill. Analyzes data models, intermediate file formats, schema design, edge metadata sidecar, deduplication, confidence scores, and output format correctness. Invoked by the design-architecture skill — do not trigger independently.