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 batterfried-philosophy172/Agent-Startup-Skills --skill deploy-plannergit clone --depth 1 https://github.com/batterfried-philosophy172/Agent-Startup-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/batterfried-philosophy172/agent-startup-skills/deploy-planner)<a href="https://agentmods.dev/skills/batterfried-philosophy172/agent-startup-skills/deploy-planner"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/deploy-planner/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/batterfried-philosophy172/agent-startup-skills/deploy-planner"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/deploy-planner.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.00052 | $0.00683 |
| Opus 5.5 | $0.00021 | $0.00273 |
| Sonnet 5.5 | $0.00010 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
deploy-planner 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.
This is a copy
100% identical to deploy-planner — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Planner — Launch Preparation Agent
Purpose
Prepare the complete deployment package so the user can go from "code on my machine" to "live on the internet" with clear, step-by-step instructions.
When to Use
- After security audit is complete and approved
- When the user asks "how do I deploy this?"
- As the final phase of the SaaS Accelerator pipeline
Process
Step 1: Deployment Target Selection
Recommend a free-tier hosting platform based on the tech stack:
| Tech Stack | Recommended Host | Free Tier Limits |
|---|---|---|
| Next.js | Vercel | 100GB bandwidth/month |
| Node.js/Express | Render | 750 hours/month |
| Python/Django | Railway | $5 free credit/month |
| Static + API | Netlify + Supabase | 100GB + 500MB DB |
Step 2: Docker Configuration
Generate a production Dockerfile:
- Multi-stage build (build stage + production stage)
- Non-root user
- Health check endpoint
- Minimal image size
Generate a docker-compose.yml for local development:
- App service
- Database service
- Volume mounts for persistence
- Environment variable passthrough
Step 3: Environment Setup Guide
Create a .env.production.example with:
- Every required variable
- Description of what each variable does
- Where to obtain each value (e.g., "Get from Supabase dashboard")
Step 4: Deployment Guide
Write a step-by-step guide:
## Deploy to [Platform]
### Prerequisites
- [ ] Account on [platform]
- [ ] Git repository pushed to GitHub
### Steps
1. Go to [platform dashboard URL]
2. Click "New Project" → "Import from GitHub"
3. Select your repository
4. Set environment variables: [list each one]
5. Click "Deploy"
6. Wait for build to complete (~2-3 minutes)
7. Visit your live URL: https://your-app.vercel.app
### Post-Deployment Verification
- [ ] Homepage loads correctly
- [ ] User registration works
- [ ] Login/logout works
- [ ] Core feature works end-to-end
- [ ] No console errors in browser DevTools
Step 5: Project README
Generate the final README.md for the project repository:
- Project name and one-line description
- Tech stack badges
- Features list
- Local development setup (step-by-step)
- Deployment instructions
- Environment variables reference
- Contributing guidelines
- License
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.
- 1mo ago First seen · 104 lines · 52 tokens per session scan A 77055040eb60
deploy-planner is a skill published in the GitHub repository batterfried-philosophy172/Agent-Startup-Skills (2 stars, last pushed 15d ago), licensed MIT. It adds 52 tokens to every session and 683 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to deploy-planner, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
dockerized-service-release-deployment-workflow
Create a Dockerized-service release contract with clean GitHub Actions builds, main-anchored tags, immutable digest manifests, published-release deployments, production approval, health checks, and exact-digest rollback.
vibe-ship
Generates and audits production-ready deployment setups for any app. Detects the stack from the repo (Node/Next.js/Bun/Deno, Python/Django/FastAPI, Go, Rust, Java/Spring, .NET, Ruby/Rails, PHP/Laravel, Elixir/Phoenix, static sites, monorepos) and writes hardened Dockerfiles, .dockerignore, compose.yaml with…
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.
import
Import a self-contained NeatContext context bundle shared by another person, or reconcile a newer copy of a context already on this machine, leaving the source bundle unchanged. Use only when the user explicitly invokes this skill or asks to import a NeatContext bundle.