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 pivoshenko/pivoshenko.ai --skill vercel-hygienegit clone --depth 1 https://github.com/pivoshenko/pivoshenko.aiWrote 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/pivoshenko/pivoshenko.ai/vercel-hygiene)<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.
<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>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.00173 | $0.03032 |
| Opus 5.5 | $0.00069 | $0.01213 |
| Sonnet 5.5 | $0.00035 | $0.00606 |
| Haiku 4.5 | $0.00017 | $0.00303 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 140 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.
First, mcp__vercel__list_projects on team pivoshenko: any project not in the Sites table = attention, name it - an unlisted project is exactly the drift this sweep exists to catch.
What ships with it
1 file 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.
- 1mo ago Changed · -9 lines e5d4f92fe046
- 1mo ago Changed · +2 lines · +11 tokens per session dad1c9059157
- 1mo ago Changed 9099fd1f8e74
- 1mo ago Changed · +12 lines 241ad679205e
- 1mo ago First seen · 135 lines · 162 tokens per session scan A 15d975c2788b
vercel-hygiene is a skill published in the GitHub repository pivoshenko/pivoshenko.ai (6 stars, last pushed 6d ago), licensed MIT. It adds 173 tokens to every session and 3,032 once invoked, about $0.0007 per session on Opus 5.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.
Other skills, from other repositories
agents-sdk
Build, debug, or review Cloudflare Agents SDK applications using the agents package.
cloudflare-one-migrations
Assess and plan migrations from existing VPN, SWG, or SASE platforms to Cloudflare One, including policy mapping, parity gaps, and rollout.
sandbox-stable
Build or maintain Cloudflare Sandbox apps on the stable @cloudflare/sandbox package. Use sandbox-next for preview apps and sandbox-migrate-to-next for stable-to-preview migrations.
sandbox-migrate-to-next
Migrate Cloudflare Sandbox apps from stable @cloudflare/sandbox to @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-next for apps already on the preview.
sandbox-next
Build or maintain Cloudflare Sandbox apps on @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-migrate-to-next when porting a stable app.
cf-cli
Cloudflare's official cf CLI (beta) for the public Cloudflare API and Workers projects. Use for finding and running Cloudflare commands from the terminal — sign-in and profiles, cf cli search, cf schema, cf deploy/dev/build, resource commands for DNS, zones, D1, KV, and R2 — and for choosing between cf and Wrangler in…