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/vercelnpx skills add monkilabs/opencastle --skill vercelgit 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)<a href="https://agentmods.dev/skills/monkilabs/opencastle/vercel"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/vercel.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.00037 | $0.00757 |
| Opus 5 | $0.00018 | $0.00378 |
| Sonnet 5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
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 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.
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 deployment-config.md.
Deployment Model
Branch → Environment mapping:
| Branch pattern | Environment |
|---|---|
main |
Production deployment (auto) |
feature/*, 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 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 · 93 lines · 37 tokens per session scan A c4302f548779
vercel-deployment is a skill published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 757 once invoked, about $0.0002 per session on Opus 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-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.