What is vercel-hygiene?

A procedure for checking and hardening four websites hosted on Vercel, a platform for deploying web applications. It produces a report for each site and applies fixes only after confirmation.

Use it to inspect Vercel site settings and code, check security headers and analytics, review an OK/attention/action report, and verify confirmed fixes.

It helps find missing security settings and analytics coverage across several related sites without silently changing them. Shared configuration fixes can then apply to all sites on a later deployment.

vercel-hygiene — Skill for Claude Code and Codex by pivoshenko

Install

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.

Any agent

npx skills add pivoshenko/pivoshenko.ai --skill vercel-hygiene

Clone the repo

git clone --depth 1 https://github.com/pivoshenko/pivoshenko.ai

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/vercel-hygiene/github.svg)](https://agentmods.dev/skills/pivoshenko/pivoshenko.ai/vercel-hygiene)

Your own site

<a href="https://agentmods.dev/skills/pivoshenko/pivoshenko.ai/vercel-hygiene"><img src="https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/vercel-hygiene/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pivoshenko/pivoshenko.ai/vercel-hygiene"><img src="https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/vercel-hygiene.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 162 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,954 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00162	$0.02954
Opus 5	$0.00081	$0.01477
Sonnet 5	$0.00032	$0.00591
Haiku 4.5	$0.00016	$0.00295

Measured yesterday against content hash 9099fd1f8e74, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

vercel-hygiene 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 yesterday.

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.

skills/vercel-hygiene/SKILL.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vercel Hygiene

Read-only sweep -> per-site report (ok / attention / action) -> confirm -> apply -> verify. Use the Vercel MCP (mcp__vercel__*) for dashboard state; read on-disk files for code-side checks.

Run every check; never report a finding this file predicts. Each check below states the command and the optimal value — the verdict comes from the run, not from here. Baked-in findings are how an audit skill rots: the fix lands, the skill keeps reporting the gap, and the next sweep raises phantom actions against work already done.

Sites

Team pivoshenko. Local repos are siblings under ~/Development/sources/; each site's app lives in <repo>/site/.

Project	Repo	Domain
`pivoshenko.dev`	`pivoshenko.dev`	`pivoshenko.dev`, `www.pivoshenko.dev`
`pivoshenko.startpage`	`pivoshenko.startpage`	`startpage.pivoshenko.dev`
`pivoshenko.wallpapers`	`pivoshenko.wallpapers`	`wallpapers.pivoshenko.dev`
`pivoshenko.ai`	`pivoshenko.ai`	`ai.pivoshenko.dev`

Shared foundation: pivoshenko.ui (git-tag-pinned per site). Config and chrome live there — baseNextConfig, <SiteLayout>, tokens — so a fix there propagates to all 4 on the next tag bump. Prefer shared fixes over per-site duplication.

Mind the two path shapes: sites import pivoshenko.ui/next/config, but on disk that file is pivoshenko.ui/ui/next/config.ts (the package export strips the leading ui/). Grep the disk path; a grep of the import path finds nothing and reads as "no shared headers" when the opposite is true.

Repo missing locally -> run the MCP-side checks anyway, mark the code-side ones skipped (no local repo), and name them. Never infer a code-side verdict from the dashboard.

Sweep (Read-Only)

Every check runs against all 4 sites and appears in the report — clean ones as ok, never silently omitted; omission reads as "not checked". Lead with security headers and analytics coverage.

1. Security Headers

Check: the shared source first — grep -n headers ~/Development/sources/pivoshenko.ui/ui/next/config.ts — then per site, grep -n headers <repo>/site/vercel.json <repo>/site/next.config.ts and ls <repo>/site/middleware.ts.
Optimal: headers() defined once in baseNextConfig, inherited by all 4.
A site may narrow the shared set in its own next.config.ts, but only by awaiting baseNextConfig.headers?.() and filtering — that keeps one source of truth and makes the exception visible. pivoshenko.startpage does this for X-Frame-Options (it's meant to be framed). A site that redefines headers from scratch, or sets them in vercel.json, = attention: it silently stops inheriting later additions.
Absent from the shared config -> action, one fix for all 4. Minimum set:

Read the full file on GitHub · 147 lines

Changes

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.

yesterday Changed 9099fd1f8e74
7d ago Changed · +12 lines 241ad679205e
12d ago First seen · 135 lines · 162 tokens per session scan A 15d975c2788b

Subscribe to this mod's changes

vercel-hygiene is a skill published in the GitHub repository pivoshenko/pivoshenko.ai (4 stars, last pushed 2d ago), licensed MIT. It adds 162 tokens to every session and 2,954 once invoked, about $0.0008 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.

Cloud DevOps and cloud Security agents ai ai-agents ai-skills deploy mcp nextjs skills vercel

vercel-hygiene

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Vercel Hygiene

Sites

Sweep (Read-Only)

1. Security Headers

What this file has done since we first saw it

Other skills, from other repositories

agents-sdk

cloudflare-one-migrations

sandbox-stable

sandbox-migrate-to-next

sandbox-next

durable-objects