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 imprezahost/impreza-mcp --skill deploy-an-appgit clone --depth 1 https://github.com/imprezahost/impreza-mcpWrote 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/imprezahost/impreza-mcp/deploy-an-app)<a href="https://agentmods.dev/skills/imprezahost/impreza-mcp/deploy-an-app"><img src="https://agentmods.dev/badge/skills/imprezahost/impreza-mcp/deploy-an-app/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/imprezahost/impreza-mcp/deploy-an-app"><img src="https://agentmods.dev/badge/skills/imprezahost/impreza-mcp/deploy-an-app.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.00056 | $0.00772 |
| Opus 5.5 | $0.00022 | $0.00309 |
| Sonnet 5.5 | $0.00011 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
deploy-an-app 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 15d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploying to an Impreza VPS
Nothing here is synchronous
This is the single thing that goes wrong most often. A deploy call returns an id, not a result. The container is still being pulled while you are reading the response. If you answer "done" at that point you are guessing, and roughly half the time you are wrong.
Every long-running family works this way: deploys, backups, scheduled task runs, app reads and CLI runs. The call starts the work; a second tool reports how it went.
So the shape of every deploy is:
- start it, keep the id
- poll
impreza_list_deployments(orimpreza_get_environment_deployfor an environment deploy) until the status settles - only then say what happened
A deploy that has not settled is not a deploy that failed. Say it is still running.
Pick the server first
impreza_list_servers shows what the account owns and which boxes are online.
An app has to land on one of those. If the account has no server yet, see the
start-from-nothing skill — buying one is a separate arc with its own rules
about money.
Catalog or custom
Catalog (impreza_list_apps → impreza_deploy_catalog_app) is the fast
path: WordPress, Nextcloud, Gitea, n8n, Vaultwarden and the rest arrive
configured, not at a setup wizard. Prefer it whenever the request names
something in the catalog. Search the catalog before assuming an app is missing.
Custom (impreza_deploy_custom) takes the customer's own image, Dockerfile
or git repository. Reach for it when the app is theirs.
For a Compose stack, impreza_prepare_compose first: it turns the file into
something the platform can accept and tells you what it refused and why. Do not
hand-translate a Compose file yourself.
After it settles
impreza_probe_deployment answers the question the status field does not: is it
reachable over public HTTPS. A deployment can be running and still not serve,
because DNS or the certificate is not there yet. If the customer asked for a
working site, probe before you claim one.
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.
- 15d ago First seen · 75 lines · 56 tokens per session scan A 8699fed89c7d
deploy-an-app is a skill published in the GitHub repository imprezahost/impreza-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 772 once invoked, about $0.0002 per session on Opus 5.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-09-30.
Other skills, from other repositories
portaljs-deploy
Deploy a PortalJS portal to PortalJS Arc — Datopian-managed static hosting on Cloudflare. Builds a static export, uploads it, and returns a live SLUG.arc.portaljs.com URL. One command, one target. Use when a portal is ready to publish or redeploy to a live URL.
ship
Deploy static websites to ShipStatic. Use when the user wants to deploy a site, publish a website, upload to hosting, go live, set up a custom domain, manage deployments, or share a site URL. Free, no account needed. CLI (ship) and Node.js/browser SDK.
shippage
Publish HTML or Markdown to a public URL instantly. Zero config, auto-registers on first use. Use when the user wants to share, preview, host, or deploy generated HTML, Markdown, JSX, or web content as a live webpage accessible from any device including mobile phones and WeChat. Perfect for sharing AI-generated pages…
pocketnook
Deploys a repository or a working directory to a private URL, and manages what is already deployed: build logs, stopping. Use when a finished piece of work needs somewhere to run, or when a deploy has failed and the reason is in the build log. Trigger with "deploy this", "put this somewhere private", "get me a link…
deploy
Deploy an app or static site to a live URL with openpouch (agent-native hosting — no account, no CAPTCHA, one command). Use when the user asks to deploy, publish, ship, host, or wants a live/preview/shareable URL for what you built.
shippage
Publish HTML or Markdown to a public URL instantly. Zero config, auto-registers on first use. Use when the user wants to share, preview, host, or deploy generated HTML, Markdown, JSX, or web content as a live webpage accessible from any device including mobile phones and WeChat. Perfect for sharing AI-generated pages…