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 littleben/awesomeAgentskills --skill deploying-to-productiongit clone --depth 1 https://github.com/littleben/awesomeAgentskillsWrote 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/littleben/awesomeagentskills/deploying-to-production)<a href="https://agentmods.dev/skills/littleben/awesomeagentskills/deploying-to-production"><img src="https://agentmods.dev/badge/skills/littleben/awesomeagentskills/deploying-to-production/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/littleben/awesomeagentskills/deploying-to-production"><img src="https://agentmods.dev/badge/skills/littleben/awesomeagentskills/deploying-to-production.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.00055 | $0.00981 |
| Opus 5 | $0.00028 | $0.00491 |
| Sonnet 5 | $0.00011 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
Deploying to Production 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 12d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploying to Production
Automated deployment workflow for Next.js websites using GitHub and Vercel.
When to use this Skill
- Creating a new website and need to deploy it
- Setting up GitHub repository for version control
- Deploying to Vercel production environment
- User mentions: "deploy", "GitHub", "Vercel", "go live", "publish"
Deployment Workflow
Copy this checklist and track your progress:
Deployment Progress:
- [ ] Step 1: Pre-deployment validation (build + E-E-A-T check)
- [ ] Step 2: Create GitHub repository
- [ ] Step 3: Push code to GitHub
- [ ] Step 4: Deploy to Vercel
- [ ] Step 5: Post-deployment verification
Step 1: Pre-deployment validation
Run build and verify no errors:
cd "$PROJECT_DIR"
npm run build
CRITICAL: Only proceed if build succeeds with no errors.
Pre-deployment checklist - See CHECKLIST.md for complete list:
-
npm run buildcompletes successfully - All environment variables configured
- E-E-A-T elements present (About page, author info)
- Core Web Vitals acceptable
- SEO meta tags complete
Step 2: Create GitHub repository
Run the script to create a private GitHub repository:
bash scripts/create-github-repo.sh <project-name>
What this script does:
- Creates a private GitHub repository
- Initializes Git (if needed)
- Commits all changes
- Pushes to GitHub
If the script fails, see TROUBLESHOOTING.md.
Step 3: Verify GitHub push
Check the repository URL:
gh repo view --web
Verify all files are pushed correctly.
Step 4: Deploy to Vercel
Run the deployment script:
bash scripts/deploy-to-vercel.sh <project-name>
What this script does:
- Links the project to Vercel
- Deploys to production environment
- Returns deployment URL
If deployment fails, see TROUBLESHOOTING.md.
Step 5: Post-deployment verification
Verify deployment:
- Visit the deployment URL
- Test core functionality:
- Homepage loads correctly
- Navigation works
- Core features functional
- Check Core Web Vitals (use PageSpeed Insights)
- Verify SEO meta tags (use browser inspector)
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.
- 12d ago First seen · 144 lines · 55 tokens per session scan A 64928bc77f7c
Deploying to Production is a skill published in the GitHub repository littleben/awesomeAgentskills (187 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 981 once invoked, about $0.0003 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
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
nextjs-deployment
Provides comprehensive patterns for deploying Next.js applications to production. Use when configuring Docker containers, setting up GitHub Actions CI/CD pipelines, managing environment variables, implementing preview deployments, or setting up monitoring and logging for Next.js applications. Covers standalone output…
nx-monorepo
Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects. Use when creating Nx workspaces, generating apps/libraries/components, running affected commands, setting up CI/CD, configuring Module Federation, or implementing NestJS backends within Nx.
turborepo-monorepo
Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance…
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
loom-ci-cd
Designs and implements CI/CD pipelines for automated testing, builds, deployment, and security scanning.