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.
npx skills add chadixearth/graphyloop --skill vercel-deploygit clone --depth 1 https://github.com/chadixearth/graphyloopWrote 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/chadixearth/graphyloop/vercel-deploy)<a href="https://agentmods.dev/skills/chadixearth/graphyloop/vercel-deploy"><img src="https://agentmods.dev/badge/skills/chadixearth/graphyloop/vercel-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/chadixearth/graphyloop/vercel-deploy"><img src="https://agentmods.dev/badge/skills/chadixearth/graphyloop/vercel-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.00052 | $0.00745 |
| Opus 5 | $0.00026 | $0.00373 |
| Sonnet 5 | $0.00010 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
vercel-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 5d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vercel deploy
A deploy is user-visible and hard to undo. The checks below cost a minute; skipping them costs a broken production URL, or a build that succeeds and then throws at runtime because a key only existed locally.
When to activate
- Shipping a preview or production deployment.
- "works locally, fails on Vercel" symptoms.
- Setting up a project's deploy pipeline for the first time.
Procedure
preflight target=deploy. Clear every blocker: missingVERCEL_TOKEN, nobuildscript, env files not git-ignored.- Link the project (
vercel link) so.vercel/project.jsonpins org and project id — otherwise later commands are ambiguous about where they ship. - Mirror runtime env keys into Vercel. A local
.env.localis NOT deployed. Every key the app reads at runtime must exist in the Vercel project, per environment (production / preview / development):vercel env add <KEY> production. Never print the values. - Migrate the database BEFORE the app deploy. New code against an old schema fails immediately; old code against an additive schema usually survives. Dry-run first, keep a rollback note. Destructive changes (drop, rename, narrowing a type) need two deploys — add the new shape, ship code, remove the old shape later.
- Build locally (
npm run build) — the cheapest possible failure. - Preview deploy (
vercel deploy) and verify the REAL URL: the touched flow, not just that the page renders. Check function logs for runtime errors. - Production (
vercel deploy --prod) only after explicit user approval, with the rollback command recorded in the report.
Rollback
vercel rollback(or promote the previous deployment) restores the app in seconds.- A migration does not roll back with the app. If the deploy included a destructive migration, the rollback plan is the down migration — write it before applying the up.
Common failure modes
| Symptom | Cause |
|---|---|
| Build passes, runtime 500 | env key exists locally, missing in the Vercel project |
| Works in preview, breaks in production | key set for preview only, or a different database per environment |
Module not found in the build |
runtime import from devDependencies, or a case-sensitive path that only works locally |
| Client-side "invalid API key" | server-only key referenced from client code, or a public key missing its NEXT_PUBLIC_ prefix |
| Function timeout | long request in a serverless handler — move it to a background job |
| Stale content after deploy | cached route/ISR — confirm revalidation instead of assuming a bad build |
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.
- 5d ago First seen · 63 lines · 52 tokens per session scan A 3718ceecb426
vercel-deploy is a skill published in the GitHub repository chadixearth/graphyloop (2 stars, last pushed 23d ago), licensed MIT. It adds 52 tokens to every session and 745 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
kirby-performance-and-media
Improves Kirby performance and media delivery (cache tuning, CDN, responsive images, lazy loading). Use when optimizing page speed, caching, or image handling.
deploy-to-vercel
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
cloudflare-deploy
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
netlify-deploy
Deploy web projects to Netlify using the Netlify CLI (npx netlify). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.
vercel-deploy
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
render-deploy
Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.