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 infohata/mind-vault --skill laravel-frontendgit clone --depth 1 https://github.com/infohata/mind-vaultWrote 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/infohata/mind-vault/laravel-frontend)<a href="https://agentmods.dev/skills/infohata/mind-vault/laravel-frontend"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/laravel-frontend/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/infohata/mind-vault/laravel-frontend"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/laravel-frontend.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.00177 | $0.03795 |
| Opus 5 | $0.00088 | $0.01898 |
| Sonnet 5 | $0.00035 | $0.00759 |
| Haiku 4.5 | $0.00018 | $0.00380 |
Grade A, and why
laravel-frontend 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
laravel-frontend
Production frontend patterns for Laravel 12, organised around the four client-surface contract concerns. The baseline is plain server-rendered Blade + a Bootstrap-style CSS framework + Vite + minimal vanilla JS (native fetch — axios is a drop-in alternative the adopter happens to use) — the actual stack of a real Laravel 12 rework PoC (server-rendered Blade, Bootstrap 5, Vite, vanilla JS; NO Livewire / Inertia / Flux / Tailwind / Alpine). Philosophy: the server renders truth as HTML, the browser does the minimum to enhance it. Livewire 4 and Inertia 2 are presented as opt-in variant layers, clearly marked [Variant: Livewire] / [Variant: Inertia]; Flux is a license-gated Livewire UI kit, never the default.
Pairs with: laravel for backend conventions (Form Requests, Eloquent eager-loading, Policies, queues). Load both on full-stack feature work — e.g. a controller returning a Blade fragment on an HX-Request and the full page otherwise.
When to use
TRIGGER when: editing Blade templates (resources/views/*.blade.php); wiring a server-rendered partial / fragment endpoint; adding a Blade component (<x-…>) or anonymous component; configuring or extending the Vite build (vite.config.js, resources/js/app.js); writing the vanilla-JS submit-lock; or working in a project that has opted into Livewire (wire:* attributes, app/Livewire/*), Inertia (@inertia, resources/js/Pages/*), or Flux (<flux:…>).
SKIP for: backend-only work (use laravel); pure API/JSON services with no server-rendered views; mobile-native clients; heavy offline-first PWAs needing a full client framework + API backend.
Stack / variant table
| Layer | What it is | When it applies |
|---|---|---|
| Baseline — plain Blade | Server-rendered Blade + Bootstrap-style CSS + Vite + minimal vanilla JS (native fetch; axios optional). No reactive framework. |
Default. Assume this unless a variant is detected or pinned. |
| [Variant: Livewire 4] | PHP component classes; wire:* directives; bundled Alpine for local-only UI. Ships in L12 starter kits. |
Project has wire:* in views / app/Livewire/*. |
| [Variant: Inertia 2] | Vue 3 / React 19 / Svelte 5 SFCs; JSON props over the adapter; client-side routing. | Project has @inertia + resources/js/Pages/*. |
| Flux (UI kit, not a variant) | Livewire's first-party <flux:…> component kit. Free tier + Pro tier (license-gated). |
Livewire-only, and only when Tailwind + Flux are installed. Never baseline. |
What ships with it
5 files 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.
- 11d ago First seen · 190 lines · 177 tokens per session scan A a5257fa9dd1b
laravel-frontend is a skill published in the GitHub repository infohata/mind-vault (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 177 tokens to every session and 3,795 once invoked, about $0.0009 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-31.
Other skills, from other repositories
symfony-backend
Use this skill when building Symfony backend applications — bundles, Doctrine ORM, Twig templates, Flex recipes, Messenger component. This skill enforces: service container autowiring, proper bundle structure, Doctrine mapping conventions, Flex-driven configuration. Do NOT use for: Laravel projects, WordPress plugins…
livewire-flux
Livewire 4 + Flux UI component scaffolder and pattern guide for Laravel projects. Generates Livewire components using Flux UI primitives — forms, data tables, modals, notifications, file uploads with Spatie Media Library, and role-gated UI with Spatie Permission. Supports both full-class and Volt single-file…
electrik-slate
Build Laravel Blade UI with Electrik Slate 3.x and optional slate-blocks. Use when writing x-slate or x-slate-block components, Livewire forms, tokens, toasts, blocks, or when the user mentions Slate, electrik/slate, electrik/slate-blocks, or slate.electrik.dev.
laravel-vite
Complete Vite bundling for Laravel - assets, HMR, SSR, frameworks, optimization. Use when configuring frontend build pipeline.
laravel:blade-components-and-layouts
Compose UIs with Blade components, slots, and layouts; keep templates pure and testable.
spatie-guidelines
Spatie's PHP, Laravel, JavaScript and Vue coding guidelines and conventions. Use when writing or reviewing PHP, Laravel, JavaScript, or Vue code for Spatie projects or packages. Covers code style, type declarations, docblocks, control flow, naming, routing, controllers, Blade, validation, comments, testing (Pest)…