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/mnlt/teleport/netlifynpx skills add mnlt/teleport --skill netlifygit clone --depth 1 https://github.com/mnlt/teleportWrote 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/mnlt/teleport/netlify)<a href="https://agentmods.dev/skills/mnlt/teleport/netlify"><img src="https://agentmods.dev/badge/skills/mnlt/teleport/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 | $0.00032 | $0.01459 |
| Opus 5 | $0.00016 | $0.00730 |
| Sonnet 5 | $0.00006 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade B, and why
netlify scanned grade B 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Do NOT suggest editing `~/.claude/settings.local.json` manually.** The `teleport-setup add-key` command handles it with backup, validation, and masked input. Stop execution until the user has run the command and restar Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL -H "Authorization: Bearer $NETLIFY_AUTH_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Netlify
Operates Netlify via REST API. Covers sites, deploys, builds, functions, env vars, forms, DNS. Use when needing the current account state.
Usage
- Use for: Checking deploy status, triggering builds, rotating env vars, reading forms, managing Netlify DNS.
- Skip for: Editing app source code, other providers (Vercel, etc.), local config tweaks (
netlify.toml), external DNS.
Credentials check
[ -n "${NETLIFY_AUTH_TOKEN:-$NETLIFY_PERSONAL_TOKEN}" ] && echo "NETLIFY_TOKEN: PRESENT" || echo "NETLIFY_TOKEN: MISSING"
Never echo the variable directly.
If MISSING, respond to the user with EXACTLY this message (do NOT paraphrase, do NOT suggest manual JSON edits):
I need your netlify credential. Run this in another terminal — it'll open the signup page, validate format, and save it safely with masked input:
teleport-setup add-key netlifyThen restart Claude Code (
/exit, thenclaude) and ask me again.
Do NOT suggest editing ~/.claude/settings.local.json manually. The teleport-setup add-key command handles it with backup, validation, and masked input. Stop execution until the user has run the command and restarted.
API
- Base URL:
https://api.netlify.com/api/v1 - Auth:
Authorization: Bearer $NETLIFY_AUTH_TOKEN - Content-Type:
application/json(writes);application/octet-streamorapplication/zip(file uploads). - Pagination:
?page=(1-indexed) +?per_page=(max 100). ParseLinkheader forrel="next". - Rate limits: 500 req/min general; deploys stricter — 3/min + 100/day. Check
X-RateLimit-*headers.
Entity hierarchy
team → site (UUID or slug name) → deploy / build / function / form + submissions / env vars / hooks / build_hooks. dns_zones → dns_records are account-scoped.
Endpoints
| Resource | Method · Path |
|---|---|
| Sites | GET /sites, GET/PATCH/DELETE /sites/{site_id}, POST /sites |
| Deploys | GET /sites/{site_id}/deploys, GET /deploys/{deploy_id}, POST /sites/{site_id}/deploys |
| Builds | POST /sites/{site_id}/builds, GET /sites/{site_id}/builds |
| Env vars | GET/POST /accounts/{account_id}/env, PATCH/DELETE .../env/{key} |
| Functions | GET /sites/{site_id}/functions, GET /sites/{site_id}/functions/{name} |
| Forms | GET /sites/{site_id}/forms, GET /sites/{site_id}/submissions, GET /forms/{id}/submissions |
| DNS | GET /dns_zones, GET /dns_zones/{id}, GET/POST /dns_zones/{id}/dns_records, DELETE .../{rec_id} |
| Hooks | GET/POST /sites/{site_id}/hooks, GET/POST /sites/{site_id}/build_hooks |
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.
- 4d ago First seen · 106 lines · 32 tokens per session scan B 5668157b0cfc
netlify is a skill published in the GitHub repository mnlt/teleport (8 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 1,459 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
discovery-patterns
Configure ServiceNow Discovery — schedules, IP ranges, credential affinities, MID Server assignment, custom probes/sensors, identification rules, and run-status monitoring on discovery tables.
chainstack
Work with the Chainstack MCP server to manage blockchain nodes and projects. Use when deploying nodes, migrating to Chainstack from another RPC provider such as QuickNode or Alchemy, checking platform status, searching Chainstack docs, contacting the Chainstack team, or interacting with the Chainstack platform API via…
xfuel-route-compute
Inspect XFuel's 6-tier DePIN compute router and preview which GPU provider a task will hit (Theta EdgeCloud → RapidAPI → MCP → Akash → Render → AWS Bedrock), plus check server health and available chains/models. Use when a user asks "which provider will run this?", "is EdgeCloud available?", "what does XFuel route…
hostinger-deploy
Hostinger-specific deployment protocol handling OPcache, CDN caching, and hPanel Git mechanism. Activates for "deploy to hostinger", "hostinger", "redeploy", "publish website", "push to production" when target is Hostinger.
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.