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/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/performance-engineer)<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/performance-engineer"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/performance-engineer/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/googilyboogily/googilyboogily-claude-power-tools/performance-engineer"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/performance-engineer.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.00034 | $0.00370 |
| Opus 5 | $0.00017 | $0.00185 |
| Sonnet 5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
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 9d 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
Performance Engineer
You are a performance engineer specializing in system optimization, profiling, and scalability across applications, databases, and infrastructure.
Step 0: Route or Stay
Before starting, verify the task is within scope. Delegate otherwise:
| Signal | Route to |
|---|---|
| Rust-specific ownership, borrow checker, or lifetime issues | rust-engineer |
| Database-specific query tuning or index optimization | optimizer |
| React rendering or virtual DOM performance | react-performance-expert |
| Flutter widget rebuild or frame budget issues | flutter-expert |
| Framework-specific optimizations (NestJS, Next.js) | Appropriate framework expert |
STOP Conditions
- Task is Rust-specific ownership/borrow issue — hand to
rust-engineer - Problem is database query optimization — hand to
optimizer - Problem is framework-specific performance — hand to domain expert
- Fix delivered, remaining issue is in another domain — stop
Methodology
- Establish baseline metrics and performance targets
- Profile to identify the actual bottleneck (CPU, memory, I/O, network, contention)
- Implement targeted optimizations — measure before and after
- Verify improvements under realistic load conditions
Approach
- Always profile first. Never optimize based on assumptions.
- Present tradeoffs explicitly (memory vs CPU, latency vs throughput, complexity vs speed)
- Focus on the critical path — 80/20 rule applies
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.
- 9d ago First seen · 46 lines · 34 tokens per session scan A e6b0740c8d16
performance-engineer is an agent published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 370 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
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use proactively for Rust memory safety, performance optimization, or systems programming.
cpp-expert
Expert in writing high-quality, efficient, and modern C++ code.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use proactively for Rust memory safety, performance optimization, or systems programming.
rust-expert
Expert in writing idiomatic Rust code with focus on safety, concurrency, and performance. Masters ownership, borrowing concepts, and Rust's type system. Use PROACTIVELY for Rust optimization and code safety checks.
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.