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 pekral/cursor-rules --skill vite-patternsgit clone --depth 1 https://github.com/pekral/cursor-rulesWrote 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/pekral/cursor-rules/vite-patterns)<a href="https://agentmods.dev/skills/pekral/cursor-rules/vite-patterns"><img src="https://agentmods.dev/badge/skills/pekral/cursor-rules/vite-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/pekral/cursor-rules/vite-patterns"><img src="https://agentmods.dev/badge/skills/pekral/cursor-rules/vite-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.00052 | $0.02320 |
| Opus 5.5 | $0.00021 | $0.00928 |
| Sonnet 5.5 | $0.00010 | $0.00464 |
| Haiku 4.5 | $0.00005 | $0.00232 |
Grade A, and why
vite-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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vite Patterns (Laravel)
Asset bundling and dev-server patterns for Laravel apps using the official
laravel-vite-plugin. Covers vite.config.js, the @vite Blade directive,
HMR in development, env vars, aliases, manifests, production builds, code
splitting, and bundling for Livewire / Filament / Alpine.
Constraints
- Apply
@rules/laravel/laravel.mdc - Apply
@rules/laravel/livewire.mdcand@rules/laravel/filament.mdcwhen bundling assets for those layers - Apply
@rules/php/core-standards.mdcfor any PHP touched (Blade config exposure, service providers) - This stack uses
laravel-vite-pluginonly. Never introduce React/Vue plugins, SSR frameworks, library mode, Bun, or Next.js. - Secrets never go into
VITE_-prefixed vars — those are inlined into the public bundle. - Keep examples to
npm,php artisan serve, andnpm run dev/npm run build.
Use when
- Setting up or editing
vite.config.jswith thelaravel()plugin. - Wiring entrypoints and the
@vite([...])directive into Blade layouts. - Getting HMR / hot reload working in local development.
- Exposing config to the client via
VITE_env vars or Blade-side config. - Adding
resolve.aliaspaths, code splitting, or dynamic imports. - Understanding the manifest, cache-busting, and the production build.
- Bundling JS/CSS that Livewire, Filament, or Alpine depend on.
- Building assets in CI before deploy.
How it works
- Dev mode (
npm run dev) runs a Vite dev server that serves source files as native ESM and pushes HMR updates. Thelaravel-vite-pluginwrites apublic/hotfile; the@vitedirective detects it and points<script>/<link>tags at the dev server instead of built files. - Build mode (
npm run build) bundles, hashes, and writes assets topublic/build/plus amanifest.json.@vitereads the manifest and emits the hashed URLs. Cache-busting is automatic via the content hash in filenames. - Env vars prefixed
VITE_are statically inlined into the client bundle viaimport.meta.env. Everything else stays server-side.
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 · 284 lines · 52 tokens per session scan A 258a1f18e829
vite-patterns is a skill published in the GitHub repository pekral/cursor-rules (11 stars, last pushed 19d ago), licensed MIT. It adds 52 tokens to every session and 2,320 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
create-powergrid-plugin
Create a complete PowerGrid plugin from scratch, including PHP class, Column macro, Blade view, Alpine.js component, and registration.
laravel
Use when building or extending a Laravel 11/12 app — Eloquent models, migrations and relationships, routing with controllers and Form Requests, queues and background jobs, framework-native security (validation, mass-assignment, policies, signed URLs, rate limiting), and Pest/PHPUnit feature tests. NOT pure PHP…
owl-admin-app-dev
Use this skill when developing an application that installed slowlyo/owl-admin, especially backend CRUD, menus, permissions, controllers, services, routes, config/admin.php, app/Admin, helper functions, settings(), adminpages(), AdminPipeline, upload/file preview issues, route conflicts, custom login/menu examples, or…
owl-admin-devtools-generator
A development guide for Owl Admin, a Laravel-based administration system, covering its code generator, API templates, relationships, and visual pages.
owl-admin-ops-commands
Use this skill for Owl Admin installation, publishing assets, upgrades, diagnostics, database inspection, menu maintenance, user creation, password reset, route generation, IDE helper, admin:publish, admin:install, admin:update, admin:doctor, admin:db, admin:menu, admin:create-user, or deployment troubleshooting.
owl-admin-extension-module
A development guide for Owl Admin extensions and modules. An extension adds optional functionality, while a module groups related routes, settings, menus, and permissions.