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 skills add sembraniteam/claude-plugins --skill bottleneck-patternsgit clone --depth 1 https://github.com/sembraniteam/claude-pluginsWrote 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/skills/sembraniteam/claude-plugins/bottleneck-patterns)<a href="https://agentmods.dev/skills/sembraniteam/claude-plugins/bottleneck-patterns"><img src="https://agentmods.dev/badge/skills/sembraniteam/claude-plugins/bottleneck-patterns/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/skills/sembraniteam/claude-plugins/bottleneck-patterns"><img src="https://agentmods.dev/badge/skills/sembraniteam/claude-plugins/bottleneck-patterns.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.00122 | $0.00786 |
| Opus 5.5 | $0.00049 | $0.00314 |
| Sonnet 5.5 | $0.00024 | $0.00157 |
| Haiku 4.5 | $0.00012 | $0.00079 |
Grade A, and why
bottleneck-patterns 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bottleneck Patterns
Performance Bottleneck Patterns
Identify which domain matches the symptom, then apply the corresponding pattern. For the full symptom → pattern → fix lookup tables, see references/bottleneck-lookup.md.
Domain Quick Reference
Response Time: Tail latency (p99 >> p50), throughput ceiling, cold-path slowness, periodic spikes
Web: Render-blocking resources, large JS bundles, layout thrashing, missing CDN, high INP
API/Backend: N+1 queries, missing indexes, connection pool exhaustion, synchronous I/O, over-fetching
Memory: Monotonic heap growth (leak), burst allocation GC churn, premature promotion, unbounded cache
CPU: Busy-wait loops, hot codec (serialization), uncached regex, lock contention
Mobile (Android): ANR on main thread, UI jank, overdraw, WakeLock abuse, battery drain from background work
Mobile (iOS): Main thread I/O, deep autolayout graph, retain cycles, Core Data on main thread
Mobile (Flutter): Expensive build() methods, shader compilation jank, large isolate messages, heavy list cells
Networking: Chatty API, missing compression, no connection reuse, oversized images, sequential loading
Database: Missing indexes (EXPLAIN ANALYZE first — parse PostgreSQL JSON output deterministically with the profiler-analysis skill's scripts/parse-profiler.py --format pg-explain), SELECT *, missing composite index, ORM over-fetching
Diagnostic Approach
- Match the symptom to a domain from the quick reference above
- Look up the specific pattern and fix in
references/bottleneck-lookup.md - Confirm with data before implementing: run
EXPLAIN ANALYZE, attach a profiler, or measure with a benchmark — for.cpuprofile/pprof -top/EXPLAIN ANALYZE JSONspecifically, useprofiler-analysis's parser script rather than reading raw output by eye - Apply the
impact-matrixskill to prioritize multiple findings
Cross-Domain Signals
Some symptoms span multiple domains — check these cross-cutting patterns first:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 56 lines · 122 tokens per session scan A 251f45aa7219
bottleneck-patterns is a skill published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 122 tokens to every session and 786 once invoked, about $0.0005 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.