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.
git 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/rules/pekral/cursor-rules/filament)<a href="https://agentmods.dev/rules/pekral/cursor-rules/filament"><img src="https://agentmods.dev/badge/rules/pekral/cursor-rules/filament/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/rules/pekral/cursor-rules/filament"><img src="https://agentmods.dev/badge/rules/pekral/cursor-rules/filament.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.00000 | $0.00313 |
| Opus 5.5 | $0.00000 | $0.00125 |
| Sonnet 5.5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
filament 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.
What it actually says
Resources
- Generate smoke tests for every Filament Resource.
- When changing a Resource, add or update tests and ensure they pass.
- Do not add a View page or Infolist unless explicitly requested.
- Use
Resource::getUrl('index')with the exact Resource class.
Enums
- When enums back model fields, prefer implementing
HasLabel,HasColor, andHasIconwhere useful. - Use enum instances instead of hardcoded strings when an enum already exists.
- Do not append
->valuewhen defining enum defaults unless truly required. - Match Filament interface return types exactly.
Actions and Forms
- Use
->authorize('ability')on actions. - Do not use
Gate::authorize()orGate::allows()manually inside Filament actions. - In Filament v4, do not specify
ignoreRecord: trueforunique()when it is already the default. - Use
->schema()instead of deprecated->form()on actions and filters. - Use
->mutateDataUsing()instead of deprecated->mutateFormDataUsing().
UI
- Use
Filament\\Support\\Icons\\Heroiconfor icons instead of raw strings. - For custom Blade files with Tailwind, create and register a custom theme.
Testing
- Use
Livewire::test(...), notlivewire(...).
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 · 31 lines · 0 tokens per session scan A b3643a719596
filament is a cursor rule published in the GitHub repository pekral/cursor-rules (11 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 313 tokens. 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 cursor rules, from other repositories
owl-admin
A set of project rules for Owl Admin, a Laravel-based framework for building web administration panels. It guides how the project should use its page renderer, controllers, services, menus, permissions, APIs, and code generator.
php
Rules applied when working in PHP files (incl. Laravel, Symfony, WordPress).
laravel-boost
Cursor rule "laravel-boost" from karuhun-developer/ecommerce, covering laravel boost guidelines, foundational context, conventions, verification scripts and application structure & architecture.
laravel-boost
Cursor rule "laravel-boost" from laravel/locket, covering laravel boost guidelines, foundational context, conventions, verification scripts and application structure & architecture.
php-drupal-best-practices
PHP & Drupal Development Standards and Best Practices.
10-backend
Backend development rules for Laravel Admin applications, including route locations, controller structure, permissions, API responses, and list filtering. Laravel is a PHP framework for building web applications.