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 instructions/netlify/context-and-tools/claude-mdgit 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/instructions/netlify/context-and-tools/claude-md)<a href="https://agentmods.dev/instructions/netlify/context-and-tools/claude-md"><img src="https://agentmods.dev/badge/instructions/netlify/context-and-tools/claude-md.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.00667 | $0.00667 |
| Opus 5 | $0.00333 | $0.00333 |
| Sonnet 5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
context-and-tools CLAUDE.md 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 3d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Netlify Context and Tools
This repository contains public Netlify skills — factual platform reference for AI agents working with Netlify projects.
Repository Structure
context/— Steering guides (e.g., POWER.md for Kiro deployments).claude-plugin/— Plugin marketplace config for Claude Code installation (VS Code agent plugins share this format and auto-detect.claude-plugin/plugin.json; no VS-Code-specific mirror is generated).grok-plugin/— Plugin manifest for Grok Build (same plugin format as Claude Code; hand-authored, not generated).mcp.json— Netlify MCP server config bundled with the Claude Code and Grok Build plugins (hosted HTTP endpoint; OAuth at runtime)skills/— Netlify platform skills (source of truth for all agent formats)agent-plugin/— Agent Plugins spec-compliant package (plugin.json+mcp.json+skills/). Root manifests are hand-authored;agent-plugin/skills/is auto-generated (do NOT edit directly)cursor/rules/— Auto-generated Cursor.mdcrule files (do NOT edit directly)codex/— Auto-generated Codex skills andAGENTS.mdrouter (do NOT edit directly)scripts/build-cursor-rules.sh— Convertsskills/→cursor/rules/scripts/build-codex-skills.sh— Copiesskills/→codex/and generatesAGENTS.mdscripts/build-agent-plugin.sh— Mirrorsskills/→agent-plugin/skills/.github/workflows/build-generated-outputs.yml— Rebuildscursor/,codex/, andagent-plugin/skills/fromskills/and commits them in a single step (on push to main and on PRs), so the generated mirrors always stay in parity withskills/
Skills
The skills/ directory contains skills covering Netlify platform primitives. See skills/CLAUDE.md for a guide on when to use each skill.
Cursor Rules
The cursor/rules/ directory is auto-generated from skills/ and must never be edited directly. A GitHub Actions workflow rebuilds these files whenever skills/ changes — committing them on same-repo PRs and on push to main (fork PRs are verified, not auto-committed). To rebuild locally:
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.
- 3d ago First seen · 39 lines · 667 tokens per session scan A d6a0017dea78
context-and-tools CLAUDE.md is an instructions file published in the GitHub repository netlify/context-and-tools (36 stars, last pushed 7d ago), licensed MIT. It adds 667 tokens to every session, about $0.0033 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.