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 skills add andreapollastri/larapilot --skill larapilot-shipgit clone --depth 1 https://github.com/andreapollastri/larapilotWrote 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/andreapollastri/larapilot/larapilot-ship)<a href="https://agentmods.dev/skills/andreapollastri/larapilot/larapilot-ship"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-ship.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.00101 | $0.04640 |
| Opus 5 | $0.00051 | $0.02320 |
| Sonnet 5 | $0.00020 | $0.00928 |
| Haiku 4.5 | $0.00010 | $0.00464 |
Grade A, and why
larapilot-ship 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 3d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Larapilot — Ship & Deploy
Release accepted increments to production. Oliver runs red-team assessment (findings → Lars); Lars runs OWASP blue-team gate; Jack orchestrates deploy; Sarah owns deploy/CI shell scripts and server-side glue Jack's runbooks invoke; Emma, Lauren, and Emily verify public-site readiness; Sophia seeds post-launch support runbook.
Shared Runtime
Read .larapilot/shared-runtime.md (core), then .larapilot/runtime-ship.md (deploy runbooks, OWASP/security, launch checks), .larapilot/runtime-ux.md (SEO/launch-adjacent UX), and .larapilot/runtime-ops.md (support runbook / Sophia).
Output Economy
Structured terse — see larapilot-ship in shared-runtime. Phase transitions: PASS / FAIL / BLOCKED + one-line reason. OWASP and launch findings as bullets or tables. Final report: structured fields only.
The Team
| Agent | Role |
|---|---|
| 🤖 Zoey | AI Guru — sharpens user intent, output economy, sub-agent orchestration, session/credit risk (every skill) |
| 🎯 Oliver | Ethical Hacker — red-team assessment & simulated attacks; reports findings to Lars |
| 🔐 Lars | Security Expert — OWASP-aligned pre-deploy assessment, GO/NO-GO verdict (incorporates Oliver's report) |
| 🚀 Jack | DevOps Engineer — deploy per PRD choice, edge/CDN/WAF, cloud, observability |
| ⌨️ Sarah | CLI / Git / Linux — deploy hooks, CI deploy jobs, release Git tagging/scripts, systemd/cron, SSH/rsync glue |
| 💰 Aurora | FinOps Expert — validates deploy target, infra/security budget; privileges security spend with Lars/Violet |
| ⚖️ Violet | Legal Expert — full privacy/legal launch gate: cookie/ToS, retention, anonymization, opt-out, subprocessors |
| 🌍 Emily | Translator — localized pages, currency/timezone correctness, per-market legal copy with Violet |
| 📈 Emma | SEO & Web Performance Specialist — URL structure, breadcrumbs, robots/sitemap/llms.txt, hreflang, Analytics, Lighthouse (public sites) |
| 💬 Lauren | Social Media Manager — marketing launch readiness, OG/share, campaign assets (public sites) |
| 📝 Albert | Tech Writer — release docs, OpenAPI finalization, PDF client manuals, migration guides |
| 🎧 Sophia | Support Manager — post-launch support runbook, bug-intake process, maintenance doc checklist |
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.
- 3d ago Changed 7cfd41af2e60
- 7d ago First seen · 317 lines · 101 tokens per session scan A 275a59950dc7
larapilot-ship is a skill published in the GitHub repository andreapollastri/larapilot (19 stars, last pushed 5d ago), licensed MIT. It adds 101 tokens to every session and 4,640 once invoked, about $0.0005 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
tcapi
A helper for managing Tencent Cloud resources through Tencent Cloud's command-line API tool. Tencent Cloud is a cloud-services provider offering products such as virtual servers, storage, networks, and containers.
atmos-migration
This skill helps you migrate a repository to Atmos. It covers native Terraform, Terraform Workspaces, Terramate, Terragrunt, Makefiles, Justfiles, and Taskfiles. It gives minimum-disruption paths, file-layout options, workspace mapping, task-to-command mapping, generatehcl/script decomposition, and the remote-state…
atmos-components
Component architecture: Terraform root modules, remote source provisioning, abstract components, component inheritance, versioning, mixins, catalog patterns.
atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.
atmos-design-patterns
Design patterns: stack organization, component catalogs, inheritance, configuration composition, version management, layered configuration.
atmos-kubernetes
Native Kubernetes components (experimental): render/plan/diff/apply/deploy/delete/validate via Kubernetes Go SDK server-side apply, components.kubernetes, kubectl/kustomize providers, paths/manifests, provision targets (cluster vs. GitOps repo), and auth.