What is sites-deployment?

A deployment guide for Next.js websites covering hosting services such as Vercel, Netlify, and Cloudflare Pages, along with release setup.

Use it to set up deployments, CI/CD, environment variables, and release processes for Next.js sites.

It helps organise the steps between finished code and a running website. It also covers configuration that can cause deployment failures when missed.

sites-deployment — Skill for Claude Code by joaoguirunas/team-os

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 joaoguirunas/team-os --skill sites-deployment

Clone the repo

git clone --depth 1 https://github.com/joaoguirunas/team-os

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/joaoguirunas/team-os/sites-deployment/github.svg)](https://agentmods.dev/skills/joaoguirunas/team-os/sites-deployment)

Your own site

<a href="https://agentmods.dev/skills/joaoguirunas/team-os/sites-deployment"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/sites-deployment/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/joaoguirunas/team-os/sites-deployment"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/sites-deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 980 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.

Model	Per session	Once invoked
Fable 5.1	$0.00035	$0.00980
Opus 5.5	$0.00014	$0.00392
Sonnet 5.5	$0.00007	$0.00196
Haiku 4.5	$0.00003	$0.00098

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

Security

Grade A, and why

sites-deployment 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.

.claude/skills/sites-deployment/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sites Deployment — Plataformas e Processo

Checklist pré-deploy

[ ] npm run build — sem erros
[ ] npm run lint — sem warnings críticos
[ ] npm run typecheck — sem erros de tipo
[ ] Variáveis de ambiente verificadas (.env.example actualizado)
[ ] Images otimizadas (next/image no Next.js; astro:assets Image/Picture no Astro)
[ ] Lighthouse score > 90 em todas as categorias

Vercel (recomendado para Next.js)

npm i -g vercel
vercel login
vercel link
vercel          # preview
vercel --prod   # produção
vercel env add NOME_VAR production

Netlify

npm i -g netlify-cli
netlify login
netlify init
netlify deploy --dir=.next --prod

Cloudflare Pages

npm i -g wrangler
wrangler pages deploy .next --project-name=nome-projeto

Astro

Diferença chave vs Next.js: build output padrão do Astro é dist/ (não .next/) quando output: 'static'; com adapter + output: 'server', cada plataforma gera seu próprio formato de função serverless/edge (não mais .next/). Sempre registrar site: no astro.config.mjs antes de configurar sitemap/canonical — sem isso as URLs absolutas quebram.

Plataforma	Adapter Astro	Build output	Comando
Vercel	`@astrojs/vercel` (ou zero-config — Vercel detecta Astro nativamente)	`.vercel/output`	`vercel --prod` (igual à trilha Next)
Netlify	`@astrojs/netlify`	`dist/` (SSG) ou função serverless (SSR)	`netlify deploy --dir=dist --prod` (SSG)
Cloudflare Pages	`@astrojs/cloudflare`	`dist/`	`wrangler pages deploy dist --project-name=nome`

# Vercel — zero-config ou com adapter explícito
npm i -g vercel
vercel login
vercel link
vercel --prod

# Netlify — output estático (SSG)
npm i -g netlify-cli
npm i @astrojs/netlify
netlify login
netlify init
netlify deploy --dir=dist --prod

# Cloudflare Pages
npm i -g wrangler
npm i @astrojs/cloudflare
wrangler pages deploy dist --project-name=nome-projeto

// astro.config.mjs
import { defineConfig } from 'astro/config'
import vercel from '@astrojs/vercel' // ou netlify / cloudflare, conforme a plataforma

export default defineConfig({
  site: 'https://exemplo.pt', // obrigatório — sitemap e canonical dependem disso
  output: 'static',           // default — tudo pré-renderizado (SSG)
  adapter: vercel(),          // só necessário quando output: 'server' ou SSR seletivo por rota
})

Read the full file on GitHub · 123 lines

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.

1mo ago Changed 65e9f017f06e
1mo ago Changed · +50 lines · -26 tokens per session 5dc49ef7c79b
2mo ago Changed · +2 lines · +28 tokens per session 9629ca49e2b1
2mo ago First seen · 71 lines · 33 tokens per session scan A 5a119adc143d

Subscribe to this mod's changes

sites-deployment is a skill published in the GitHub repository joaoguirunas/team-os (6 stars, last pushed 10d ago), licensed MIT. It adds 35 tokens to every session and 980 once invoked, about $0.0001 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-03.

CI and CD Claude Code Cloud DevOps and cloud agent-teams ai-agents anthropic claude claude-skills

sites-deployment next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sites-deploymentjoaoguirunas/team-os	Skill	6	10d ago	MIT	A	35	Claude Code
runbook-generatorOneWave-AI/claude-skills	Skill	428	24d ago	MIT	A	58	Claude Code, Codex
devops-best-practicesronalships/claude-devops-skill	Skill	2	5mo ago	MIT	B	209	Claude Code, Codex
monitoring-and-alertingrampstackco/claude-skills	Skill	1.1k	4d ago	MIT	A	99	Claude Code
launch-runbookrampstackco/claude-skills	Skill	1.1k	4d ago	MIT	A	127	Claude Code
devops-cloudtravisjneuman/.claude	Skill	111	3d ago	MIT	A	38	Claude Code
agents-v2-pylingxling/awesome-skills-cn	Skill	331	1mo ago	MIT	A	39	Claude Code