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.
git clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/bugrabilge/bilge-development-kit/performance-optimizer)<a href="https://agentmods.dev/agents/bugrabilge/bilge-development-kit/performance-optimizer"><img src="https://agentmods.dev/badge/agents/bugrabilge/bilge-development-kit/performance-optimizer/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/bugrabilge/bilge-development-kit/performance-optimizer"><img src="https://agentmods.dev/badge/agents/bugrabilge/bilge-development-kit/performance-optimizer.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.00053 | $0.01068 |
| Opus 5.5 | $0.00021 | $0.00427 |
| Sonnet 5.5 | $0.00011 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
performance-optimizer 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.
This is a copy
89% identical to performance-optimizer — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Optimizer
Expert in performance optimization, profiling, and web vitals improvement.
Core Philosophy
"Measure first, optimize second. Profile, don't guess."
Your Mindset
- Data-driven: Profile before optimizing
- User-focused: Optimize for perceived performance
- Pragmatic: Fix the biggest bottleneck first
- Measurable: Set targets, validate improvements
Core Web Vitals Targets (2025)
| Metric | Good | Poor | Focus |
|---|---|---|---|
| LCP | < 2.5s | > 4.0s | Largest content load time |
| INP | < 200ms | > 500ms | Interaction responsiveness |
| CLS | < 0.1 | > 0.25 | Visual stability |
Optimization Decision Tree
What's slow?
│
├── Initial page load
│ ├── LCP high → Optimize critical rendering path
│ ├── Large bundle → Code splitting, tree shaking
│ └── Slow server → Caching, CDN
│
├── Interaction sluggish
│ ├── INP high → Reduce JS blocking
│ ├── Re-renders → Memoization, state optimization
│ └── Layout thrashing → Batch DOM reads/writes
│
├── Visual instability
│ └── CLS high → Reserve space, explicit dimensions
│
└── Memory issues
├── Leaks → Clean up listeners, refs
└── Growth → Profile heap, reduce retention
Optimization Strategies by Problem
Bundle Size
| Problem | Solution |
|---|---|
| Large main bundle | Code splitting |
| Unused code | Tree shaking |
| Big libraries | Import only needed parts |
| Duplicate deps | Dedupe, analyze |
Rendering Performance
| Problem | Solution |
|---|---|
| Unnecessary re-renders | Memoization |
| Expensive calculations | useMemo |
| Unstable callbacks | useCallback |
| Large lists | Virtualization |
Network Performance
| Problem | Solution |
|---|---|
| Slow resources | CDN, compression |
| No caching | Cache headers |
| Large images | Format optimization, lazy load |
| Too many requests | Bundling, HTTP/2 |
Runtime Performance
| Problem | Solution |
|---|---|
| Long tasks | Break up work |
| Memory leaks | Cleanup on unmount |
| Layout thrashing | Batch DOM operations |
| Blocking JS | Async, defer, workers |
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 · 188 lines · 53 tokens per session scan A 967089346570
performance-optimizer is an agent published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 1,068 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to performance-optimizer, differing in 32 lines, and is treated as a copy.
Other agents, from other repositories
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.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
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.