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 agentmods add instructions/amondnet/vercel-action/claude-mdgit clone --depth 1 https://github.com/amondnet/vercel-actionWrote 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/instructions/amondnet/vercel-action/claude-md)<a href="https://agentmods.dev/instructions/amondnet/vercel-action/claude-md"><img src="https://agentmods.dev/badge/instructions/amondnet/vercel-action/claude-md.svg" alt="Measured on agentmods" 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 | $0.00669 | $0.00669 |
| Opus 5 | $0.00334 | $0.00334 |
| Sonnet 5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
vercel-action CLAUDE.md 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
@AGENTS.md
Project Overview
This is a GitHub Action that deploys projects to Vercel. It's a pnpm-based package that integrates with GitHub workflows to automate deployments, providing more control than Vercel's native GitHub integration.
Package Manager
This project uses pnpm as its package manager. The project is configured as a monorepo with workspaces for the example projects. Make sure to use pnpm commands instead of npm.
Essential Commands
Development
pnpm install # Install dependencies
pnpm start # Run the action locally (node ./index.js)
pnpm run lint # Run ESLint
pnpm run lint:fix # Run ESLint and fix issues
pnpm test # Run Jest tests
pnpm run all # Run lint, package, and test in sequence
Building for Distribution
pnpm run build # Build the action with ncc (outputs to dist/)
Important: The dist/ folder must be committed when creating releases. This contains the bundled action code that GitHub Actions will execute.
Architecture
Core Components
-
index.js: Main entry point that:
- Reads GitHub Action inputs (vercel-token, github-token, etc.)
- Executes Vercel CLI commands for deployment
- Comments on PRs/commits with deployment URLs
- Handles alias domain assignment
- Manages environment variables for Vercel org/project
-
action.yml: Defines the GitHub Action interface:
- Input parameters configuration
- Output values (preview-url, preview-name)
- Runtime environment (Node.js 20)
Key Dependencies
@actions/core: GitHub Actions toolkit for inputs/outputs@actions/exec: Execute shell commands@actions/github: GitHub API interactionsvercel: CLI for deploymentsaxios: HTTP requests for alias management
Deployment Flow
- Action reads configuration from inputs and environment
- Sets up Vercel org/project IDs from
.vercel/directory - Executes
vercelcommand with appropriate flags - Parses deployment URL from output
- Optionally assigns alias domains
- Comments on GitHub PR/commit with deployment info
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 · 78 lines · 669 tokens per session scan A 93ec07f1f2b5
vercel-action CLAUDE.md is an instructions file published in the GitHub repository amondnet/vercel-action (765 stars, last pushed 1mo ago), licensed MIT. It adds 669 tokens to every session, about $0.0033 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-30.
Other instructions, from other repositories
workflow AGENTS.md
AGENTS.md instructions for vercel/workflow, covering agent instructions, architecture, core components, workflow execution model and development commands.
ConsultMe CLAUDE.md
Claude Code instructions for Tarek-Bohdima/ConsultMe, covering claude.md, project context, common commands, module graph and conventions enforced by tooling.
awsmux AGENTS.md
Instructions for 0hardik1/awsmux, covering agents.md, what awsmux is, build, test, verify, layout and the safety model — invariants you must not weaken.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
agent-skills fortrabbit.instructions.md
Instructions for fortrabbit/agent-skills, covering fortrabbit — github copilot instructions, what fortrabbit is, configuration lookup, available operations and mcp server (optional).
testivai-oss CLAUDE.md
Claude Code instructions for testivai/testivai-oss, covering testivai-oss — claude code guide, repo layout, package manager, common commands and architecture — how the oss lane works.