Laravel Package Skeleton is a starter repository for creating Laravel packages, with package configuration, testing, static analysis, formatting, and a workbench application already set up. Laravel package developers use it as the starting point for new packages. The catalogue add-ons support workflows around this package template.
Borrowing it
Nothing to install: this file belongs to laravel/package-skeleton. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/laravel/package-skeleton/main/.agents/skills/package-scaffold/SKILL.mdgit clone --depth 1 https://github.com/laravel/package-skeletonWrote 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/laravel/package-skeleton/package-scaffold)<a href="https://agentmods.dev/skills/laravel/package-skeleton/package-scaffold"><img src="https://agentmods.dev/badge/skills/laravel/package-skeleton/package-scaffold/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/laravel/package-skeleton/package-scaffold"><img src="https://agentmods.dev/badge/skills/laravel/package-skeleton/package-scaffold.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 62 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00049 | $0.00787 |
| Opus 5 | $0.00024 | $0.00394 |
| Sonnet 5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
package-scaffold 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- package-scaffold — 94% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Package Scaffold
Primary Goal
Add package features in the right place and wire them through the service provider using explicit Laravel APIs, keeping package names, namespaces, config keys, and publish tags consistent.
Workflow
- Inspect the existing package structure, sibling examples, README setup notes, and the current service provider before creating files.
- Identify whether the request touches commands, migrations, routes, config, views, translations, assets, middleware, tests, README/contributing docs, compatibility, or release flow.
- Create the capability files under Laravel-native package paths and use the configured package names, namespaces, publish tags, URLs, and badges consistently.
- Wire the capability through the service provider using the patterns in Provider wiring below.
- Use
package-testingfor coverage, update README or contributing documentation when user-facing behavior changes, usepackage-compatibilityfor matrix-sensitive changes, and usepackage-releasefor release tasks. - Add only the files needed for the requested capability and validate with the narrowest relevant command before broader checks.
Provider Wiring
- Keep provider wiring in
register()orboot()unless extracting a method makes a real repeated concern clearer. - Put container bindings and
mergeConfigFromcalls inregister()when the host app must be able to override configuration. - Put resource loading in boot-time methods with Laravel-native APIs such as
loadRoutesFrom,loadViewsFrom, andloadTranslationsFrom. - Guard console-only publishing and command registration with
runningInConsole()before callingpublishes,publishesMigrations, orcommands. - Name publish tags with the
:package_slug-*convention so consumers can target individual resource groups. - Add tests for the observable provider behavior: merged config, loaded routes, publish tags, or command registration.
Provider wiring anti-patterns:
- Loading host app state too early during provider registration.
- Calling
env()outside config files; use config values aftermergeConfigFrominstead. - Registering web-only concerns unconditionally when the package can run in console contexts.
- Replacing explicit provider methods with
spatie/laravel-package-toolsby default.
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.
- 9d ago First seen · 64 lines · 49 tokens per session scan A 8711864d1e25
package-scaffold is a skill published in the GitHub repository laravel/package-skeleton (61 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 787 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-30.
Other skills, from other repositories
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…
create-powergrid-plugin
Create a complete PowerGrid plugin from scratch, including PHP class, Column macro, Blade view, Alpine.js component, and registration.
owl-admin-devtools-generator
A development guide for Owl Admin, a Laravel-based administration system, covering its code generator, API templates, relationships, and visual pages.
llamaindex-development
Expert guidance for LlamaIndex development including RAG applications, vector stores, document processing, query engines, and building production AI applications.
craftcms
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing…
php-development
Expert guidance for PHP 8+ development with SOLID principles, PSR standards, and modern best practices.