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 amondnet/vercel-action --skill use-vercel-actiongit clone --depth 1 https://github.com/amondnet/vercel-actionWrote 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/amondnet/vercel-action/use-vercel-action)<a href="https://agentmods.dev/skills/amondnet/vercel-action/use-vercel-action"><img src="https://agentmods.dev/badge/skills/amondnet/vercel-action/use-vercel-action.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 26 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00151 | $0.02772 |
| Opus 5 | $0.00076 | $0.01386 |
| Sonnet 5 | $0.00030 | $0.00554 |
| Haiku 4.5 | $0.00015 | $0.00277 |
Grade A, and why
use-vercel-action 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 9d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
use-vercel-action
This skill teaches an agent how to consume amondnet/vercel-action correctly. Inputs and outputs documented here come from action.yml in this repo — when in doubt, open action.yml for the full surface.
When to use
- Adding
amondnet/vercel-actionto a workflow for the first time. - Fixing a workflow that already uses the action (input names, mutual exclusions, missing prerequisites).
- Choosing between CLI mode (default), experimental API mode, and the two prebuilt flows.
- Migrating from Vercel's native GitHub integration to action-driven deploys.
When NOT to use
- The user just wants the Vercel CLI locally (no GitHub Actions involved) — refer them to the official Vercel CLI docs instead.
- The user is happy with Vercel's native GitHub integration and isn't asking for action-based deploys.
Mandatory prerequisites
Consumers consistently miss these. Verify each before writing the workflow:
-
Disable Vercel's native auto-deploys in the project repo, otherwise both Vercel and the action will deploy and you'll get duplicate previews. Add to
vercel.json(orvercel.ts):{ "git": { "deploymentEnabled": false } }Legacy projects may instead use the older
{ "github": { "enabled": false } }— both are accepted. -
Link the project locally and capture the IDs. Run
vercel linkonce on a developer machine; this writes.vercel/project.jsonwithprojectIdandorgId. Store those values as GitHub repository secrets:VERCEL_TOKEN— created at https://vercel.com/account/tokensVERCEL_ORG_ID— from.vercel/project.jsonVERCEL_PROJECT_ID— from.vercel/project.json
Do not commit raw IDs into workflow files; reference them via
${{ secrets.* }}. -
GitHub Deployments need explicit permission. If you set
github-deployment: true, the workflow job must declarepermissions: deployments: write(and usuallycontents: read). Without it the deployment write call fails.
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.
- 9d ago First seen · 212 lines · 151 tokens per session scan A 77c24fc9cee7
use-vercel-action is a skill published in the GitHub repository amondnet/vercel-action (765 stars, last pushed 1mo ago), licensed MIT. It adds 151 tokens to every session and 2,772 once invoked, about $0.0008 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
failure-diagnosis
Diagnose deployment failures, container crashes, and networking issues using structured pattern matching on logs and container state. Use when a deployment fails, a container crashes or exits unexpectedly, or the app is unreachable after deployment.
deploy-flow
Full deploy pipeline — source detection, hints-driven analysis, project creation, deployment monitoring, and live URL delivery. Load when the user wants to deploy an application.
domain-tls-routing
Diagnose domain resolution, TLS certificate provisioning, and reverse proxy routing issues. Use when a domain is not resolving, TLS certificates fail, proxy returns 502/503/504, or custom domains are stuck in pending status.
caddyfile-generation
Generate Caddyfile configurations for static sites and reverse proxies — SPA fallback routing, cache headers, compression, redirects, and error pages. Use when deploying a static site that needs custom Caddy configuration, or when the user needs SPA routing, caching, or redirect rules.
java-deploy
Build and deploy Java applications — Maven, Gradle, Spring Boot, version detection, and Dockerfile patterns. Use when deploying a Java project, or when pom.xml or build.gradle is detected.
domain-attachment
Domain setup for applications. Preferred path is passing domains at creation time via createProject. Falls back to addapplicationdomain for post-creation attachment or custom domains.