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 electrikhq/slate --skill electrik-slategit clone --depth 1 https://github.com/electrikhq/slateWrote 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/electrikhq/slate/electrik-slate)<a href="https://agentmods.dev/skills/electrikhq/slate/electrik-slate"><img src="https://agentmods.dev/badge/skills/electrikhq/slate/electrik-slate/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/electrikhq/slate/electrik-slate"><img src="https://agentmods.dev/badge/skills/electrikhq/slate/electrik-slate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 30 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00072 | $0.00492 |
| Opus 5 | $0.00036 | $0.00246 |
| Sonnet 5 | $0.00014 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
electrik-slate 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 9d 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
Quick facts
- Package:
electrik/slate(Composer), line3.x/^3.0 - Blocks:
electrik/slate-blocks— curated<x-slate-block::*>sections (~24) - Docs: https://slate.electrik.dev
- AI index: https://slate.electrik.dev/llms.txt
- MCP:
@electrik/slate-mcpin repomcp/(read-only docs + Blade source)
Do
- Fetch component docs (
/components/{slug}.md) or use MCPget_component_docsbefore coding. - Use progressive form props and documented composition trees.
- Prefer
<x-slate-block::*>from the package for login, settings, pricing, FAQ, CTA, app shell — do not paste one-off demos from thin gallery wrappers unless adapting props. - Keep Alpine state on the Slate root for overlays.
- Theme via
--slate-*tokens (default is neutral/achromatic; accents are optional).
Don't
- Invent a
npx slate add/ registry install flow. - Generate React, Vue, or shadcn/ui TSX for Slate apps.
- Nest identical
<x-slate::*>components or put@ifin opening tags. - Treat slate-blocks as a thousand-block marketplace — curated Electrik-shaped set only.
Toast snippet
<x-slate::toaster />
<x-slate::button
@click="$dispatch('slate-toast', { title: 'Saved', variant: 'success' })"
>
Save
</x-slate::button>
Block snippet
<x-slate-block::hero
title="Ship your SaaS"
description="Auth, teams, and billing on Laravel."
primary-href="/install"
primary-label="Install"
/>
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.
- 9d ago First seen · 57 lines · 72 tokens per session scan A 90e4ca4fce71
electrik-slate is a skill published in the GitHub repository electrikhq/slate (27 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 492 once invoked, about $0.0004 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
livewire
Version-aware best practices for Laravel Livewire (Caleb Porzio's full-stack framework), covering v1 through v4. Use whenever building, reviewing, or upgrading Livewire components, wire:model bindings, actions, events, validation, lifecycle hooks, or single-file/island components. ALWAYS detects the installed Livewire…
olakunlevpn-filament-skills
Use when writing, reviewing, or refactoring Filament PHP v5 code -- resources, forms, tables, infolists, actions, widgets, panels, relation managers, multi-tenancy, testing, or plugin development. Always apply these standards to all Filament work.
livewire-reference
Use for all Laravel Livewire work. Covers Livewire v4 components, page routes, wire directives, PHP attributes, forms, validation, uploads, pagination, tables, modals, events, islands, performance, JavaScript, Alpine integration, Volt, Pest tests, upgrades, and debugging. Use it before you create, change, review…
craft-view
Crafting package views. Blade components, view publishing, and the visual contract with your consumers.
laravel-best-practices
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization…
laravel-livewire
Build dynamic, reactive Laravel applications using Livewire. Create real-time interfaces without writing JavaScript for SPA-like experiences.