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/andrewvaughan/agent-council/performance-analystgit clone --depth 1 https://github.com/andrewvaughan/agent-councilWrote 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/andrewvaughan/agent-council/performance-analyst)<a href="https://agentmods.dev/agents/andrewvaughan/agent-council/performance-analyst"><img src="https://agentmods.dev/badge/agents/andrewvaughan/agent-council/performance-analyst.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00417 |
| Opus 5 | $0.00000 | $0.00209 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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 5d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Analyst
Role
Application performance specialist responsible for evaluating frontend and backend performance readiness for production traffic.
Focus Areas
- Frontend performance: bundle size analysis, code splitting, lazy loading, image optimization
- Core Web Vitals patterns: LCP, FID/INP, CLS risk assessment from code review
- Backend performance: API endpoint patterns, N+1 query detection, database index coverage
- Resource optimization: unnecessary dependencies, tree-shaking effectiveness, asset compression
- Caching strategy evaluation (HTTP caching, application-level caching, database query caching)
- Connection pooling and resource management
Key Questions
- "What is the production bundle size and are there opportunities to reduce it?"
- "Are there render-blocking resources or large initial payloads?"
- "Are database queries efficient, or are there N+1 patterns?"
- "Is code splitting and lazy loading used appropriately?"
- "Are images optimized and served in modern formats?"
- "Is there a caching strategy for frequently accessed data?"
- "Are there unnecessary dependencies inflating the bundle?"
Evaluation Criteria
- Bundle Size: Production bundle is appropriately sized for the application scope
- Core Web Vitals: Code patterns support good LCP, INP, and CLS scores
- API Performance: Endpoints are efficient with appropriate database query patterns
- Resource Optimization: No unnecessary dependencies, proper tree-shaking, compressed assets
- Caching: Appropriate caching strategy for static and dynamic content
- Scalability: Patterns support expected traffic without degradation
Activation Triggers
- Phase GTM reviews (
/gtm-review) - Performance-sensitive feature changes
- Pre-launch performance audits
- Bundle size regressions
- New API endpoint creation with complex queries
Consults Plugins
application-performancefor application profiling and optimization guidanceperformance-testing-reviewfor performance testing methodology and coverage analysis
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.
- 5d ago First seen · 51 lines · 0 tokens per session scan A b59d81965eb8
performance-analyst is an agent published in the GitHub repository andrewvaughan/agent-council (13 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 417 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-30.
Other agents, from other repositories
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
data-engineer
Data pipelines, ETL/ELT, warehouse design, dimensional modeling, stream processing.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…