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 vercel-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/vercel-deployment)<a href="https://agentmods.dev/skills/monkilabs/opencastle/vercel-deployment"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/vercel-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/vercel-deployment"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/vercel-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.00766 |
| Opus 5.5 | $0.00019 | $0.00306 |
| Sonnet 5.5 | $0.00009 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
vercel-deployment 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 23d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vercel Deployment
Vercel-specific deployment patterns and MCP tool usage. For project-specific deployment architecture, environment variables, and key files, see .opencastle/stack/deployment-config.md.
Deployment Model
Branch → Environment mapping:
| Branch pattern | Environment |
|---|---|
main |
Production deployment (auto) |
Any other branch (feat/*, fix/*, …) |
Preview deployment (auto) |
MCP Tools
The Vercel MCP server provides these tools through https://mcp.vercel.com:
| Tool | Purpose |
|---|---|
deploy_to_vercel |
Trigger a deployment |
get_deployment |
Check deployment status and metadata |
get_deployment_build_logs |
Read build output for debugging |
get_runtime_logs |
Read runtime logs for debugging |
list_deployments |
List recent deployments |
get_project |
Get project configuration |
list_projects |
List all projects in the team |
list_teams |
List available teams |
search_vercel_documentation |
Search Vercel docs |
check_domain_availability_and_price |
Domain availability check |
Environment Variables
Vercel Environment Scoping
Vercel supports three environment scopes — set variables for each appropriately:
| Scope | When Applied | Use For |
|---|---|---|
| Production | main branch deploys |
Live secrets, production API keys |
| Preview | All non-production branches | Staging/test API keys |
| Development | vercel dev local server |
Local development overrides |
Best Practices
Verify required env vars exist in production and preview scopes.
Build Troubleshooting
When builds fail, follow this workflow:
- Read build logs — use
get_deployment_build_logsto get the full output - Check common causes:
- Missing environment variables
- Node.js version mismatch (check
enginesinpackage.json) - Build command mismatch (verify in project settings)
- Dependency resolution issues (lockfile out of sync)
- Check runtime logs — use
get_runtime_logsfor post-deploy errors - Verify deployment status — use
get_deploymentto check state and error details
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.
- 23d ago Changed · +10 tokens per session 2970fa26242c
- 24d ago First seen · 93 lines · 37 tokens per session scan A 1b689023ebb3
vercel-deployment is a skill published in the GitHub repository monkilabs/opencastle (80 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 766 once invoked, about $0.0002 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-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-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
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.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
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.