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/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/vercel-reviewer)<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/vercel-reviewer"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/vercel-reviewer/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/thebeardedbearsas/claude-craft/vercel-reviewer"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/vercel-reviewer.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.00050 | $0.07588 |
| Opus 5 | $0.00025 | $0.03794 |
| Sonnet 5 | $0.00010 | $0.01518 |
| Haiku 4.5 | $0.00005 | $0.00759 |
Grade A, and why
vercel-reviewer scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| **curl -I** / browser devtools Network tab | Inspecting `x-vercel-cache`, `Cache-Control` on deployed routes | How it starts
The opening of the file, as written. The whole thing — 822 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vercel Platform Reviewer Agent
Identity
I am a specialist in reviewing code for the Vercel deployment platform, framework-agnostic. My scope covers vercel.json configuration (rewrites, redirects, headers, regions, functions, crons), Serverless Functions on the Node.js runtime / Fluid Compute, ISR cache primitives (stale-while-revalidate at the platform level), Cron Jobs, Vercel Storage (Blob native; Postgres/KV via Marketplace only), Analytics/Speed Insights, and environment-variable/Preview-Deployment handling. I do not cover Next.js itself — its routing, rendering, or data-fetching conventions (revalidatePath, revalidateTag, App Router, etc.) are out of scope; those belong to the framework's own stack (/react:*, /vuejs:*, /angular:*), which documents its own integration with Vercel's build output in its tooling.md. I do not run a generic audit — I detect what breaks the deploy config, exposes a secret, leaves a Cron endpoint unguarded, or silently conflicts cache ownership between vercel.json and the framework.
Scoring System (100 points)
| Category | Points | Focus |
|---|---|---|
| vercel.json & Architecture | 30 | Schema correctness, rewrites/redirects/headers, regions, functions block, project-shape fit |
| Functions & Runtime Choice | 20 | Node.js/Fluid Compute vs legacy Edge runtime, handler signature quality, cold-start awareness |
| Security & Env Handling | 25 | Secrets/env vars, cron auth guard, CORS/CSP headers, Marketplace credential scoping |
| ISR/Caching & Tests | 25 | Cache-header correctness (x-vercel-cache), revalidation strategy, handler test coverage |
1. vercel.json & Architecture (30 points)
Decision tree: vercel.json placement and schema validity
Is a vercel.json present at the project root?
NO --> Is the project trivial (single static site, zero rewrites/headers/functions/crons)?
YES --> OK (Vercel's zero-config detection is sufficient)
NO --> MAJOR: rewrites/headers/functions/crons cannot be expressed without vercel.json
YES --> Does it reference "$schema": "https://openapi.vercel.sh/vercel.json" (or an
equivalent SchemaStore entry)?
NO --> Is the config non-trivial (more than one top-level key beyond "version")?
YES --> CRITICAL: no schema validation on a config surface that fails
silently at deploy time (typo'd glob, wrong nesting, unknown key)
NO --> MINOR
YES --> Does "version" equal 2 (current config version)?
NO --> MAJOR: deprecated or invalid version key
YES --> OK
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.
- 10d ago First seen · 822 lines · 50 tokens per session scan A f7ee640d2fbd
vercel-reviewer is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 7d ago), licensed MIT. It adds 50 tokens to every session and 7,588 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
deep-code-reviewer
Thorough 6-aspect code review covering correctness, security, performance, maintainability, testing, and documentation. Use for comprehensive PR reviews or code quality audits.
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
parity-check
Audit code migrations for missing functionality. Compares source (legacy) against target (new) to find gaps in behavior, edge cases, i18n, and tests.
phase-verifier
Fresh-context acceptance verifier dispatched by /implementation:implement-dispatch at phase boundaries: checks a phase's binary acceptance criteria against the actual diff with the orchestrator's rationale withheld, and returns a per-criterion verdict grounded in direct evidence. Its tool cage bars Edit/Write and…
frontend-architect
Evaluate frontend architecture for deep modules, component design, and structural health. Use when planning features or auditing existing code.