What is apps-deploying-vercel-branches?

A deployment guide for sending frontend applications to Vercel, a service that builds and hosts web applications. It describes branch-based deployment patterns and checks that the deployed build actually succeeded.

Use it to deploy applications through direct branch pushes or scheduled GitHub Actions workflows. It helps verify the result after Vercel builds the application.

It removes guesswork from moving an environment branch and distinguishing a successful push from a successful deployment. It also covers projects with production, staging, or test-only workflows.

apps-deploying-vercel-branches — Skill by wahidyankf/ose-public

Install

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.

Any agent

npx skills add wahidyankf/ose-public --skill apps-deploying-vercel-branches

Clone the repo

git clone --depth 1 https://github.com/wahidyankf/ose-public

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/wahidyankf/ose-public/apps-deploying-vercel-branches/github.svg)](https://agentmods.dev/skills/wahidyankf/ose-public/apps-deploying-vercel-branches)

Your own site

<a href="https://agentmods.dev/skills/wahidyankf/ose-public/apps-deploying-vercel-branches"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/apps-deploying-vercel-branches/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/wahidyankf/ose-public/apps-deploying-vercel-branches"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/apps-deploying-vercel-branches.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 522 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00090	$0.00522
Opus 5.5	$0.00036	$0.00209
Sonnet 5.5	$0.00018	$0.00104
Haiku 4.5	$0.00009	$0.00052

Measured 2d ago against content hash 9873c51311f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

apps-deploying-vercel-branches 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 2d 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.

.agents/skills/apps-deploying-vercel-branches/SKILL.md · 39 lines

What it actually says

Deploying Vercel Branches Skill

Purpose

Every apps-*-deployer agent in this repo ships a frontend by moving an environment branch, never by running a local build. This skill holds the procedure once so each deployer agent's own file only needs to state its target-specific values (branch name, project slug, workflow file).

The Three Patterns

Direct force-push (reference/01-direct-force-push-workflow.md) — validate main, force-push straight to a prod-* branch Vercel watches. Used by production sites with no staging gate.
Scheduled staging workflow (reference/02-scheduled-staging-workflow.md) — trigger a GitHub Actions workflow that runs the full local-stack test suite, then force-pushes stag-* branches itself. Used by app groups with a staging tier.
Scheduled test-only workflow (reference/03-scheduled-test-only-workflow.md) — trigger a GitHub Actions workflow that only runs tests; no deploy target exists yet. Used where staging/prod infrastructure is not provisioned.

All three share reference/04-post-deploy-verification-vercel-mcp.md — the Vercel MCP protocol that confirms a build actually succeeded, since a successful push is not evidence of a successful deploy.

How a Deployer Agent Uses This Skill

The agent's own file states which pattern applies and its target parameters (branch, project slug, team, workflow filename). It then points its ## Required Reading section at this skill's reference/ directory instead of repeating the procedure inline.

References

Files

What ships with it

6 files 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.

Changes

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.

2d ago First seen · 39 lines · 90 tokens per session scan A 9873c51311f9

Subscribe to this mod's changes

apps-deploying-vercel-branches is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 522 once invoked, about $0.0004 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-14.

CI and CD Cloud DevOps and cloud TypeScript erp islamic-finance monorepo nx sharia-compliant

turborepo

Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.

vercel/turborepo · 50 tokens

investigate-cloudflare

Investigate deployed Worker failures, regressions, and missing operational signals using Cloudflare Issues, logs, traces, SQL, or Observability MCP. Produce bounded evidence and verify recurrence against the deployed version.

brandhaug/b2b-saas-starter · 45 tokens

configure-cloudflare-monitoring

Configure or reconcile Cloudflare SQL alerts and shared Worker dashboards for a deployment, adapt monitoring to a scenario, and verify thresholds, missing data, and delivery. Use for monitoring setup or changes; use investigate-cloudflare for incident diagnosis.

brandhaug/b2b-saas-starter · 52 tokens

apps-deploying-vercel-branches