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/omergulcicek/omergulcicek.comWrote 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/rules/omergulcicek/omergulcicek.com/performance)<a href="https://agentmods.dev/rules/omergulcicek/omergulcicek.com/performance"><img src="https://agentmods.dev/badge/rules/omergulcicek/omergulcicek.com/performance/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/rules/omergulcicek/omergulcicek.com/performance"><img src="https://agentmods.dev/badge/rules/omergulcicek/omergulcicek.com/performance.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.00000 | $0.00715 |
| Opus 5.5 | $0.00000 | $0.00286 |
| Sonnet 5.5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
performance 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance & Accessibility (Lighthouse 95+)
Constraints
- Measurement First: Avoid premature optimization. Identify specific bottlenecks via profiling (DevTools Performance tab) before applying any fixes.
- Performance Budgets:
- Core Web Vitals: LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1.
- API & Load: API response time < 200ms (p95). Time to Interactive (TTI) < 3.5s on 4G connections.
- Bundle Size: Keep initial feature chunks < 50kb. Enforce dynamic imports (
next/dynamic) for heavy dependencies.
- LCP Optimization: Use the
priorityattribute for the first visibleImage(Next.js) or hero assets to prioritize loading. - Image & Data Standards:
- Define explicit
widthandheightto prevent CLS. - Use
<picture>withsourcetags for complex art direction or resolution switching. - Prevent N+1 query patterns; strictly use pagination or optimized includes/joins for all data-driven components.
- Define explicit
- Icon & Font Strategy: Use tree-shakable icons (e.g.,
lucide-react). Applyswapdisplay strategy for fonts, optimized vianext/fontor local self-hosting. - A11y SSOT: All interactive elements MUST have
aria-label,role, or an associated<label>. Maintain WCAG AA compliance (4.5:1 contrast ratio). - Asset Links: Reference
ui-components.mdcfor specific Skeleton and Layout Shift (CLS) implementation rules.
Bans
- Layout Shift: Forbidden to render content without reserved dimensions (use Skeletons).
- Native Img: Forbidden to use raw
<img>tags. - Blocking JS: Forbidden to use heavy 3rd party scripts in the main thread (use
next/scriptor Web Workers). - A11y Gaps: Forbidden to use
divas a button withouttabIndexandonKeyDown. - Alt Text: Forbidden to leave
altattributes empty or generic (e.g., "image").
Correct Implementation
export const Hero = () => (
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 · 67 lines · 0 tokens per session scan A 64522fec8805
performance is a cursor rule published in the GitHub repository omergulcicek/omergulcicek.com (15 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 715 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-09-01.
Other cursor rules, from other repositories
styling-conventions
Provides comprehensive guidelines for writing CSS Modules specifically for UI components within the @vibe/core library (under packages/core/src/components/). This rule covers file naming conventions (e.g., ComponentName.module.scss), CSS nesting, mandatory browser compatibility, strategies for adopting newer CSS APIs…
color-token-management
Comprehensive guide for adding, modifying, and managing color tokens in the @vibe/style package. Covers SCSS theme files, build process, naming conventions, and special handling for hacker theme.
react-sot-storybook-parity
SOT component CSS ownership — Storybook preview must match live routes without per-page token overrides.
self-hosted-fonts-vite
Self-hosted fonts in Vite/TanStack Start — file location, @font-face import order, Webflow legacy family names.
widget-iframe-overlay
Floating widgets with iframes — z-index doesn't work, reserve layout space instead.
webflow-css-preservation
Keep Webflow class names and compiled CSS verbatim during migration; don't refactor to Tailwind utilities until visual parity is confirmed.