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/panquequelol/coding-agentsWrote 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/panquequelol/coding-agents/vercel)<a href="https://agentmods.dev/commands/panquequelol/coding-agents/vercel"><img src="https://agentmods.dev/badge/commands/panquequelol/coding-agents/vercel/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/panquequelol/coding-agents/vercel"><img src="https://agentmods.dev/badge/commands/panquequelol/coding-agents/vercel.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.00204 |
| Opus 5.5 | $0.00000 | $0.00082 |
| Sonnet 5.5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
vercel 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 25d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 25d ago First seen · 16 lines · 0 tokens per session scan A fd25f1f24c9e
vercel is a command published in the GitHub repository panquequelol/coding-agents (21 stars, last pushed 25d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 204 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-21.
Other commands, from other repositories
design-dashboard
Call getworkflowcommandguidance(kind="design-reporting-ui", focus="{{context}}") and follow the returned instructions verbatim. Treat focus as the conversation/request context that appeared before the slash command, including the user's recent constraints and intent. The tool returns the canonical guided-flow text for…
aitask-screen-recording
Turn a screen-recording video (.mp4, .mov, .webm, .mkv from a phone, emulator or desktop) into labelled contact sheets, key frames, a timeline, and measured animation timing and easing, because coding agents can read images but not video files. Use this whenever the user gives, attaches or mentions a video or screen…
audit-accessibility
Audit iOS app for accessibility compliance.
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.