Borrowing it
Nothing to install: this file belongs to MrPunyapal/laravel-auditor. 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/MrPunyapal/laravel-auditor/main/.agents/skills/package-release/SKILL.mdgit clone --depth 1 https://github.com/MrPunyapal/laravel-auditorWrote 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/mrpunyapal/laravel-auditor/package-release)<a href="https://agentmods.dev/skills/mrpunyapal/laravel-auditor/package-release"><img src="https://agentmods.dev/badge/skills/mrpunyapal/laravel-auditor/package-release/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/mrpunyapal/laravel-auditor/package-release"><img src="https://agentmods.dev/badge/skills/mrpunyapal/laravel-auditor/package-release.svg" alt="Reviewed on agentmods" width="80" 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.5 | $0.00018 | $0.00143 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to package-release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 42 lines · 44 tokens per session scan A 60f93c34f96f
package-release is a skill published in the GitHub repository MrPunyapal/laravel-auditor (60 stars, last pushed 20d ago), licensed MIT. It adds 44 tokens to every session and 357 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to package-release, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
goshipit
Pre-launch codebase audit skill. Use this whenever someone is about to ship, deploy, launch, push to main/prod, or merge a release - even without "goshipit" explicitly. Trigger on: "is my app ready?", "can I deploy now?", "pre-deploy check", "review before launch", "is this production-ready?", "check my codebase"…
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
release
Evaluate readiness and publish to crates.io.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
changelog
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.
release-kotlin-library
Use when preparing, publishing, or checking readiness for a Kotlin library release, including verifying its gradle-maven-publish-plugin prerequisite, reconciling changelogs and API snapshots, and checking publication.