Borrowing it
Nothing to install: this file belongs to ieeecsopen/mcp-cs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ieeecsopen/mcp-cs/main/.agents/skills/devops-vercel-render-deploy/SKILL.mdgit clone --depth 1 https://github.com/ieeecsopen/mcp-csWrote 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/ieeecsopen/mcp-cs/devops-vercel-render-deploy)<a href="https://agentmods.dev/skills/ieeecsopen/mcp-cs/devops-vercel-render-deploy"><img src="https://agentmods.dev/badge/skills/ieeecsopen/mcp-cs/devops-vercel-render-deploy/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/ieeecsopen/mcp-cs/devops-vercel-render-deploy"><img src="https://agentmods.dev/badge/skills/ieeecsopen/mcp-cs/devops-vercel-render-deploy.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.00115 | $0.00651 |
| Opus 5.5 | $0.00046 | $0.00260 |
| Sonnet 5.5 | $0.00023 | $0.00130 |
| Haiku 4.5 | $0.00012 | $0.00065 |
Grade A, and why
devops-vercel-render-deploy 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 2mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2mo ago First seen · 56 lines · 115 tokens per session scan A d4d639641812
devops-vercel-render-deploy is a skill published in the GitHub repository ieeecsopen/mcp-cs (3 stars, last pushed 1mo ago), with no licence file. It adds 115 tokens to every session and 651 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
viberaven
Use VibeRaven when working on an AI-built app that must ship to real users; when the user asks to ship, deploy, go to production, connect auth, database, payments, RLS, env vars, webhooks, or monitoring; when production-only errors appear; or when the agent needs product context (versions, providers, launch risks)…
vercel-supabase-launch-check
Use when an AI-built app on Vercel and Supabase (Lovable, Bolt, v0, Cursor or Claude Code output) is about to launch or be handed to a client, or when the user asks whether Supabase tables are missing RLS, whether a policy lets everyone read or write, whether a service role or secret key leaked into client code or a…
go-live
Use when a user wants an AI-built local project pushed to GitHub and deployed live on Vercel with the least friction, while keeping git, secrets, provider setup, and live proof explicit.
prelaunch-check
Use when the user has an AI-built app that deploys on Vercel and uses Supabase and asks whether it is ready to launch or hand off, wants to find Supabase migrations that create tables without RLS, or pastes a production error about RLS, env vars, the database connection, the service role key or a Stripe webhook. Not…
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
architecture-context
Use when an AI coding agent starts real app work, product feature design, provider work, migrations, auth, billing, storage, webhooks, deploys, or any task where unclear architecture could cause broad or unsafe changes.