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 agentmods add instructions/electrikhq/slate/agents-mdgit clone --depth 1 https://github.com/electrikhq/slateWhat 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 | $0.00445 | $0.00445 |
| Opus 5 | $0.00222 | $0.00222 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
slate AGENTS.md 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 3d 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
Electrik Slate — agent notes
Use these rules when generating Laravel Blade UI with Electrik Slate (electrik/slate 3.x).
Stack
- Anonymous Blade components:
<x-slate::name /> - Tailwind CSS v4 + Slate OKLCH tokens (
--slate-*) - Alpine.js only when interactivity is required
- Livewire-friendly forms (do not invent React/shadcn or a CLI
addcommand)
Install reminder
composer require electrik/slate:^3.0
Import after Tailwind:
@import 'tailwindcss';
@import '../../vendor/electrik/slate/resources/css/slate.css';
Authoring rules
- Prefer progressive props:
label,description,errorMessageon form controls. - Do not nest the same Blade component inside itself.
- Do not put
@ifinside<x-slate::*>opening tags — compute classes in@phpfirst. - Use logical CSS (
start/end) overleft/rightwhen touching layout. - Mount
<x-slate::toaster />once in the layout; dispatchslate-toastbrowser events. - For busy buttons:
loading/loadingText(static/Alpine) or Livewirewire:loading. - Theme via CSS variables (
--slate-primary, etc.), not hardcoded hex in components. - Compose overlays from documented parts (
dialog+dialog-trigger+dialog-content, …).
AI sources
- https://slate.electrik.dev/llms.txt
- https://slate.electrik.dev/components/{name}.md
- MCP: see
mcp/README.mdand https://slate.electrik.dev/docs/ai
Good prompts for agents
- “Build a settings form with Slate progressive field props and a destructive alert.”
- “Use the login block pattern from slate.electrik.dev/blocks/login.”
- “Fetch dialog docs via MCP and wire Alpine open state.”
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.
- 3d ago First seen · 47 lines · 445 tokens per session scan A 96b71b8c6a2e
slate AGENTS.md is an instructions file published in the GitHub repository electrikhq/slate (25 stars, last pushed 7d ago), licensed MIT. It adds 445 tokens to every session, about $0.0022 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 instructions, from other repositories
wirekit AGENTS.md
Instructions for pushery/wirekit, covering wirekit — guidance for ai coding assistants, discover the api before authoring — do not guess, core conventions and full reference.
freek.dev CLAUDE.md
Claude Code instructions for spatie/freek.dev, covering laravel boost guidelines, foundational context, skills activation, conventions and verification scripts.
aura-ui AGENTS.md
Instructions for BlueStarSystem/aura-ui, covering agents.md — aura ui, what this is, how to use components, livewire integration and accessibility (do not regress).
aura-ui CLAUDE.md
Instructions for BlueStarSystem/aura-ui, covering aura ui — claude code context, architecture, key directories, commands and free/pro split.
laravel-vue-starter AGENTS.md
AGENTS.md instructions for gdarko/laravel-vue-starter, covering laravel boost guidelines, foundational context, skills activation, conventions and verification scripts.
laravel-vue-starter GEMINI.md
Gemini CLI instructions for gdarko/laravel-vue-starter, covering laravel boost guidelines, foundational context, skills activation, conventions and verification scripts.