filament-infolists

filament-infolists is a skill for Claude Code, Codex from leek/filament-agent-rules. It costs 42 tokens per session (918 once invoked), scanned A, original, MIT.

A guide for Filament infolists, which are read-only screens for displaying records in an admin panel. It covers entries, layouts, relationships, and computed or static content.

In plain words
What is it for?
Use it when creating or reviewing read-only views in Filament pages, action modals, relation managers, or custom pages.
Why use it?
It helps present record details clearly without treating read-only information like an editable form, while respecting sensitive data and project conventions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; installed under .agents/ (shared by several agents).

Good fit Use it when creating or reviewing read-only views in Filament pages, action modals, relation managers, or custom pages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/leek/filament-agent-rules/filament-infolists
Install

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.

Any agent
npx skills add leek/filament-agent-rules --skill filament-infolists
Clone the repo
git clone --depth 1 https://github.com/leek/filament-agent-rules

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for filament-infolists

README.md
[![agentmods](https://agentmods.dev/badge/skills/leek/filament-agent-rules/filament-infolists/github.svg)](https://agentmods.dev/skills/leek/filament-agent-rules/filament-infolists)
Your own site
<a href="https://agentmods.dev/skills/leek/filament-agent-rules/filament-infolists"><img src="https://agentmods.dev/badge/skills/leek/filament-agent-rules/filament-infolists/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.

agentmods 80×15 button for filament-infolists

Your own site · 80×15
<a href="https://agentmods.dev/skills/leek/filament-agent-rules/filament-infolists"><img src="https://agentmods.dev/badge/skills/leek/filament-agent-rules/filament-infolists.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 918 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.00918
Opus 5 $0.00021 $0.00459
Sonnet 5 $0.00008 $0.00184
Haiku 4.5 $0.00004 $0.00092

Measured 11d ago against content hash 397cd3e5428d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

filament-infolists 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 11d 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.

.agents/skills/filament-infolists/SKILL.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Filament Infolist Workflow

Use this skill for read-only record display. Infolists are schema component trees that use entries for display, layout components for structure, and prime components for static or computed content.

Read First

Resolve paths from the current project root:

  1. app/Filament/CLAUDE.md
  2. app/Filament/Resources/Schemas/CLAUDE.md
  3. app/Filament/Resources/Pages/CLAUDE.md when used on View pages
  4. app/Filament/Actions/CLAUDE.md when used in an action modal
  5. tests/Feature/Filament/CLAUDE.md when tests are expected

Inspect the model casts, relationships, sensitive attributes, existing form schema, and nearby view pages before designing the display.

Build Flow

  1. Use entries for read-only data: TextEntry, IconEntry, ImageEntry, ColorEntry, key-value/repeatable entries, and custom entries only when built-ins cannot represent the data.
  2. Group record facts by domain meaning, not by database order.
  3. Mirror the form's conceptual groups where that helps the admin compare edit and view surfaces.
  4. Use enum presentation contracts for labels, colors, and icons instead of duplicating match blocks across fields, columns, and entries.
  5. Use badges, icons, copyable values, placeholders, and date/money formatting where they make scanning easier.
  6. Keep sensitive values out of the infolist unless the current user is authorized to see them.

Review Checklist

  • Entries use Filament\Infolists\Components\*.
  • Layout wrappers use schema layout components.
  • Dot-notation relationship entries are loaded safely.
  • Long content is limited, wrapped, or placed in a full-width section.
  • View-page tests assert rendering and important displayed state.

Deep Pattern: Custom Entry Choices

Use the lowest-level escape hatch that fits:

  1. Built-in entry plus modifiers: TextEntry, IconEntry, ImageEntry, ColorEntry, ->badge()->color()->icon(), ->formatStateUsing(), trusted ->html(), ->markdown().
  2. Prime component or Callout when the content is not bound to a record attribute.
  3. ViewEntry for one-off bespoke record-bound markup.
  4. A custom entry class when reused or configurable.

Read the full file on GitHub · 107 lines

Changes

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.

  1. 11d ago First seen · 107 lines · 42 tokens per session scan A 397cd3e5428d

Subscribe to this mod's changes

filament-infolists is a skill published in the GitHub repository leek/filament-agent-rules (4 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 918 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.