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 skills/ericrisco/rsc-harness/netlifynpx skills add ericrisco/rsc-harness --skill netlifygit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/netlify)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/netlify"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/netlify.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.1 | $0.00063 | $0.02455 |
| Opus 5 | $0.00032 | $0.01228 |
| Sonnet 5 | $0.00013 | $0.00491 |
| Haiku 4.5 | $0.00006 | $0.00246 |
Grade A, and why
netlify 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Netlify — netlify.toml, Functions, Edge Functions, redirects & the CLI
The platform-mechanics layer for Netlify: config, function handlers, routing, env contexts, and the deploy CLI. Not framework code, not generic CI.
What this owns
You own the Netlify adapter/config surface — netlify.toml, netlify/functions/,
netlify/edge-functions/, _redirects, _headers, and netlify <cmd>. You do not own
the app's routing or data layer (that is ../nextjs/SKILL.md / a React skill), DNS records
(../domains-dns/SKILL.md), or another platform's config — Vercel is ../vercel/SKILL.md,
Cloudflare is ../cloudflare/SKILL.md. Their config files and function models differ; never
cross-apply.
The 5-minute happy path
netlify link # link the cwd to a site (or `netlify init` to create one)
# write/edit netlify.toml (see skeleton below)
netlify dev # local emulation: build, functions, redirects, env injection
netlify deploy --prod # build + push straight to production
netlify deploy with no flag creates a draft deploy (preview URL, not live). --prod
publishes. Test with netlify dev first — it is the only local runtime that emulates
redirects and function routing together.
Where does each piece of config live?
Two rules decide everything below: _redirects/_headers files are processed before the
netlify.toml equivalents, and a function's own config export beats dashboard guesses.
| Concern | Put it in | Why |
|---|---|---|
| Redirects / rewrites / SPA fallback | [[redirects]] in toml or _redirects file |
One source. File rules run first; pick one and stay consistent. |
| Response headers (CSP, caching) | [[headers]] in toml or _headers file |
Same precedence; keep security headers in version control, not the UI. |
| Build command / publish dir / functions dir | [build] in toml |
Single declarative source the build picks up; survives UI drift. |
| A function's URL path | export const config = { path } in the function |
Co-located with the handler; deterministic, no dashboard mapping. |
| Edge function path + ordering | [[edge_functions]] in toml |
Declaration order in toml is deterministic (inline config is not). |
| Secrets / API keys / per-context vars | dashboard or netlify env:set |
Never commit secrets — build-time secrets scanning fails the build if it finds one. |
What ships with it
5 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.
- 3d ago First seen · 209 lines · 63 tokens per session scan A b2d0aae0d9cf
netlify is a skill published in the GitHub repository ericrisco/rsc-harness (65 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 2,455 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-09-03.
Other skills, from other repositories
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
cli-ux
Use for packages/cli changes that affect command UX, prompts, help, output layout, progress, success, warnings, errors, JSON/stdout/stderr contracts, non-interactive/agent behavior, copy, or tests for those surfaces. Do not load for implementation-only refactors with unchanged CLI surface.
x-lsof
Enhanced lsof (List Open Files) with interactive UI and structured output. View open files, network connections, and processes. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
moai-platform-deployment
Deployment and hosting platform specialist covering Vercel, Railway, and Convex. Use when deploying applications, configuring edge functions, setting up continuous deployment, or managing serverless infrastructure.
moai-ref-react-patterns
React/Next.js component design patterns, state management strategies, and project structure reference for frontend development. Agent-extending skill that amplifies frontend domain work (spawned via Agent(general-purpose) with frontend instructions) with production-grade React patterns. NOT for: backend API design…