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.
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/laravel/package-skeleton/package-releasenpx skills add laravel/package-skeleton --skill package-releasegit 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-release)<a href="https://agentmods.dev/skills/laravel/package-skeleton/package-release"><img src="https://agentmods.dev/badge/skills/laravel/package-skeleton/package-release.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.00044 | $0.00357 |
| Opus 5 | $0.00022 | $0.00179 |
| Sonnet 5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
package-release 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 5d 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-release — 100% identical, 0 lines differ
What it actually says
Package Release
Primary Goal
Prepare a safe package release checklist and implementation without tagging, pushing, or publishing unless the user explicitly approves that action.
Workflow
- Review
CHANGELOG.md, generated release notes config, GitHub release workflows, open diff, and pending package changes. - Validate the release state with
composer testbefore recommending a release. - Confirm whether version metadata needs to change; many Laravel packages rely on Git tags rather than a hardcoded package version.
- Review tag naming, release branch, and GitHub release workflow behavior before any release command.
- Do not tag, push, or publish without explicit user approval.
References
CHANGELOG.md.github/release.yml.github/workflows/update-changelog.yml.github/workflows/tests.ymlcomposer.json
Examples
- Prepare a release by checking changelog coverage, confirming generated release notes categories, running
composer test, and drafting the tag command for user approval. - Update release notes grouping in
.github/release.ymlwhen a new label convention is added.
Anti-Patterns
- Creating tags, pushing branches, or publishing releases without explicit approval.
- Skipping
composer testbefore a release recommendation. - Treating generated release notes as a replacement for meaningful
CHANGELOG.mdentries. - Changing release workflows without checking the supported matrix in
.github/workflows/tests.yml.
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.
- 5d ago First seen · 42 lines · 44 tokens per session scan A 60f93c34f96f
package-release is a skill published in the GitHub repository laravel/package-skeleton (60 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 357 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…