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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/performance-benchmarker)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/performance-benchmarker"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/performance-benchmarker/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/timurgaleev/vibestack/performance-benchmarker"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/performance-benchmarker.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.00036 | $0.02460 |
| Opus 5.5 | $0.00014 | $0.00984 |
| Sonnet 5.5 | $0.00007 | $0.00492 |
| Haiku 4.5 | $0.00004 | $0.00246 |
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 19d 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.
This is a copy
95% identical to Performance Benchmarker — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 273 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.
- 19d ago First seen · 273 lines · 36 tokens per session scan A 6db9ffe06db1
performance-benchmarker is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 2,460 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to Performance Benchmarker, differing in 31 lines, and is treated as a copy.
Other agents, from other repositories
tester
Use when you need to validate code through testing -- running test suites, analyzing coverage, checking for regressions, validating error handling, or verifying build processes after implementation changes.
Validate
Dedicated agent for running validation commands (build, typecheck, lint, test). Reports pass/fail with structured failure details - never fixes.
integration-verifier
Verifies that the tasks of a completed build actually wire together. Dispatched once at /execute Step 4 for multi-task specs. Read-only -- cannot modify the codebase. Checks cross-task wiring + global acceptance, not per-task acceptance.
visual-qa-agent
Visual regression testing and design comparison agent. Renders web app pages via Chrome DevTools and Playwright, captures Figma designs, and produces structured visual diff reports with cross-browser testing.
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.
security-validator
Use during a deep security scan to adversarially validate ONE candidate finding. Attempts to refute it, assigns confidence 1-10; findings below 8 are dropped. The false-positive filter of the pipeline.