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/practicalswan/agent-skills/netlify-access-controlnpx skills add PracticalSwan/agent-skills --skill netlify-access-controlgit clone --depth 1 https://github.com/PracticalSwan/agent-skillsWrote 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/practicalswan/agent-skills/netlify-access-control)<a href="https://agentmods.dev/skills/practicalswan/agent-skills/netlify-access-control"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/netlify-access-control.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.00142 | $0.03298 |
| Opus 5 | $0.00071 | $0.01649 |
| Sonnet 5 | $0.00028 | $0.00660 |
| Haiku 4.5 | $0.00014 | $0.00330 |
Grade C, and why
netlify-access-control scanned grade C with 2 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- system: agent-context/access-control/system.md — human-owned, merged by ctx-gen; edit system.md, not this section --> Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
These settings have **no public API, no CLI command, and no MCP tool**. Do NOT curl `api.netlify.com` or read local auth tokens to inspect or change them. Hand the user the dashboard path and checklist. On failure, repor This is a copy
94% identical to netlify-access-control — 55 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Netlify access control (picking the protection layer)
This skill ROUTES. Its job is choosing the correct protection layer for loading a site, not implementing app auth. Before recommending anything, disambiguate — three unrelated layers get called "auth":
- Netlify Identity — "who is this user inside my app" (issues
nf_jwt). App login, OAuth providers for your users, auth code. → Route to the netlify-identity skill. Not covered here. - Password Protection / Project visibility — "can this request load the site at all." Platform perimeter. This skill.
- Team/Org SAML SSO — "can you log into the Netlify dashboard." Team member access to Netlify itself.
Sessions are separate. The same provider (e.g. Google) can be an Identity OAuth provider for app users AND a SAML IdP for team members — unrelated wiring.
Footgun: no API, CLI, or MCP for these settings
These settings have no public API, no CLI command, and no MCP tool. Do NOT curl api.netlify.com or read local auth tokens to inspect or change them. Hand the user the dashboard path and checklist. On failure, report what you tried and stop.
Footgun: the double login is real
A Password-Protection / team-login perimeter session and a Netlify Identity app session have no bridge — no shared cookie, no header forwarding, no JWT exchange. Don't burn iterations trying to wire them together. For the combined Password-Protection + Identity pattern and its tradeoffs, see references/two-layer-pattern.md.
For company-wide app-level SSO with a single sign-in (no double login), recommend the Auth0 extension (federating to the corporate IdP) BEFORE the two-layer stack.
Pick the layer
| Goal | Use |
|---|---|
| Restrict site to your team, invite by email | Private project (Credit-based) or team login protection |
| Shared password anyone can use | Basic password protection, or Password visibility (Pro only) |
| Protect only previews, keep production open | "Non-production deploys only" / "Previews only" |
| Require SSO to view the site | Org/Team SSO with Only SSO allowed (strict) + team login protection |
| Log in users inside your app | → netlify-identity skill |
| Single company-wide app SSO, no double login | → Auth0 extension |
What ships with it
3 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.
- 2d ago First seen · 217 lines · 142 tokens per session scan C 8d4f7356240c
netlify-access-control is a skill published in the GitHub repository PracticalSwan/agent-skills (13 stars, last pushed 5d ago), licensed MIT. It adds 142 tokens to every session and 3,298 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it C with 2 findings (hidden instructions, makes network calls). It is 94% identical to netlify-access-control, differing in 55 lines, and is treated as a copy.
Other skills, from other repositories
netlify
Use when deploying or operating a site on Netlify — writing or fixing netlify.toml, authoring Functions or Edge Functions, redirects, rewrites and headers, env vars per deploy context, and shipping via the Netlify CLI. NOT deploying to Vercel (that is vercel).
analyzing-cloud-storage-access-patterns
Use when detect abnormal access patterns in AWS S3, GCS, and Azure Blob Storage by analyzing CloudTrail Data Events, GCS audit logs, and Azure Storage Analytics. Identifies after-hours bulk downloads, access from new IP addresses, unusual API calls (GetObject spikes), and potential data exfiltration using statistical…
aws-api-mcp
Comprehensive AWS API support with command validation and access to all services.
awslabs-ccapi-mcp
Direct resource management with security scanning.
com.googleapis.container-mcp-mcp
Provides read access to your GKE and Kubernetes resources.
static-blog-deploy
Skill "static-blog-deploy" from Morningstar202604/awesome-skillkit, covering static blog deploy, 支持平台, 安全设计, 使用示例 and hexo 部署.