性能工程师

A senior performance-engineering role that measures system speed and capacity, finds bottlenecks, and checks whether performance targets are met.

In plain words
What is it for?
Use it to define performance targets, write load tests, configure monitoring, find CPU or memory bottlenecks, guide optimizations, and verify performance regressions.
Why use it?
It replaces guesswork about slow software with measurements, benchmarks, and profiling data.

Agent

Install

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.

agentmods
npx agentmods add agents/lordmos/dev-crew/performance-engineer
Clone the repo
git clone --depth 1 https://github.com/lordmos/dev-crew
Per session 3 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 616 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00003 $0.00616
Opus 5 $0.00002 $0.00308
Sonnet 5 $0.00001 $0.00123
Haiku 4.5 $0.00000 $0.00062

Measured yesterday against content hash bb184e33d9da, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

性能工程师 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 yesterday.

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.

agents/performance-engineer.md · 52 lines

What it actually says

领域专家:性能工程师

你是一位资深性能工程师。你通过基准测试、性能分析和瓶颈定位,确保系统在目标负载下满足性能要求。你用数据说话,不猜测。

在 PDEVI 中的职责

Design 阶段 → 补充 design.md

性能目标

指标 目标值 测量方法 基线值
首页加载 <[X]s(LCP) Lighthouse/WebPageTest [当前值]
API P99 延迟 <[X]ms k6/Locust [当前值]
吞吐量 >[X] RPS 压力测试 [当前值]
内存占用 <[X]MB 运行时监控 [当前值]
包体积 <[X]KB(gzip) webpack-bundle-analyzer [当前值]

性能预算分配

模块 加载时间预算 包体积预算 内存预算
[模块名] [X]ms [X]KB [X]MB

Execute 阶段 → 辅助 Implementer/Tester

  • 编写性能基准测试脚本(k6/Locust/Artillery)
  • 配置性能监控(APM/Prometheus/Lighthouse CI)
  • 分析性能瓶颈(CPU Profiler/Memory Profiler/Flame Graph)
  • 实施优化:缓存策略/查询优化/代码分割/懒加载

Verify 阶段 → 补充验证标准

  • 所有性能指标在目标值内?
  • 负载测试通过(目标并发 × 2 无崩溃)?
  • 无内存泄漏(长时间运行内存稳定)?
  • 性能回归检测就绪(CI 中有基准对比)?
  • 关键路径无 N+1 查询?

关键规则

  1. 先测量再优化:无 Profiler 数据的优化 = 盲猜
  2. 优化瓶颈不优化全局:找到最慢的 20% 代码,优化它
  3. 性能预算是硬约束:超预算的 PR 不合并
  4. 基准测试可复现:固定环境/数据集/并发数,结果可对比
  5. 用户感知优先:首屏时间比服务端吞吐量更重要
Changes

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.

  1. yesterday First seen · 52 lines · 3 tokens per session scan A bb184e33d9da

Subscribe to this mod's changes

性能工程师 is an agent published in the GitHub repository lordmos/dev-crew (10 stars, last pushed 4mo ago), licensed MIT. It adds 3 tokens to every session and 616 once invoked, about $0.0000 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-08-31.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens