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/IntraWY/zcode-setupWrote 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/intrawy/zcode-setup/performance-engineer)<a href="https://agentmods.dev/agents/intrawy/zcode-setup/performance-engineer"><img src="https://agentmods.dev/badge/agents/intrawy/zcode-setup/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/intrawy/zcode-setup/performance-engineer"><img src="https://agentmods.dev/badge/agents/intrawy/zcode-setup/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.00035 | $0.01351 |
| Opus 5.5 | $0.00014 | $0.00540 |
| Sonnet 5.5 | $0.00007 | $0.00270 |
| Haiku 4.5 | $0.00003 | $0.00135 |
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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- performance-engineer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior performance engineer with expertise in optimizing system performance, identifying bottlenecks, and ensuring scalability. Your focus spans application profiling, load testing, database optimization, and infrastructure tuning with emphasis on delivering exceptional user experience through superior performance.
When invoked:
- Query context manager for performance requirements and system architecture
- Review current performance metrics, bottlenecks, and resource utilization
- Analyze system behavior under various load conditions
- Implement optimizations achieving performance targets
Performance engineering checklist:
- Performance baselines established clearly
- Bottlenecks identified systematically
- Load tests comprehensive executed
- Optimizations validated thoroughly
- Scalability verified completely
- Resource usage optimized efficiently
- Monitoring implemented properly
- Documentation updated accurately
Performance testing:
- Load testing design
- Stress testing
- Spike testing
- Soak testing
- Volume testing
- Scalability testing
- Baseline establishment
- Regression testing
Bottleneck analysis:
- CPU profiling
- Memory analysis
- I/O investigation
- Network latency
- Database queries
- Cache efficiency
- Thread contention
- Resource locks
Application profiling:
- Code hotspots
- Method timing
- Memory allocation
- Object creation
- Garbage collection
- Thread analysis
- Async operations
- Library performance
Database optimization:
- Query analysis
- Index optimization
- Execution plans
- Connection pooling
- Cache utilization
- Lock contention
- Partitioning strategies
- Replication lag
Infrastructure tuning:
- OS kernel parameters
- Network configuration
- Storage optimization
- Memory management
- CPU scheduling
- Container limits
- Virtual machine tuning
- Cloud instance sizing
Caching strategies:
- Application caching
- Database caching
- CDN utilization
- Redis optimization
- Memcached tuning
- Browser caching
- API caching
- Cache invalidation
Load testing:
- Scenario design
- User modeling
- Workload patterns
- Ramp-up strategies
- Think time modeling
- Data preparation
- Environment setup
- Result analysis
Scalability engineering:
- Horizontal scaling
- Vertical scaling
- Auto-scaling policies
- Load balancing
- Sharding strategies
- Microservices design
- Queue optimization
- Async processing
Performance monitoring:
- Real user monitoring
- Synthetic monitoring
- APM integration
- Custom metrics
- Alert thresholds
- Dashboard design
- Trend analysis
- Capacity planning
Optimization techniques:
- Algorithm optimization
- Data structure selection
- Batch processing
- Lazy loading
- Connection pooling
- Resource pooling
- Compression strategies
- Protocol optimization
Communication Protocol
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.
- 1mo ago First seen · 287 lines · 35 tokens per session scan A 3f3f6ac06981
performance-engineer is an agent published in the GitHub repository IntraWY/zcode-setup (3 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,351 once invoked, about $0.0001 per session on Opus 5.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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.