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 majdghithan/agent-skills --skill filament-plugin-developmentgit clone --depth 1 https://github.com/majdghithan/agent-skillsWrote 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/majdghithan/agent-skills/filament-plugin-development)<a href="https://agentmods.dev/skills/majdghithan/agent-skills/filament-plugin-development"><img src="https://agentmods.dev/badge/skills/majdghithan/agent-skills/filament-plugin-development.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.00105 | $0.02198 |
| Opus 5 | $0.00053 | $0.01099 |
| Sonnet 5 | $0.00021 | $0.00440 |
| Haiku 4.5 | $0.00011 | $0.00220 |
Grade A, and why
filament-plugin-development 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 8d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building & publishing Filament plugins (v4 / v5)
A Filament "plugin" is just a Composer package that extends a Filament app. Verified against filamentphp.com/docs/4.x. v5 shares the same plugin API.
Two tiers - pick the smaller one
A. Plain package (components only). Ships resources/pages/widgets/fields/actions and does not implement any contract. The installing app wires them in manually (->resources([...]), ->widgets([...])). If your package is one widget or one field, do this - you do not need the Plugin contract.
B. Panel Plugin. A class implementing Filament\Contracts\Plugin, registered with ->plugin(YourPlugin::make()). Reach for this only when you bundle multiple things behind one registration, need per-panel configuration, or need boot-time logic. Rule of thumb: more than one moving part, or configurable -> Plugin contract; otherwise ship it plain.
The Plugin contract
Three methods:
| Method | Runs | Purpose |
|---|---|---|
getId(): string |
- | Globally-unique, stable singleton key (e.g. 'blog' - not 'settings', which clashes) |
register(Panel $panel): void |
while the panel is configured | register resources/pages/widgets/render hooks/assets on the panel |
boot(Panel $panel): void |
only for the active panel (via middleware) | runtime side effects |
namespace Vendor\FilamentBlog;
use Filament\Contracts\Plugin;
use Filament\Panel;
class BlogPlugin implements Plugin
{
public function getId(): string { return 'blog'; }
public function register(Panel $panel): void
{
$panel->resources([PostResource::class])
->pages([Settings::class])
->widgets([BlogOverviewWidget::class]);
}
public function boot(Panel $panel): void { /* runtime side effects here */ }
public static function make(): static { return app(static::class); } // install-side: ->plugin(BlogPlugin::make())
public static function get(): static { return filament(app(static::class)->getId()); } // read configured instance anywhere
}
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.
- 8d ago First seen · 163 lines · 105 tokens per session scan A 4b8157b3c76f
filament-plugin-development is a skill published in the GitHub repository majdghithan/agent-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 2,198 once invoked, about $0.0005 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
create-powergrid-plugin
Create a complete PowerGrid plugin from scratch, including PHP class, Column macro, Blade view, Alpine.js component, and registration.
build-me
Implement a solution write-up (typically the markdown file produced by /solve-me) in this Laravel project, following existing project patterns and Laravel best practices. Cuts the work into commits itself, writes the commit plan to docs/build/ .md, and gets the developer's approval before writing any code. Then builds…
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.
laravel-13-expert
Comprehensive Laravel 13.x expert skill covering the entire framework — installation, configuration, routing, controllers, middleware, Blade views, Eloquent ORM, migrations, queues, jobs, events, mail, notifications, caching, Redis, scheduling, service container, service providers, authentication, authorization, AI…
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
php-pro
Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invokes strict typing, PHPStan level 9, async patterns with Swoole, and PSR standards. Creates controllers, configures middleware, generates migrations, writes PHPUnit/Pest tests, defines typed DTOs and value objects…