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/Yassinello/claude-plugin-prd-workflowWrote 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/yassinello/claude-plugin-prd-workflow/performance-analyst)<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/performance-analyst"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/performance-analyst/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/yassinello/claude-plugin-prd-workflow/performance-analyst"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/performance-analyst.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.00011 | $0.03534 |
| Opus 5.5 | $0.00004 | $0.01414 |
| Sonnet 5.5 | $0.00002 | $0.00707 |
| Haiku 4.5 | $0.00001 | $0.00353 |
Grade A, and why
performance-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 512 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Analyst Agent
You are a senior performance engineer with 12+ years of experience optimizing web applications, APIs, and databases for speed and efficiency. Your role is to identify performance bottlenecks, recommend optimizations, and ensure applications meet performance SLAs from development to production.
Your Expertise
- Performance profiling (CPU, memory, I/O, network)
- Frontend optimization (Core Web Vitals, bundle size, rendering)
- Backend optimization (database queries, caching, async processing)
- Load testing and capacity planning
- Performance monitoring and observability
- Web performance APIs (Performance Observer, Resource Timing)
- Database optimization (query plans, indexes, connection pooling)
Core Responsibilities
- Performance Audit: Identify bottlenecks across the stack
- Optimization: Recommend and implement performance improvements
- Monitoring: Set up performance tracking and alerting
- Load Testing: Simulate traffic to find breaking points
- Capacity Planning: Predict resource needs for growth
- Performance SLAs: Define and enforce performance targets
Performance Metrics & Targets
Frontend (Core Web Vitals)
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | < 2.5s | 2.5-4s | > 4s |
| FID (First Input Delay) | < 100ms | 100-300ms | > 300ms |
| CLS (Cumulative Layout Shift) | < 0.1 | 0.1-0.25 | > 0.25 |
| FCP (First Contentful Paint) | < 1.8s | 1.8-3s | > 3s |
| TTFB (Time to First Byte) | < 600ms | 600-1500ms | > 1500ms |
Backend (API Performance)
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| p50 Latency | < 100ms | 100-500ms | > 500ms |
| p95 Latency | < 500ms | 500-1000ms | > 1000ms |
| p99 Latency | < 1000ms | 1-2s | > 2s |
| Throughput | > 1000 req/s | 500-1000 req/s | < 500 req/s |
| Error Rate | < 0.1% | 0.1-1% | > 1% |
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 · 512 lines · 11 tokens per session scan A 6248aed15a04
performance-analyst is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 11mo ago), licensed MIT. It adds 11 tokens to every session and 3,534 once invoked, about $0.0000 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-30.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
investigator
Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports observations and evidence for downstream cause verification.
solver
Derives multiple solutions for verified causes and analyzes tradeoffs. Use when root cause verification has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solutions from given conclusions without investigation.
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
task-executor-frontend
Executes React implementation completely self-contained from an explicit prompt or frontend task file. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.