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 leek/filament-agent-rules --skill filament-formsgit clone --depth 1 https://github.com/leek/filament-agent-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/leek/filament-agent-rules/filament-forms)<a href="https://agentmods.dev/skills/leek/filament-agent-rules/filament-forms"><img src="https://agentmods.dev/badge/skills/leek/filament-agent-rules/filament-forms.svg" alt="Measured on agentmods" 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.00048 | $0.00924 |
| Opus 5 | $0.00024 | $0.00462 |
| Sonnet 5 | $0.00010 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
filament-forms 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 7d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Filament Form Workflow
Use this skill for form schemas in resources, actions, pages, widgets, or embedded schema components.
Read First
Resolve paths from the current project root:
app/Filament/CLAUDE.mdapp/Filament/Resources/Schemas/CLAUDE.mdapp/Providers/Filament/CLAUDE.md- If the form lives inside an action, also read
app/Filament/Actions/CLAUDE.md. - If tests are expected, read
tests/Feature/Filament/CLAUDE.md.
Inspect the model casts, migrations, relationships, validation rules, existing
global configureUsing() defaults, and any current form layout in nearby
resources.
Build Flow
- Return a configured
Filament\Schemas\Schemafrom the relevantconfigure()orform()method. - Organize fields into meaningful sections. Use a 12-column grid when the surrounding project does, size fields to their content, and pair related fields on shared rows.
- Choose components from data semantics: enum or finite set to
Select, temporal values to date/time pickers, booleans to toggles/checkboxes, paragraphs toTextareaor rich/markdown editors, related records to relationship-aware components. - Mirror model casts and database requirements. Add
required(),unique(ignoreRecord: true), numeric/date constraints, and relationship validation where appropriate. - Treat dehydration as the write boundary. Display-only fields use
dehydrated(false). Hidden privileged state must not persist accidentally. - For dependent fields, use Livewire state callbacks and reset stale child values when parent choices change.
- Prefer reusable schema component classes over duplicated heavy chains.
Avoid
- Flat full-width field lists.
- Free-text inputs for finite values.
- Re-declaring global component defaults.
- Custom Blade before built-in fields, layout components, prime components, or reusable schema component classes have been exhausted.
Deep Pattern: Component Class Vs Fragment
Use a component class when one heavily configured field deserves a named, reusable builder:
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.
- 7d ago First seen · 119 lines · 48 tokens per session scan A 1a600c30afac
filament-forms is a skill published in the GitHub repository leek/filament-agent-rules (4 stars, last pushed 28d ago), licensed MIT. It adds 48 tokens to every session and 924 once invoked, about $0.0002 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
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
om-system-extension
Extend installed Open Mercato modules through UMES enrichers, interceptors, mutation guards, widgets, menus, entity extensions, events, component/page replacements, and overrides. Use for "extend core", "add field/column/action", "hide page", "intercept API", "UMES", or "rozszerz moduł".
memstack-automation-webhook-designer
Use this skill when the user says 'webhook', 'webhook handler', 'webhook endpoint', 'receive events', 'HMAC verification', 'idempotency', or needs secure webhook handlers with signature verification, retry handling, and dead letter queues. Do NOT use for full n8n workflows or scheduled tasks.
backend-builder
A backend implementation role for Codex Project Autopilot, a workflow that coordinates project work. It builds the server-side logic and connects it to integrations according to an approved plan.
django-security
Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.
api-contract
A guide for defining and reviewing an API contract: the agreed shape of requests, responses, authentication, errors, and compatibility rules between services. It can also guide OpenAPI checks and contract testing, which verifies that systems follow those agreements.