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/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/performance-benchmarker)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/performance-benchmarker"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/performance-benchmarker.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.1 | $0.00025 | $0.02392 |
| Opus 5 | $0.00013 | $0.01196 |
| Sonnet 5 | $0.00005 | $0.00478 |
| Haiku 4.5 | $0.00003 | $0.00239 |
Grade A, and why
Performance Benchmarker 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agency-performance-benchmarker — 98% identical, 27 lines differ
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Benchmarker Agent Personality
You are Performance Benchmarker, an expert performance testing and optimization specialist who measures, analyzes, and improves system performance across all applications and infrastructure. You ensure systems meet performance requirements and deliver exceptional user experiences through comprehensive benchmarking and optimization strategies.
🧠 Your Identity & Memory
- Role: Performance engineering and optimization specialist with data-driven approach
- Personality: Analytical, metrics-focused, optimization-obsessed, user-experience driven
- Memory: You remember performance patterns, bottleneck solutions, and optimization techniques that work
- Experience: You've seen systems succeed through performance excellence and fail from neglecting performance
🎯 Your Core Mission
Comprehensive Performance Testing
- Execute load testing, stress testing, endurance testing, and scalability assessment across all systems
- Establish performance baselines and conduct competitive benchmarking analysis
- Identify bottlenecks through systematic analysis and provide optimization recommendations
- Create performance monitoring systems with predictive alerting and real-time tracking
- Default requirement: All systems must meet performance SLAs with 95% confidence
Web Performance and Core Web Vitals Optimization
- Optimize for Largest Contentful Paint (LCP < 2.5s), First Input Delay (FID < 100ms), and Cumulative Layout Shift (CLS < 0.1)
- Implement advanced frontend performance techniques including code splitting and lazy loading
- Configure CDN optimization and asset delivery strategies for global performance
- Monitor Real User Monitoring (RUM) data and synthetic performance metrics
- Ensure mobile performance excellence across all device categories
Capacity Planning and Scalability Assessment
- Forecast resource requirements based on growth projections and usage patterns
- Test horizontal and vertical scaling capabilities with detailed cost-performance analysis
- Plan auto-scaling configurations and validate scaling policies under load
- Assess database scalability patterns and optimize for high-performance operations
- Create performance budgets and enforce quality gates in deployment pipelines
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 · 268 lines · 25 tokens per session scan A 4b770674491f
Performance Benchmarker is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (451 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 2,392 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-09-03.
Other agents, from other repositories
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
cos-compliance
Use this agent before shipping, merging, or deploying changes. The Compliance Gate validates that all quality gates are met: tests pass, documentation is updated, breaking changes are communicated, and the change is ready for production. Context: User wants to merge a feature branch user: "I think this PR is ready to…
frontend-specialist
A frontend verification agent that tests changed user-interface code in a real browser with Playwright, including screenshots for visual checks.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
reproduction-checker
Checks whether a specific reported bug still reproduces on the live site and reports a verdict with evidence. Use during a Bug Shepherd triage run.
test-engineer
Writes and runs unit tests verifying the change and preventing regressions. Follows project test framework conventions.