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 silvioventre/lovable-skills --skill shipgit clone --depth 1 https://github.com/silvioventre/lovable-skillsWrote 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/silvioventre/lovable-skills/ship)<a href="https://agentmods.dev/skills/silvioventre/lovable-skills/ship"><img src="https://agentmods.dev/badge/skills/silvioventre/lovable-skills/ship/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/silvioventre/lovable-skills/ship"><img src="https://agentmods.dev/badge/skills/silvioventre/lovable-skills/ship.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.00151 | $0.01023 |
| Opus 5 | $0.00076 | $0.00511 |
| Sonnet 5 | $0.00030 | $0.00205 |
| Haiku 4.5 | $0.00015 | $0.00102 |
Grade A, and why
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 11d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship
Getting live is three things: knowing what publishing actually does, checking the right things before it, and verifying the right things after it. Each has a failure mode that is invisible until someone else finds it.
What publishing actually does
Publishing deploys a snapshot of the current version. It is not a live link to your project. Once published, further edits keep changing the project and do not change the live site until you publish again.
This produces the single most common confusion: "my changes aren't showing on the live site." Almost always the answer is that the changes were never published. A dot appears on the Publish button when the project is ahead of the live version. Republishing is the fix, not debugging.
Two consequences worth stating explicitly:
- The live site is always behind or equal to the project, never ahead. When diagnosing a live-site problem, first establish whether the live version even contains the code you are reading. Debugging current source against a stale deployment wastes entire sessions.
- A published site does not expire. Preview share links do, after seven days. If someone reports a dead link, work out which of the two they were given.
Route the task
| The task | Playbook |
|---|---|
| About to publish for the first time | reference/preflight.md |
| "Am I ready to launch?" | reference/preflight.md |
| Who can see this, or how to make it private | reference/access.md |
| Sharing with a team, client, or reviewer | reference/access.md |
| Enabling or questioning public remixing | reference/access.md |
| Changes not showing on the live site | reference/after-publish.md |
| Verifying or updating a published app | reference/after-publish.md |
| Taking a published app down | reference/after-publish.md |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 63 lines · 151 tokens per session scan A 20ff948b0e5b
ship is a skill published in the GitHub repository silvioventre/lovable-skills (2 stars, last pushed 16d ago), licensed MIT. It adds 151 tokens to every session and 1,023 once invoked, about $0.0008 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
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
agent-resource-allocator
Agent skill for resource-allocator - invoke with $agent-resource-allocator.
flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform.
eng-runbook
A one-page engineering runbook: a practical guide for operating a software service. It includes alerts, dashboards, procedures, on-call information, and an incident checklist.
moai-platform-deployment
Deployment and hosting platform specialist covering Vercel, Railway, and Convex. Use when deploying applications, configuring edge functions, setting up continuous deployment, or managing serverless infrastructure.