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-testinggit 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-testing)<a href="https://agentmods.dev/skills/leek/filament-agent-rules/filament-testing"><img src="https://agentmods.dev/badge/skills/leek/filament-agent-rules/filament-testing.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.00045 | $0.00625 |
| Opus 5 | $0.00023 | $0.00313 |
| Sonnet 5 | $0.00009 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
filament-testing 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Filament Testing Workflow
Use this skill for focused Pest + Livewire feature coverage of Filament admin surfaces.
Read First
Resolve paths from the current project root:
tests/Feature/Filament/CLAUDE.mdapp/Filament/CLAUDE.md- The rule file for the surface under test:
app/Filament/Resources/CLAUDE.mdapp/Filament/Resources/Schemas/CLAUDE.mdapp/Filament/Resources/Tables/CLAUDE.mdapp/Filament/Actions/CLAUDE.mdapp/Filament/Widgets/CLAUDE.mdapp/Filament/Resources/RelationManagers/CLAUDE.md
Inspect existing test style, factories, panel access rules, policies, and database refresh conventions before adding tests.
Build Flow
- Authenticate a user that passes the panel access check in setup.
- Add the lowest-cost render test for every page, relation manager, or widget touched.
- For forms, test create/edit success, required validation, unique rules with current-record ignore behavior, relationship fields, and conditional state.
- For tables, test visible records, search, sort, filters, important columns, dot-notation rendering, row actions, and bulk actions.
- For actions, test success, validation failures, visibility/authorization, redirects/downloads, and resulting database state.
- For authorization, test both allowed and forbidden users when the behavior is security relevant.
- Keep tests targeted. Do not snapshot whole rendered pages.
Review Checklist
- Successful saves assert no form/action errors.
- Factories create all related data needed by fields, filters, and columns.
- Assertions check database state after mutations.
- Tests cover the regression risk introduced by the change, not unrelated framework behavior.
Helper Reference
Common Filament Livewire helpers:
| Helper | Use |
|---|---|
callAction('name') |
header/footer action |
callAction('name', data: [...]) |
action with modal form state |
callTableAction('name', $record) |
row action |
callTableBulkAction('name', $records) |
bulk action |
assertActionVisible('name') / assertActionHidden('name') |
action visibility |
assertHasNoActionErrors() / assertHasActionErrors([...]) |
action modal validation |
assertFormSet([...]) |
hydrated form state |
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 · 67 lines · 45 tokens per session scan A b4f93cf993ae
filament-testing is a skill published in the GitHub repository leek/filament-agent-rules (4 stars, last pushed 28d ago), licensed MIT. It adds 45 tokens to every session and 625 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
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
unity-agent-workflows
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first…
laravel-tdd
Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
eval-harness
An evaluation framework for AI-assisted development that defines pass/fail criteria, measures pass@k reliability, and runs regression checks. Eval-driven development means testing an agent's expected behavior before and after changes, much like tests for software.