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 monkilabs/opencastle --skill netlify-deploymentgit 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-deployment)<a href="https://agentmods.dev/skills/monkilabs/opencastle/netlify-deployment"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/netlify-deployment/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/monkilabs/opencastle/netlify-deployment"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/netlify-deployment.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.00543 |
| Opus 5.5 | $0.00019 | $0.00217 |
| Sonnet 5.5 | $0.00009 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00054 |
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 11d 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: .opencastle/stack/deployment-config.md. Docs: https://docs.netlify.com
main → production (auto). Every other branch (feat/*, 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 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.
- 11d ago Changed · -14 tokens per session 96fbbb98ff3e
- 12d ago First seen · 40 lines · 61 tokens per session scan A 77e5406714a7
netlify-deployment is a skill published in the GitHub repository monkilabs/opencastle (80 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 543 once invoked, about $0.0002 per session on Opus 5.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-10-04.
Other skills, from other repositories
aws-iac-change-safety-review
Review AWS infrastructure-as-code changes across CDK, CloudFormation, SAM, Terraform, Serverless Framework, generated templates, plans, stack updates, change sets, and drift. Use when the user asks whether an AWS IaC deployment is safe, what a change set will do, why a resource replacement will happen, or how to…
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
telnyx-storage-curl
Manage cloud storage buckets and objects using the S3-compatible Telnyx Storage API. This skill provides REST API (curl) examples.
cicd-secrets-exfil
Extracting CI secrets / OIDC tokens once you have code execution in a build job — echo/printenv exfil, log-masking bypass (base64, char-split, reversal), OIDC token abuse to assume cloud roles, GITHUBTOKEN / CIJOBTOKEN scope abuse, cache / artifact secret leakage, provenance pivot.
relay-deploy
Set up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".