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/get-convex/convex-agent-pluginsWrote 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/get-convex/convex-agent-plugins/labs-acquire-domain)<a href="https://agentmods.dev/commands/get-convex/convex-agent-plugins/labs-acquire-domain"><img src="https://agentmods.dev/badge/commands/get-convex/convex-agent-plugins/labs-acquire-domain.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.1 | $0.00024 | $0.00240 |
| Opus 5 | $0.00012 | $0.00120 |
| Sonnet 5 | $0.00005 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
labs-acquire-domain 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 8d 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
Acquire a domain (labs) — find and buy through Convex
Suggest memorable names for the idea, check live availability + price, then (only on explicit yes) register the chosen domain through Convex and bind it to the deployment.
Steps
- Brainstorm a few on-theme names; check live availability + annual price.
- Present the top options with prices; wait for an explicit pick.
- Register through Convex (DNSimple) — a Tier-2 spend action performed by the control plane; the agent never holds the registrar credential.
- Point DNS at the deployment and attach it as a Convex custom domain; rebind the auth origin (RP_ID/ORIGIN) and re-publish.
Rules
- Never register without an explicit yes on a specific domain.
- Show the price before registering.
- If the user already owns a domain, hand off to the
domainscapability instead of buying a new one. - Rebinding the domain changes the auth origin — re-publish after.
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.
- 8d ago First seen · 20 lines · 24 tokens per session scan A 98be178f9b7a
labs-acquire-domain is a command published in the GitHub repository get-convex/convex-agent-plugins (112 stars, last pushed 10d ago), licensed MIT. It adds 24 tokens to every session and 240 once invoked, about $0.0001 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 commands, from other repositories
deploy-app
Deploy Shopify app to production with CLI release, verify deployment, and configure post-deployment webhooks and metrics.
deploy-setup
Wire CI + secrets for a fresh storefront. Run once after /init-store before the first push to main.
dev
Runs Vendure in development mode. By default it starts three processes: the GraphQL server (ts-node ./src/index.ts), the worker (ts-node ./src/index-worker.ts), and the dashboard (a Vite dev server).
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.