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 DominikTobureto/awesome-grok-build --skill performance-optimizergit clone --depth 1 https://github.com/DominikTobureto/awesome-grok-buildWrote 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/dominiktobureto/awesome-grok-build/performance-optimizer)<a href="https://agentmods.dev/skills/dominiktobureto/awesome-grok-build/performance-optimizer"><img src="https://agentmods.dev/badge/skills/dominiktobureto/awesome-grok-build/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/skills/dominiktobureto/awesome-grok-build/performance-optimizer"><img src="https://agentmods.dev/badge/skills/dominiktobureto/awesome-grok-build/performance-optimizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00369 |
| Opus 5 | $0.00018 | $0.00185 |
| Sonnet 5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
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 11d 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
Performance Optimizer
Measure first, optimize second, verify always.
Grok Build Mode
- Use Plan Mode before broad rewrites or caching changes.
- Use subagents for parallel investigation:
backend: endpoints, CPU, IO, concurrency.database: query shape, indexes, N+1, transactions.frontend: bundle, render loops, hydration, assets.infra: deploy, network, cache, limits.
- Arena-style optimization: compare approaches by measured impact, risk, and complexity.
- Human-in-the-loop: get approval before changing data model, cache semantics, or infra settings.
Workflow
- Define the metric and baseline.
- Reproduce or inspect evidence.
- Find the bottleneck with the least invasive tool available.
- Propose 2-3 fixes with tradeoffs.
- Implement the smallest fix.
- Re-measure or run a focused benchmark/test.
- Document the before/after.
Rules
- Do not optimize without a metric.
- Avoid caching correctness bugs.
- Prefer algorithm/query fixes over hardware assumptions.
- Keep performance tests stable and bounded.
- Watch for memory and bundle-size regressions.
Example Prompts
Use performance-optimizer. Investigate this p99 regression with subagents for backend, database, frontend, and infra. No edits until evidence is summarized.
Find the smallest measurable frontend performance win and verify it with a before/after check.
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.
- 11d ago First seen · 50 lines · 36 tokens per session scan A 14644a9e68c5
performance-optimizer is a skill published in the GitHub repository DominikTobureto/awesome-grok-build (61 stars, last pushed 18d ago), licensed MIT. It adds 36 tokens to every session and 369 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.
bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.