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 osouthgate/agent-plus-skills --skill vercel-remotegit clone --depth 1 https://github.com/osouthgate/agent-plus-skillsWrote 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/osouthgate/agent-plus-skills/vercel-remote)<a href="https://agentmods.dev/skills/osouthgate/agent-plus-skills/vercel-remote"><img src="https://agentmods.dev/badge/skills/osouthgate/agent-plus-skills/vercel-remote/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/osouthgate/agent-plus-skills/vercel-remote"><img src="https://agentmods.dev/badge/skills/osouthgate/agent-plus-skills/vercel-remote.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.00117 | $0.02988 |
| Opus 5 | $0.00059 | $0.01494 |
| Sonnet 5 | $0.00023 | $0.00598 |
| Haiku 4.5 | $0.00012 | $0.00299 |
Grade B, and why
vercel-remote scanned grade B with 2 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Missing token → "Set in project `.env` or `.env.local` (keys prefixed `VERCEL_`), or `~/.claude/settings.json`. Get one: https://vercel.com/account/tokens" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**This wrapper's scope is deliberately narrow:** projects (list/resolve), `overview`, deployments (list/show/trigger via Deploy Hook), `logs`, domains (list/verify), and env (list NAMES / set / remove). Anything outside How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vercel-remote
Project-scoped CLI that wraps the Vercel REST API into a read-first, JSON-output overview tool. Stdlib-only Python 3 (no pip installs, no venvs). Designed for agent-driven incident triage — one call returns the full project/deployments/domains/env-names picture so you don't burn tool calls chaining per-resource requests.
Lives at ${CLAUDE_SKILL_DIR}/../../bin/vercel-remote; the plugin auto-adds bin/ to PATH, so just run vercel-remote ....
Prerequisites
VERCEL_TOKENset (project.env/.env.localor shell env). Get one at https://vercel.com/account/tokens.- Optional:
VERCEL_TEAM_IDfor team-scoped projects. Every API call appends?teamId=…when set. - Optional:
VERCEL_PROJECTto omit--projecton every call.
The CLI bails with a clear missing-config message if VERCEL_TOKEN is absent.
When to reach for this
- User asks "what's happening on " → run
overview --project <name> --pretty. One call → project info + recent deployments (with commit metadata) + domain health + env var NAMES + top-level warnings. - User asks "why is prod broken" → run
deployments list --project <name> --state error --limit 5thenlogs <deployment-url> --errors-only. - User asks "what env vars does have" → run
env list --project <name>. Names only — values never touch output. - User asks "trigger a deploy" → run
deployments trigger --hook-url <hook> --wait. Waits up to 15 min for build completion. - User asks "is my domain verified" → run
domains list --project <name>ordomains verify <domain> --project <name> --wait.
Headline commands
vercel-remote projects list [--pretty]
vercel-remote projects resolve <name-or-id>
vercel-remote overview --project <name> [--limit 10] [--pretty]
vercel-remote deployments list [--project <name>] [--state ready|error|building|queued|canceled] [--limit 20]
vercel-remote deployments show <deployment-or-url>
vercel-remote deployments trigger --hook-url <url> [--wait] [--timeout 900]
vercel-remote logs <deployment-or-url> [--since 1h] [--errors-only] [--limit 100]
vercel-remote domains list --project <name>
vercel-remote domains verify <domain> --project <name> [--wait] [--timeout 300]
vercel-remote env list --project <name> [--env production|preview|development]
vercel-remote env set <KEY> <VALUE> --project <name> [--env ...] [--wait]
vercel-remote env remove <KEY> --project <name> [--env ...] [--wait]
vercel-remote whoami [--json] # identity for `agent-plus refresh` ("what's my vercel identity")
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.
- 9d ago First seen · 172 lines · 117 tokens per session scan B ce89b36a4c42
vercel-remote is a skill published in the GitHub repository osouthgate/agent-plus-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 117 tokens to every session and 2,988 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
coolify
Operate a Coolify self-hosted PaaS through the @masonator/coolify-mcp server. Use this skill whenever the user asks Claude to inspect, deploy, restart, debug, or manage anything on Coolify — including applications, databases, services, servers, projects, environments, deployments, environment variables, private keys…
cloud-administration
Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider does not do for you. Use this to structure subscriptions or tenants, get…
network-administration
Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…
virtualization-operations
Runs the hypervisor layer beneath the servers — host capacity and consolidation ratios, VM sprawl, snapshot discipline, resilience and live migration, and licensing that counts cores rather than instances. Use this to size or expand a cluster, work out why VMs are slow when the hosts look idle, clean up sprawl, set…
business-continuity-and-resilience
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.