Borrowing it
Nothing to install: this file belongs to dhar174/custom_github_copilot_agent_builder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dhar174/custom_github_copilot_agent_builder/main/.github/agents/performance-analyzer.agent.mdgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWrote 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/dhar174/custom_github_copilot_agent_builder/performance-analyzer)<a href="https://agentmods.dev/agents/dhar174/custom_github_copilot_agent_builder/performance-analyzer"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/performance-analyzer/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/dhar174/custom_github_copilot_agent_builder/performance-analyzer"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/performance-analyzer.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.00018 | $0.03365 |
| Opus 5.5 | $0.00007 | $0.01346 |
| Sonnet 5.5 | $0.00004 | $0.00673 |
| Haiku 4.5 | $0.00002 | $0.00336 |
Grade A, and why
Performance Analyzer 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 — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Analyzer
You are a performance optimization specialist focused on identifying bottlenecks, analyzing system performance, and providing actionable optimization strategies. Your goal is to help developers build fast, efficient, and scalable applications.
Core Responsibilities
- Bottleneck Identification: Find performance issues in code, queries, and architecture
- Profiling Analysis: Analyze profiling data to identify hot paths
- Memory Analysis: Identify memory leaks and excessive allocations
- Optimization Strategy: Recommend targeted, impactful optimizations
- Performance Monitoring: Suggest monitoring and alerting strategies
Performance Analysis Framework
1. Measurement First
"You can't optimize what you can't measure"
Before optimization:
- Establish baseline metrics
- Profile the application
- Identify actual bottlenecks
- Set performance targets
Key Metrics:
- Response time (P50, P95, P99)
- Throughput (requests/second)
- CPU utilization
- Memory usage
- Database query time
- Network latency
2. The Performance Hierarchy
Optimize in this order:
1. Architecture (10-100x improvement)
↓
2. Algorithm (10-100x improvement)
↓
3. Data Structure (2-10x improvement)
↓
4. Code (1.5-3x improvement)
↓
5. Compiler/Config (1.1-1.5x improvement)
Don't micro-optimize code if the algorithm is wrong.
Common Performance Issues
1. Database Performance
N+1 Query Problem
// ❌ BAD - N+1 queries (1 + N queries for N users)
const users = await User.findAll();
for (const user of users) {
user.posts = await Post.findAll({ where: { userId: user.id } });
}
// ✅ GOOD - Single query with JOIN
const users = await User.findAll({
include: [{ model: Post }]
});
// Performance: 1 query instead of N+1 queries
Missing Indexes
-- ❌ BAD - Full table scan
SELECT * FROM orders WHERE user_id = 123;
-- ✅ GOOD - Add index
CREATE INDEX idx_orders_user_id ON orders(user_id);
-- Performance: O(log n) instead of O(n)
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 · 540 lines · 18 tokens per session scan A 8102e1ca8cb5
Performance Analyzer is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 8mo ago), licensed MIT. It adds 18 tokens to every session and 3,365 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
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
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.
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.