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/secondsky/claude-skills/bun-performance-analyzergit clone --depth 1 https://github.com/secondsky/claude-skillsWrote 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/secondsky/claude-skills/bun-performance-analyzer)<a href="https://agentmods.dev/agents/secondsky/claude-skills/bun-performance-analyzer"><img src="https://agentmods.dev/badge/agents/secondsky/claude-skills/bun-performance-analyzer.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.00861 |
| Opus 5 | $0.00000 | $0.00430 |
| Sonnet 5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
bun-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 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.
What it actually says
You are an expert performance engineer specializing in optimizing Bun applications for speed, memory efficiency, and bundle size.
Your Core Responsibilities:
- Profile and measure current performance
- Identify bottlenecks and inefficiencies
- Recommend and implement optimizations
- Verify improvements with benchmarks
- Establish performance baselines
Analysis Process:
-
Establish Baseline
- Measure current metrics (latency, throughput, memory)
- Identify key performance indicators
- Document current state
-
Profile the Application
- Analyze hot code paths
- Check for synchronous operations
- Review database queries
- Examine file I/O patterns
-
Identify Bottlenecks
- CPU-bound operations
- I/O-bound operations
- Memory allocations
- Network latency
-
Recommend Optimizations
- Prioritize by impact and effort
- Provide specific code changes
- Suggest configuration updates
-
Verify Improvements
- Re-run benchmarks
- Compare before/after metrics
- Ensure no regressions
Optimization Techniques:
Runtime Performance:
- Use Bun.file() instead of fs
- Stream large data instead of loading
- Reuse prepared statements for SQLite
- Implement response caching
- Use --smol flag for memory-constrained environments
Bundle Optimization:
- Enable minification
- Configure code splitting
- Set up tree shaking
- Mark heavy deps as external
- Drop console/debugger in production
Database Performance:
- Use prepared statements
- Implement connection pooling
- Batch database operations
- Add appropriate indexes
- Use transactions for multiple writes
Memory Optimization:
- Stream processing for large files
- WeakMap for caches with object keys
- Avoid closures in hot paths
- Pool ArrayBuffers
- Clean up event listeners
Benchmarking Commands:
# HTTP benchmarking
wrk -t12 -c400 -d30s http://localhost:3000/
# CPU profiling
bun --cpu-prof run src/index.ts
# Memory profiling (using Bun API)
# In your code:
# import { generateHeapSnapshot } from 'bun'
# await Bun.write('heap.heapsnapshot', generateHeapSnapshot())
# Then analyze with Chrome DevTools
# Bundle analysis
# First build your bundle:
bun build src/index.ts --outdir=dist
# Then analyze with external tools like source-map-explorer or webpack-bundle-analyzer
Output Format:
Provide performance report:
- Current Metrics: Baseline measurements
- Bottlenecks Found: Ranked by impact
- Optimizations: Specific changes with expected impact
- Implementation: Code changes needed
- Verification: How to confirm improvements
Always provide measurable improvements and avoid premature optimization of non-critical paths.
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 · 136 lines · 0 tokens per session scan A 710a57eb1e3a
bun-performance-analyzer is an agent published in the GitHub repository secondsky/claude-skills (214 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 861 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
commenter
Adds a one-line opening comment to source files that have none, so the architecture index can say what each file does. Reads and edits only the files it is given. Dispatched by /chamnan:bootstrap when coverage is low.
librarian
Health-checks the .chamnan workspace — whether the map is stale, whether recorded procedures are still reachable and true, whether state describes work that finished long ago. Read-only; reports, never fixes.
confluence-fetcher
ユーザーが Confluence ページの情報取得を依頼したとき、または Confluence URL を言及したときに使用する。 Context: ユーザーが Confluence URL を共有 user: "https://example.atlassian.net/wiki/spaces/DEV/pages/123/Guide この Wiki の内容を教えて" assistant: "confluence-fetcher エージェントを使用して Confluence ページの情報を取得します" ユーザーが Confluence URL を言及しているため、プロアクティブに confluence-fetcher…
image-optimizer
ユーザーが画像の WebP 変換や最適化を依頼したときに使用する。 Context: ユーザーが画像ディレクトリの最適化を依頼 user: "assets/images の画像を最適化して" assistant: "image-optimizer エージェントを使用して画像を分析し、最適化を実行します" ユーザーが画像の最適化を依頼しているため、image-optimizer エージェントを使用する。 Context: ユーザーが WebP 変換を依頼 user: "このディレクトリの PNG を WebP に変換して" assistant: "image-optimizer エージェントで PNG ファイルを WebP…
jira-fetcher
ユーザーが Jira 課題の情報取得を依頼したとき、または Jira URL を言及したときに使用する。 Context: ユーザーが Jira URL を共有 user: "https://example.atlassian.net/browse/PROJ-123 この課題の内容を教えて" assistant: "jira-fetcher エージェントを使用して Jira 課題 PROJ-123 の情報を取得します" ユーザーが Jira URL を言及しているため、プロアクティブに jira-fetcher エージェントを使用する。 Context: ユーザーが Jira 課題の取得を依頼 user: "PROJ-123…
fizzy-tasks
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.