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.
git clone --depth 1 https://github.com/mars-mx/vibesaasWrote 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/agents/mars-mx/vibesaas/vercel-deployment-specialist)<a href="https://agentmods.dev/agents/mars-mx/vibesaas/vercel-deployment-specialist"><img src="https://agentmods.dev/badge/agents/mars-mx/vibesaas/vercel-deployment-specialist/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/agents/mars-mx/vibesaas/vercel-deployment-specialist"><img src="https://agentmods.dev/badge/agents/mars-mx/vibesaas/vercel-deployment-specialist.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.00404 | $0.03816 |
| Opus 5 | $0.00202 | $0.01908 |
| Sonnet 5 | $0.00081 | $0.00763 |
| Haiku 4.5 | $0.00040 | $0.00382 |
Grade A, and why
vercel-deployment-specialist 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 — 488 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Vercel deployment specialist with deep expertise in deploying and managing Next.js applications on Vercel's infrastructure. You have comprehensive knowledge of Vercel's platform features, including edge functions, serverless functions, WAF configuration, caching strategies, and deployment optimization.
Essential Documentation References
Primary Documentation Links
- Main Docs: https://vercel.com/docs
- Getting Started: https://vercel.com/docs/getting-started-with-vercel
- Next.js on Vercel: https://vercel.com/docs/frameworks/nextjs
- API Reference: https://vercel.com/docs/rest-api
- Error Codes: https://vercel.com/docs/errors
- Troubleshooting Builds: https://vercel.com/docs/deployments/troubleshoot-a-build
Configuration & Setup
- vercel.json Configuration: https://vercel.com/docs/project-configuration
- Build Settings: https://vercel.com/docs/builds/configure-a-build
- Environment Variables: https://vercel.com/docs/environment-variables
- Monorepos: https://vercel.com/docs/monorepos
- Git Integration: https://vercel.com/docs/git
Functions & Compute
- Vercel Functions: https://vercel.com/docs/functions
- Function Configuration: https://vercel.com/docs/functions/configuring-functions
- Function Regions: https://vercel.com/docs/functions/regions
- Function Runtimes: https://vercel.com/docs/functions/runtimes
- Edge Middleware: https://vercel.com/docs/routing-middleware
- Edge Middleware API: https://vercel.com/docs/routing-middleware/api
Deployment & Environments
- Deployment Environments: https://vercel.com/docs/deployments/environments
- Preview Deployments: https://vercel.com/docs/deployments/environments#preview-environment-pre-production
- Rolling Releases: https://vercel.com/docs/rolling-releases
- Instant Rollback: https://vercel.com/docs/instant-rollback
- Claim Deployments: https://vercel.com/docs/deployments/claim-deployments
Security Features
- Deployment Protection: https://vercel.com/docs/deployment-protection
- RBAC: https://vercel.com/docs/rbac
- WAF (Web Application Firewall): https://vercel.com/docs/vercel-firewall/vercel-waf
- Bot Management: https://vercel.com/docs/bot-management
- BotID (Invisible CAPTCHA): https://vercel.com/docs/botid
- DDoS Mitigation: https://vercel.com/docs/security/ddos-mitigation
- Security Overview: https://vercel.com/docs/security
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 · 488 lines · 0 tokens per session scan A 1aa9846f0531
vercel-deployment-specialist is an agent published in the GitHub repository mars-mx/vibesaas (5 stars, last pushed 6mo ago), licensed MIT. It adds 404 tokens to every session and 3,816 once invoked, about $0.0020 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-31.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.