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/toyamarinyon/giselleWrote 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/rules/toyamarinyon/giselle/vercel-cli)<a href="https://agentmods.dev/rules/toyamarinyon/giselle/vercel-cli"><img src="https://agentmods.dev/badge/rules/toyamarinyon/giselle/vercel-cli/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/rules/toyamarinyon/giselle/vercel-cli"><img src="https://agentmods.dev/badge/rules/toyamarinyon/giselle/vercel-cli.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.00005 | $0.00299 |
| Opus 5.5 | $0.00002 | $0.00120 |
| Sonnet 5.5 | $0.00001 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
vercel-cli 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 1mo 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.
This is a copy
100% identical to vercel-cli — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Vercel CLI Setup Guide
Installation
To install Vercel CLI globally using pnpm (recommended for this project):
pnpm i -g vercel
Authentication
Log in to your Vercel account:
vercel login
Project Setup
Link to Existing Project
vercel link
Development Workflow
Test Locally
Run a local development server that replicates the Vercel environment:
vercel dev
Environment Variables
Pull Environment Variables
Download environment variables to a local .env file:
vercel env pull
Common Commands
Check CLI Version
vercel --version
Update CLI
pnpm i -g vercel@latest
View Deployments
vercel list
View Logs
vercel logs [deployment-url]
Project Configuration
Vercel projects can be configured using a vercel.json file in your project root. This allows you to define build settings, routes, environment variables, and more.
Refer to the Vercel documentation for more detailed information on available commands and configuration options.
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.
- 1mo ago First seen · 85 lines · 5 tokens per session scan A b0bc37a971ee
vercel-cli is a cursor rule published in the GitHub repository toyamarinyon/giselle (4 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 5 tokens to every session and 299 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to vercel-cli, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.