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 austinfox/claude-plugins --skill subdomain-deploygit clone --depth 1 https://github.com/austinfox/claude-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/skills/austinfox/claude-plugins/subdomain-deploy)<a href="https://agentmods.dev/skills/austinfox/claude-plugins/subdomain-deploy"><img src="https://agentmods.dev/badge/skills/austinfox/claude-plugins/subdomain-deploy/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/austinfox/claude-plugins/subdomain-deploy"><img src="https://agentmods.dev/badge/skills/austinfox/claude-plugins/subdomain-deploy.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.00155 | $0.03802 |
| Opus 5.5 | $0.00062 | $0.01521 |
| Sonnet 5.5 | $0.00031 | $0.00760 |
| Haiku 4.5 | $0.00015 | $0.00380 |
Grade A, and why
subdomain-deploy scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
After deploy, smoke-test against the **custom domain**, not the `*.vercel.app` URL — see Gotchas. If your local resolver hasn't picked up the new subdomain yet, force it via curl `--resolve`: How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personal Subdomain Deploy (austinfox.com)
Stand up a new personal project at <name>.austinfox.com on Vercel with the right access pattern and storage strategy for the project. This skill is for Austin's personal projects only — not client work, not company projects.
Non-Negotiables
These are the rules that distinguish this workflow from generic "deploy to Vercel":
- One Vercel project per subdomain. Never combine multiple personal projects into a single Vercel project, never use path-based routing across them. Each subdomain gets its own GitHub repo, its own Vercel project, its own env vars, its own analytics.
- Default stack: Bun + Vite + React 19 + TypeScript. Bun is the runtime/package manager; Vite is the dev server/bundler — they do different jobs and both are needed. Add Tailwind v4 (via
@tailwindcss/vite) when styling is non-trivial. Don't reach for Next.js for static personal projects. - Auth is custom Edge middleware, never Vercel's built-in Password Protection. Vercel's feature requires the Advanced Deployment Protection add-on (~$150/mo). The middleware patterns in
references/are no-ops when their env vars are unset, so they cost nothing during local dev. - Wildcard DNS is already set on Porkbun (
*.austinfox.com → cname.vercel-dns.com). New subdomains require zero DNS work —vercel domains addis sufficient. - Private GitHub repo by default. Personal projects are private unless the user explicitly says otherwise.
When to Use This Skill
Activate when the user's request implies creating a brand-new project on an austinfox.com subdomain. Strong signals:
- "deploy this" / "ship this" + the project is local-only and has no Vercel link yet
- "put it on austinfox.com" / "set up
<name>.austinfox.com" - "spin up a new personal project"
- Mentions of austinfox.com or a subdomain like
lettera.austinfox.com
Do NOT use this skill when:
- The project is already linked to a Vercel project — in that case use the generic
deploy-to-vercelskill. - The user wants to deploy to a non-austinfox.com domain — use the generic flow.
- The user is deploying a redeploy / preview / hotfix to an existing project — use the generic flow.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 250 lines · 155 tokens per session scan A 63600a5759eb
subdomain-deploy is a skill published in the GitHub repository austinfox/claude-plugins (4 stars, last pushed 3mo ago), licensed MIT. It adds 155 tokens to every session and 3,802 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (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
activate-site
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
deploy
Builds and deploys a Power Apps code app to Power Platform. Use when deploying changes, redeploying an existing app, or pushing updates.
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…
cloud-infrastructure
Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand.
deploy-to-connect
Deploy or publish Python and R content to a Posit Connect server using rsconnect-python or the R rsconnect package. Handles interactive apps and dashboards, web APIs, rendered documents, and prepared bundles/manifests. Use whenever the user asks to deploy, publish, or redeploy content to Posit Connect, or mentions…