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 agentmods add skills/fusengine/agents/laravel-attributesnpx skills add fusengine/agents --skill laravel-attributesgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/laravel-attributes)<a href="https://agentmods.dev/skills/fusengine/agents/laravel-attributes"><img src="https://agentmods.dev/badge/skills/fusengine/agents/laravel-attributes.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 | $0.00036 | $0.01635 |
| Opus 5 | $0.00018 | $0.00817 |
| Sonnet 5 | $0.00007 | $0.00327 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade A, and why
laravel-attributes 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 today.
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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel 13 PHP Attributes
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Scan existing models/jobs/controllers for legacy
protected $fillable / $hidden / $connectionproperties to convert - fuse-ai-pilot:research-expert - Verify Laravel 13 release notes for attribute coverage and edge cases
- mcp__context7__query-docs - Pull authoritative examples from
laravel.com/docs/13.x
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
| Category | Attributes |
|---|---|
| Eloquent | #[Table] #[Connection] #[Fillable] #[Hidden] #[Visible] #[Guarded] #[Unguarded] #[Appends] #[Touches] |
| Queue / Job | #[Connection] #[Queue] #[Tries] #[Timeout] #[Backoff] #[MaxExceptions] #[FailOnTimeout] #[UniqueFor] |
| Console | #[Signature] #[Description] |
| Controllers | #[Middleware] #[Authorize] |
| Validation | #[RedirectTo] #[StopOnFirstFailure] |
| API Resources | #[Collects] #[PreserveKeys] |
| Factories / Seeders | #[UseModel] #[Seed] #[Seeder] |
Critical Rules
- NEVER mix attributes and legacy properties -
#[Fillable(['name'])]+protected $fillable = [...]causes Laravel to ignore the attribute silently - Class-level only - All Eloquent / Job / Controller attributes apply to the class, never to private/protected methods
- Single source of truth - Choose attributes OR properties per class; refactor in one pass to avoid drift
- Inheritance is additive - Child class attributes merge with parent attributes; redeclare to override
- Import the right namespace -
Illuminate\Database\Eloquent\Attributes\*for Eloquent,Illuminate\Queue\Attributes\*for Jobs
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/api-resources.md 1.2 KB
- references/console.md 1.1 KB
- references/controllers.md 1.4 KB
- references/eloquent.md 2.2 KB
- references/factories-seeders.md 1.5 KB
- references/queue.md 2.0 KB
- references/templates/Job-with-attributes.php.md 1.6 KB
- references/templates/Model-with-attributes.php.md 1.5 KB
- references/validation.md 1.3 KB
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.
- today Changed 7974e2b2934c
- yesterday First seen · 148 lines · 36 tokens per session scan A d32d72bf59e7
laravel-attributes is a skill published in the GitHub repository fusengine/agents (25 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,635 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-09-03.
Other skills, from other repositories
radin-record
Log feedback, bugs, follow-ups, or ideas raised mid-session as structured backlog entries, so they survive past the conversation. Use for /radin-record, "log this to the backlog", "add as follow-up/bug/idea", "record what we just found", "note this for later", "add findings to backlog". Triggers even on vague asks…
radin-doctor
Check that radin's own install under /.claude is complete and its optional companion tools are reachable. Use for /radin-doctor, "check my radin install", "is radin installed correctly", "radin doctor", "verify radin install".
designing-interfaces
Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed — whether creating from scratch or extracting patterns from existing code.
managing-product
Extracts product requirements and produces a PRD. Use when a user wants to build software and needs to define what to build before architecture or implementation, when scoping an MVP, or when translating a vague idea into a buildable specification.
orchestrating-software-dev
Runs software development projects from idea to completion. Use when starting a software project, adding a feature, fixing a bug, or resuming an in-progress build.
collecting-sources
Collects research sources with quality evaluation. Use when gathering or finding sources, building a source library, searching for academic papers, or performing RADAR assessment.