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/MonumentalSystems/Atlas-Agent-TeamsWrote 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/commands/monumentalsystems/atlas-agent-teams/vercel-gen-ui)<a href="https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/vercel-gen-ui"><img src="https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/vercel-gen-ui/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/commands/monumentalsystems/atlas-agent-teams/vercel-gen-ui"><img src="https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/vercel-gen-ui.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.00000 | $0.00135 |
| Opus 5 | $0.00000 | $0.00068 |
| Sonnet 5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
vercel-gen-ui 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 7d 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.
What it actually says
Vercel Generative UI Command
Main command for the Vercel Generative UI team.
Usage
/vercel-gen-ui [subcommand]
Subcommands
build- Build a new generative UI applicationadd-ai- Add AI features to existing appdeploy- Deploy to Vercelcomponent- Create AI-powered componentstream- Add streaming to a feature
Examples
/vercel-gen-ui build my-gen-ui-app
/vercel-gen-ui add-ai --feature chat
/vercel-gen-ui component streaming-chat
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.
- 7d ago First seen · 26 lines · 0 tokens per session scan A 107235f8fd98
vercel-gen-ui is a command published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 135 tokens. 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-09-03.
Other commands, from other repositories
mlops
Invoke the MLOps Engineer for model serving & inference infrastructure, ML/AI pipelines, model deployment & monitoring, and infrastructure-level AI cost optimization.
azure-openai-deploy
Provision a new Azure OpenAI deployment — select model, SKU, capacity, content filter, and apply governance guardrails.
data-pipeline
You are a data pipeline architecture expert specializing in scalable, reliable, and cost-effective data pipelines for batch and streaming data processing.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.