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-dashboardgit 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-dashboard)<a href="https://agentmods.dev/skills/leek/filament-agent-rules/filament-dashboard"><img src="https://agentmods.dev/badge/skills/leek/filament-agent-rules/filament-dashboard/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/leek/filament-agent-rules/filament-dashboard"><img src="https://agentmods.dev/badge/skills/leek/filament-agent-rules/filament-dashboard.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.00048 | $0.00999 |
| Opus 5 | $0.00024 | $0.00500 |
| Sonnet 5 | $0.00010 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
filament-dashboard 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 10d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Filament Dashboard And Page Workflow
Use this skill for dashboards and custom panel pages. Prefer composing existing Filament widgets, schema components, and embedded Livewire components before building bespoke Blade-heavy pages.
Read First
Resolve paths from the current project root:
app/Filament/CLAUDE.mdapp/Filament/Pages/CLAUDE.mdapp/Filament/Widgets/CLAUDE.mdapp/Providers/Filament/CLAUDE.mdapp/Filament/Actions/CLAUDE.mdwhen the page has actionstests/Feature/Filament/CLAUDE.mdwhen tests are expected
Inspect existing panel pages, dashboard widgets, navigation groups, panel discovery paths, and global defaults.
Build Flow
- Decide whether the request is really a dashboard page. If the standard panel dashboard plus widgets is enough, register widgets instead of creating a page.
- If a custom page is needed, keep standard Filament page behavior and compose custom content through schema components, widgets, or embedded Livewire.
- Use tabs, sections, grids, callouts, and prime components for layout and explanatory content.
- Keep expensive metrics in widgets or query objects with clear caching, polling, and lazy-loading behavior.
- Use page header actions for page-level commands and delegate domain work.
- Register navigation metadata consistently with nearby pages and clusters.
- Add render tests and targeted assertions for critical widgets/actions.
Avoid
- Reimplementing a resource page as a custom page when only one area is custom.
- Large Blade views that bypass Filament theming and authorization.
- Dashboard queries that run expensive aggregates on every request without caching, filters, or lazy loading.
Deep Pattern: Tabbed Dashboard Pages
When a dashboard swaps widget sets without leaving the route, drive the tabs from a single array and keep widget references as class strings so Livewire can serialize state between requests.
final class Analytics extends Page
{
protected static string $view = 'filament.admin.pages.analytics';
public string $activeTab = 'overview';
public function getTabs(): array
{
return [
[
'key' => 'overview',
'title' => 'Overview',
'icon' => 'heroicon-o-home',
'widgets' => [OrdersOverview::class, RevenueChart::class],
],
[
'key' => 'revenue',
'title' => 'Revenue',
'icon' => 'heroicon-o-currency-dollar',
'widgets' => [RevenueBreakdown::class, TopProducts::class],
],
];
}
public function getActiveTabData(): ?array
{
return collect($this->getTabs())->firstWhere('key', $this->activeTab);
}
}
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.
- 10d ago First seen · 124 lines · 48 tokens per session scan A 1276f6b97dcd
filament-dashboard is a skill published in the GitHub repository leek/filament-agent-rules (4 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 999 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
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
miniapp-dev
A development guide for BitFun MiniApps, which are small applications that run inside BitFun. It covers creating new MiniApps as well as maintaining the MiniApp framework.
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
ss-studio
Turn a product brief and optional references into three distinct creative directions, a human-selected StyleSeed interaction plan, generated image/video asset jobs, a working UI prototype, and a verified prototype-first showcase reel. Use for client concepts, app interaction exploration, trendy but coherent UI…
ss-copy
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone.
ui-web
Web UI - glassmorphism, Tailwind, dark mode, accessibility.