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 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/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.
<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/netlify"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/netlify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 171 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 150 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.5 | $0.00025 | $0.00982 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 209 lines · 63 tokens per session scan A b2d0aae0d9cf
netlify is a skill published in the GitHub repository ericrisco/rsc-harness (232 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.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
huawei-cloud-deployment-task-management
Huawei Cloud CloudDeploy (CodeArts Deploy / 部署) management, execution, and failure analysis using the KooCLI hcloud command-line client. Covers deploy application listing and creation, deployment task listing/detail/creation, task start, task deletion, deployment failure root-cause analysis (agent offline, timeout…
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
04-security
A security and operations guide for deploying Dify, an open-source platform for building AI applications, in production.
huawei-cloud-apig-instance-management
Manage Huawei Cloud APIG (API Gateway, dedicated instances) via hcloud CLI: instance lifecycle (create/list/delete), API groups, API create/update/delete, publish/offline, request throttling policies, signature keys, access control (ACL) policies, and public ingress EIP binding, plus read-only diagnosis of public…
huawei-cloud-waf-aad-rule-management
A command-line skill for managing and diagnosing Huawei Cloud WAF and AAD protection. WAF is a web application firewall; AAD is protection against distributed denial-of-service attacks.
huawei-ecs
Use when creating, configuring, managing, or troubleshooting ECS instances on Huawei Cloud. Covers instance creation (hcloud ECS CreateServers), flavor selection, image management, security groups, EIP binding, disk attachment, auto-scaling (AS), and troubleshooting. Triggers on: ECS, instance, flavor, image, security…