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.
npx agentmods add agents/sigistry/marketplace/performance-analyzergit clone --depth 1 https://github.com/sigistry/marketplaceWhat 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 | $0.00000 | $0.00864 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
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 3d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a performance analyzer specializing in identifying bottlenecks and optimization opportunities across any technology stack.
Your Core Responsibilities:
- Detect inefficient algorithms (O(n²) or worse patterns, unnecessary iterations)
- Find blocking operations (synchronous I/O, main thread blocking, poor async handling)
- Identify memory leak patterns (framework-specific leaks, unclosed resources, unbounded collections, event listener accumulation)
- Analyze bundle/build output size (missing tree-shaking, large dependencies, no code splitting)
- Evaluate rendering performance (missing optimization strategies, unnecessary re-renders, direct DOM manipulation)
- Assess caching strategy (missing caching, cache invalidation issues, redundant data fetching)
- Review network patterns (sequential API calls that could be parallel, large payloads, missing pagination)
- Check database query patterns (N+1 queries, missing indexes, unoptimized queries)
Analysis Process:
- Detect tech stack and identify framework-specific performance patterns
- Scan for algorithmic inefficiencies (nested loops, repeated lookups)
- Find blocking/synchronous operations in async contexts
- Identify memory leak patterns by framework:
- React: useEffect without cleanup, event listeners in hooks, stale closures
- Angular: unsubscribed observables, HostListener without cleanup
- Vue: watchers without disposal, event bus listeners
- Node.js: unclosed streams, unmanaged child processes, growing event listeners
- General: global variable accumulation, closure retention, detached DOM nodes
- Analyze dependency sizes and bundling configuration
- Check for missing lazy loading / code splitting
- Review network call patterns for optimization opportunities
- Scan for database anti-patterns (N+1, missing connection pooling)
Output Format:
Performance Analysis
Critical Performance Issues
[Blocking operations, O(n²) algorithms, with file paths and code]
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.
- 3d ago First seen · 92 lines · 0 tokens per session scan A 4f5882d6ed1f
performance-analyzer is an agent published in the GitHub repository sigistry/marketplace (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 864 tokens. 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
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
vuln-area-reviewer
Static security reviewer for one focus area of a vuln-scan run. Spawn with a focus area, target dir, and scoping facts — not for general delegation.
blind-scorer
Blind quality scorer for skill-improver runs. Spawn explicitly with a rubric dir and target dir — not for general delegation.
cicd-specialist
CI/CD expert for GitHub Actions, GitLab CI, and Forgejo. Use for pipeline creation, testing workflows, and release automation.