deploy-plan

deploy-plan is a skill for Claude Code, Codex from jsuncar/deployplan. It costs 62 tokens per session (537 once invoked), scanned A, original, MIT.

A skill for deploying an app through deployplan, which is an open-source deployment tool. It covers putting an app online, starting required services, monitoring it, and keeping it available.

In plain words
What is it for?
Use it when someone says to deploy, host, launch, keep an app running, add an existing domain, or investigate an app that is down.
Why use it?
It provides one guided deployment path without making the app owner choose hosting vendors, sign up for services, or manage provider billing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when someone says to deploy, host, launch, keep an app running, add an existing domain, or investigate an app that is down.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jsuncar/deployplan/deploy-plan
Install

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.

Any agent
npx skills add jsuncar/deployplan --skill deploy-plan
Clone the repo
git clone --depth 1 https://github.com/jsuncar/deployplan

Made for: Claude Code, Codex.

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.

agentmods badge for deploy-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/jsuncar/deployplan/deploy-plan/github.svg)](https://agentmods.dev/skills/jsuncar/deployplan/deploy-plan)
Your own site
<a href="https://agentmods.dev/skills/jsuncar/deployplan/deploy-plan"><img src="https://agentmods.dev/badge/skills/jsuncar/deployplan/deploy-plan/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.

agentmods 80×15 button for deploy-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/jsuncar/deployplan/deploy-plan"><img src="https://agentmods.dev/badge/skills/jsuncar/deployplan/deploy-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 537 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00537
Opus 5.5 $0.00025 $0.00215
Sonnet 5.5 $0.00012 $0.00107
Haiku 4.5 $0.00006 $0.00054

Measured 1mo ago against content hash fd8e239448fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deploy-plan 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.

skills/deploy-plan/SKILL.md · 44 lines

What it actually says

Deploy on deployplan

The human does not pick a host and does not pay. They answer scale questions. You talk to the deployplan MCP. Failures come back as logs and events. Never ask them to paste a provider email.

Hard rules

  • Do not recommend signing up for Vercel, Supabase, Railway, Neon, AWS, or Lovable on the default path.
  • Do not ask them to paste API keys from another dashboard.
  • Do not ask them to check email, click a magic link, or forward a vendor error.
  • Do not ask them to pay, enter a card, or pick a paid plan.
  • Ask only the questions interview_questions returns. Those are preferences (who uses it, sleep vs always-on, login/files/jobs, domain). They are not vendor menus.
  • Present one topology. Then apply.

Loop

  1. inspect_repo on the project root.
  2. interview_questions with answers so far. Ask the pending ones in English.
  3. list_required_services then propose_plan when required questions are done. Show always-on, workload, optional, and Docker-live. quote is an estimate only.
  4. apply_plan. That starts Docker services the app can use (Postgres, Redis, files, queue, mail). A static index.html is served. Other apps need a Dockerfile in the repo to run the process.
  5. Give them the URL and the connection strings (DATABASE_URL on localhost). If they have a domain, attach_domain is the only other human step.
  6. On failure or “it’s down”: logs and events, patch the repo, apply again. rollback if the last release is bad.

What you may ask

  • Who will use it
  • Can it sleep
  • Login, email, uploads, jobs
  • Custom domain now or later
  • How bad is downtime
  • Region only if the tool asks

What you may not ask

  • For a card, a plan, or a payment
  • Vercel or Railway or Fly
  • Supabase or Neon
  • “Which provider do you prefer?”
  • “Can you paste the email they sent you?”
Changes

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.

  1. 1mo ago First seen · 44 lines · 62 tokens per session scan A fd8e239448fd

Subscribe to this mod's changes

deploy-plan is a skill published in the GitHub repository jsuncar/deployplan (0 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 537 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-08-31.

Related

Other skills, from other repositories

lastlight-server

Install and configure a Last Light SERVER — the GitHub maintenance agent plus its docker-compose stack — on a host. Use when the user wants to "set up / install / deploy / stand up a Last Light server or instance", configure its GitHub App, models, managed repos, or domain, or get the agent running for the first time.…

nearform/lastlight · 109 tokens

cloudflare-deploy

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.

Haohao-end/openagent · 43 tokens

all-deploy

Deploys websites, web apps, APIs, and agents to the internet with a strict pre-deploy audit and a preview → health-check → prod flow. Handles plain HTML/CSS/JS pages and static sites (Astro, Hugo, Jekyll, Eleventy, Vite) as well as Next, Remix, Nuxt, SvelteKit, FastAPI, Flask, Express, MCP servers, Claude Agent SDK…

Hainrixz/all-deploy · 242 tokens

vercel-deploy

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Haohao-end/openagent · 47 tokens

publish-website

Puts a web page on the internet for free, with no terminal and no paid plan — a folder of HTML/CSS/JS, or a page Claude just built. Checks the page for the things that silently break it once it's live (wrong filename, broken image paths, capitalisation that works on your computer and 404s on the host, API keys left in…

Hainrixz/all-deploy · 216 tokens

cf

USE WHEN: running, finding, or troubleshooting Cloudflare CLI (cf) commands in this repo - dev servers, builds and their Build Output, Env types, startup profiling, production profiles, Workers Issues, and telemetry, local KV/D1/R2 data, the commands that still need Wrangler, or the cf equivalent of a Wrangler habit.…

louisbrulenaudet/monorepo-template · 81 tokens