Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/olakunlevpn/olakunlevpn-deployment-skills/olakunlevpn-deployment-skills)<a href="https://agentmods.dev/skills/olakunlevpn/olakunlevpn-deployment-skills/olakunlevpn-deployment-skills"><img src="https://agentmods.dev/badge/skills/olakunlevpn/olakunlevpn-deployment-skills/olakunlevpn-deployment-skills/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/olakunlevpn/olakunlevpn-deployment-skills/olakunlevpn-deployment-skills"><img src="https://agentmods.dev/badge/skills/olakunlevpn/olakunlevpn-deployment-skills/olakunlevpn-deployment-skills.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.00061 | $0.02793 |
| Opus 5 | $0.00030 | $0.01396 |
| Sonnet 5 | $0.00012 | $0.00559 |
| Haiku 4.5 | $0.00006 | $0.00279 |
Grade A, and why
olakunlevpn-deployment-skills 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel Deployment Scripts
Generate production-ready deployment scripts for Laravel + Inertia applications. Two scripts: manual deploy and auto-deploy with GitHub polling. Always ask for the project path and log path before generating.
Rules
- ALWAYS ask for the server project directory path and log directory path before generating scripts. These are SERVER paths, not local machine paths. Every server is different.
- NEVER hardcode paths, usernames, domains, or server-specific values. The scripts use configurable variables at the top that the user sets once for their server.
- NEVER skip migration. Always include
php artisan migrate --force --no-interaction. - ALWAYS clear and rebuild cache.
optimize:clearthenoptimizein that order. - ALWAYS stash local changes before pulling. Prevents merge conflicts on server.
- ALWAYS include error handling. Scripts should exit on failure with clear error messages.
- NEVER run
npm run devin production. Alwaysnpm run build. - ALWAYS log deployments with timestamps.
- Auto-deploy checks every 2 minutes by default. Configurable.
- Both scripts must be in the project root and added to
.gitignore.
Phase 1: Gather Information
Before generating anything, you MUST ask the user these questions. Do NOT assume any answers. Do NOT generate scripts until all required answers are collected.
ASK THESE QUESTIONS (one message, wait for all answers):
1. "What is the full server path to your project?"
Example: /home/ubuntu/htdocs/example.com
This is the path ON THE SERVER, not your local machine.
2. "Do you need npm install and npm run build in the deploy?"
- YES = project has frontend assets (React, Vue, Vite, etc.)
- NO = backend-only project, no frontend build step
3. "Do you need composer install in the deploy?"
- YES = always run composer install on deploy
- AUTO = only run when composer.lock changes (recommended)
- NO = skip composer entirely
4. "What git branch do you deploy from?" (default: main)
5. "Does your project use any of these? (list all that apply)"
- Filament (adds filament:optimize + icons:cache)
- Queue workers (adds queue:restart)
- Horizon (adds horizon:terminate)
- Reverb/WebSockets (adds reverb:restart)
- None of the above
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.
- 12d ago First seen · 388 lines · 61 tokens per session scan A e61808fb6036
olakunlevpn-deployment-skills is a skill published in the GitHub repository olakunlevpn/olakunlevpn-deployment-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 2,793 once invoked, about $0.0003 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.
Other skills, from other repositories
land-and-deploy
Land and deploy workflow. (gstack).
publish-site
Versioned site deploys to GitHub/Cloudflare/Netlify Pages.
csv
CSV data processing — view, filter, convert, merge tabular data. Zero barrier — use with x-cmd, Python, or awk. Use for "csv", "data", "table", "spreadsheet", "conversion".
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
atmos-vendoring
Component vendoring: vendor.yaml and component.yaml manifests, immutable vendor.lock.yaml receipts, pulling from Git/S3/HTTP/OCI/Terraform Registry, --stack/--labels/--tags selector composition, native vendor update, clean, diff, config, and reviewed local component copies.