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/monkilabs/opencastle/netlifynpx skills add monkilabs/opencastle --skill netlifygit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/netlify)<a href="https://agentmods.dev/skills/monkilabs/opencastle/netlify"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/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.00061 | $0.00559 |
| Opus 5 | $0.00030 | $0.00280 |
| Sonnet 5 | $0.00012 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
netlify-deployment scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsS -o /dev/null -w '%{http_code}' https://<DEPLOY_URL>/ What it actually says
Netlify Deployment
Project deployment architecture, env vars, and key files: deployment-config.md. Docs: https://docs.netlify.com
main → production (auto). feature/*, fix/* → deploy preview at a unique URL (auto).
Hard limits
- Serverless functions (
netlify/functions/): default timeout 10s, extendable to 26s on Pro. Anything longer must be a background function — up to 15 min. - Edge functions (
netlify/edge-functions/) run on Deno, not Node — no Node built-ins, no npm-only packages. Use for personalization, A/B tests, geo-routing (context.geo). - Functions use web-standard
Request/Response. TypeScript works with no build step.
Gotchas
- Exporting
config = { path: '/geo' }from a function replaces the default/.netlify/functions/<name>route. Without it, the default path is the only one that works. - Cron is a function-level
config: Config = { schedule: "0 0 * * *" }— the schedule is UTC, and the request body carriesnext_run. - Env vars are scoped and do not cascade: Production (
maindeploys), Deploy previews (all PR/branch builds), Branch deploy (one named branch), Local (netlify dev). A var set only on Production is undefined in previews. - Most build failures are
NODE_VERSION(set it under[build.environment]innetlify.toml), a stale lockfile, or apublishdir that does not match the actual build output.
Commands
netlify build --debug # reproduce the CI build locally, verbose — do this before pushing
netlify env:list # confirm vars exist in the scope you expect
netlify status # linked site + deploy state
Post-deploy, verify each critical route returns 200:
curl -fsS -o /dev/null -w '%{http_code}' https://<DEPLOY_URL>/
Any non-200 → read the deploy log in the Netlify UI, fix, redeploy.
What ships with it
1 file 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.
- 4d ago First seen · 40 lines · 61 tokens per session scan A c393ae76a0b6
netlify-deployment is a skill published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 6d ago), licensed MIT. It adds 61 tokens to every session and 559 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
product-architect
Complete product development system with 80 agents and 36 frameworks. Use when the user wants to build a product, write a PRD, plan an MVP or roadmap, design an app, research a market or check whether a feature already exists or is novel, do competitive analysis, run a security audit, build a financial model, plan…
codex-delegation
Use when a coding task would benefit from delegating work to Codex in the background — a deep independent second opinion, security or architecture analysis, or a parallel implementation running while the session continues. Lets Claude drive the codex companion itself (task, review, status --wait, result) without the…
cursor-delegation
Use when a coding task would benefit from delegating work to Cursor in the background — fast parallel implementation, scaffolding, or an everyday review running while the session continues. Lets Claude drive the cursor companion itself (task, review, status --wait, result) without the user typing /cursor: commands.
cursor-cli-runtime
Internal helper contract for calling the cursor-companion runtime from Claude Code.
cursor-prompting
Internal guidance for composing cursor-agent prompts and picking models for coding, review, diagnosis, and research tasks inside the Cursor Claude Code plugin.
goal-runner
Use when the user asks to advance, continue, or work on the project's long-horizon goal (or to set one up) — the policy for goal-driven increments driven through the goal companion, one increment at a time, delegated via the codex/cursor delegation skills, honestly recorded.