netlify-deploy-cli-commands

A quick reference for using the Netlify command-line tool to manage sites and deployments. Netlify is a service that builds and hosts websites.

In plain words
What is it for?
Use it to log in, connect a project to a Netlify site, create sites, preview changes, deploy to production, and open site dashboards.
Why use it?
It avoids searching through documentation for the right command or deployment option. It also explains how to authenticate in automated build systems.

Cursor rule

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.

agentmods
npx agentmods add rules/netlify/context-and-tools/netlify-deploy-cli-commands
Clone the repo
git clone --depth 1 https://github.com/netlify/context-and-tools
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 885 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00015 $0.00885
Opus 5 $0.00008 $0.00443
Sonnet 5 $0.00003 $0.00177
Haiku 4.5 $0.00002 $0.00089

Measured 2d ago against content hash 8e9922e1a3fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

netlify-deploy-cli-commands 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 2d 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.

cursor/rules/netlify-deploy-cli-commands.mdc · 147 lines

How it starts

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

Netlify CLI Commands Reference

Quick reference for common Netlify CLI commands used in deployments. Commands can be run from a global install (netlify <command>) or without installing (npx netlify <command>).

Authentication

# Login via browser OAuth
netlify login

# Logout
netlify logout

For CI, set NETLIFY_AUTH_TOKEN (and NETLIFY_SITE_ID to select the target site) instead of logging in interactively. Don't pre-check auth — run the real command and only surface netlify login if it fails with an auth error.

Site Management

# Link current directory to an existing site (interactive)
netlify link

# Link by Git remote URL
netlify link --git-remote-url <url>

# Create and link a new site
netlify init           # With Git CI/CD setup
netlify init --manual  # Without Git CI/CD

# Unlink from the current site
netlify unlink

# List sites for the account
netlify sites:list

# Open the site in the Netlify dashboard
netlify open
netlify open:admin     # Admin panel
netlify open:site      # Live site in the browser

Deployment

# Draft deploy (preview URL) — safe for testing
netlify deploy

# Deploy to production
netlify deploy --prod

# Deploy a specific directory
netlify deploy --dir=dist

# Add a deploy message
netlify deploy --message="Deploy message"

# List past deploys
netlify deploy:list

The primary deploy path is Git-based continuous deployment (push to deploy). Use netlify deploy for manual/local uploads — prototypes, sites with no Git remote, or CI pipelines that upload a prebuilt artifact.

Build

# Show build settings without building
netlify build --dry

# Run the build locally (mimics the Netlify build environment)
netlify build

Functions (Serverless)

# List functions
netlify functions:list

# Invoke a function locally
netlify functions:invoke FUNCTION_NAME

# Scaffold a new function
netlify functions:create FUNCTION_NAME

Logs

# View recent logs from functions and edge functions (defaults to last 10m)
netlify logs

# Stream logs in real time
netlify logs --follow

# Stream logs for a specific function
netlify logs --source functions --function FUNCTION_NAME --follow

# View historical logs for a specific function over a longer window
netlify logs --source functions --function FUNCTION_NAME --since 24h

# Include deploy logs alongside function logs
netlify logs --source deploy --source functions --since 1h

Read the full file on GitHub · 147 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.

  1. 2d ago First seen · 147 lines · 15 tokens per session scan A 8e9922e1a3fb

Subscribe to this mod's changes

netlify-deploy-cli-commands is a cursor rule published in the GitHub repository netlify/context-and-tools (36 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 885 once invoked, about $0.0001 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.