Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/kok-o/koko-contextos-agentsnpx agentmods add skills/kok-o/koko-contextos-agents/vercel-optimizeWrote 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/kok-o/koko-contextos-agents/vercel-optimize)<a href="https://agentmods.dev/skills/kok-o/koko-contextos-agents/vercel-optimize"><img src="https://agentmods.dev/badge/skills/kok-o/koko-contextos-agents/vercel-optimize.svg" alt="Measured on agentmods" 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.00116 | $0.00957 |
| Opus 5 | $0.00058 | $0.00478 |
| Sonnet 5 | $0.00023 | $0.00191 |
| Haiku 4.5 | $0.00012 | $0.00096 |
Grade A, and why
vercel-optimize 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 3d 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-optimize — 335 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vercel Optimize
Overview
Observability-first Vercel performance and cost reduction optimization skill. Evaluates deployed Next.js, SvelteKit, Nuxt, and Astro projects using production telemetry signals (signals.json), deterministic candidate gating, and code scanning to deliver ranked, verified architectural recommendations.
When to Use
- When tasked with reducing Vercel bills, Function Invocations, Fast Data Transfer, or Build Minutes.
- When diagnosing slow serverless routes, cold starts, or Edge vs Node runtime mismatches.
- When evaluating caching opportunities (
stale-while-revalidate, ISR, CDN edge caching) or Core Web Vitals degradation.
Rules & Patterns
1. Prerequisites & Framework Support
- Vercel CLI v53+ with
vercel metrics,vercel usage,vercel contract, andvercel api. - Authenticated CLI session (
vercel login) and linked app directory (vercel link). - Framework support: Next.js App Router (Full), Pages Router (Supported), SvelteKit (Supported), Nuxt (Supported), Astro (Limited).
- Security rule: Never put auth tokens in shell commands (
VERCEL_TOKEN=...is banned in chat/logs).
2. Core Doctrine & Gating Pipeline
- Metrics First: Recommendations start from Vercel production signals (14-day window), not repo-wide grep.
- Deterministic Gates:
scripts/gate-investigations.mjsselects code-scope and platform-scope candidates. - Candidate-Bound Scope: Inspect only files named by a candidate or a route-local import chain.
- Version-Aware Citations: Use only verified citations matching the target framework version.
- Specific Cache Policies: When recommending caching, state the exact cache policy and headers; keep auth-sensitive and error responses dynamic.
3. Recommendation Rules
- Every recommendation must trace to a launched candidate and include observed metric evidence.
- Cite verified files with line numbers when code changes are proposed.
- Use precise observed performance numbers; avoid customer-facing speculative
$Nsavings formulas. - Do not recommend duration reductions for Vercel Workflow runtime endpoints (
/.well-known/workflow/v1/*).
What ships with it
2 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.
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.
- 3d ago Changed · -239 lines b25941d505ca
- 8d ago First seen · 323 lines · 116 tokens per session scan A 95ae2683b30d
vercel-optimize is a skill published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 4d ago), licensed MIT. It adds 116 tokens to every session and 957 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vercel-optimize, differing in 335 lines, and is treated as a copy.
Other skills, from other repositories
deploy-release
Prepare and verify a staged or production deployment with rollback and smoke checks.
system-design-building-blocks
Select infrastructure components by the constraint each removes: load balancers, caches and invalidation, queues and pub/sub, CDN, API gateway, rate limiting, consistent hashing. Use when choosing cache, queue, replica, or edge layers; defer engine tuning to the database category.
harden-vps
Harden a production Linux VPS for your application across three layers — application (systemd hardening, monitoring alerts, backup automation), Ubuntu OS (UFW firewall, fail2ban SSH, unattended-upgrades, SSH hardening), and VPS provider (health checks, daily backups, monthly snapshots). Use when the user wants to…
deploy
Build → verify artifact → deploy → wait → smoke deployment pipeline. Platform-agnostic (MCP or CLI), with configurable timeout, retry with exponential backoff, and integrated health-check. The deploy half of CI/CD: run after build to push to production.
wire-observability
Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.
deploy
Deploy an application to a configured environment.