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 agentmods add rules/netlify/context-and-tools/netlify-deploy-netlify-tomlgit clone --depth 1 https://github.com/netlify/context-and-toolsWrote 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/rules/netlify/context-and-tools/netlify-deploy-netlify-toml)<a href="https://agentmods.dev/rules/netlify/context-and-tools/netlify-deploy-netlify-toml"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-deploy-netlify-toml.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00676 |
| Opus 5 | $0.00010 | $0.00338 |
| Sonnet 5 | $0.00004 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
netlify-deploy-netlify-toml 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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
netlify.toml — Build Configuration for Deploys
netlify.toml at the repository root controls how Netlify builds and deploys the site (in monorepos, the first config found wins — see the discovery order under "Monorepo with a Base Directory" below). This reference covers the deploy-relevant build settings. For the complete netlify.toml syntax — redirects, headers, deploy contexts, functions and edge-functions config, plugins, and the Image CDN block — see the netlify-config skill, which is the source of truth for configuration.
Build Settings
[build]
# Command to build the site
command = "npm run build"
# Directory to publish, relative to `base` when set, otherwise the repo root
publish = "dist"
# Base directory the build runs from (default: repo root)
base = "packages/frontend"
# Functions directory (default: netlify/functions)
functions = "netlify/functions"
# Skip a build when nothing relevant changed
ignore = "git diff --quiet HEAD^ HEAD package.json"
publish is resolved relative to base. With base = "packages/frontend" and publish = "dist", Netlify publishes packages/frontend/dist — not dist at the repo root. Set publish relative to the base directory or the deploy will fail with "publish directory not found."
netlify.toml overrides the Netlify UI. When a build setting is in both, the committed file wins; the UI field becomes inert until you change the file and redeploy.
Monorepo with a Base Directory
[build]
base = "packages/web"
command = "npm run build"
publish = "dist" # publishes packages/web/dist
In a monorepo, Netlify uses the first netlify.toml it finds: the package directory, then the base directory, then the repo root.
Build-Time Environment and Context Overrides
Build-scoped environment variables and per-context build overrides can live in netlify.toml:
[build.environment]
NODE_VERSION = "20"
[context.production]
command = "npm run build:prod"
[context.deploy-preview]
command = "npm run build:preview"
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.
- 5d ago First seen · 71 lines · 20 tokens per session scan A e8440d6b3725
netlify-deploy-netlify-toml is a cursor rule published in the GitHub repository netlify/context-and-tools (36 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 676 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.
Other cursor rules, from other repositories
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.