elizaOS is an open-source TypeScript framework and product stack for building and running autonomous AI agents. Developers use its runtime, application, command-line tool, cloud services, native bridges, and plugins to create agent-based software. The catalogue entries provide skills, commands, instructions, and rules for working with this monorepo and its agent ecosystem.
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 commands/elizaos/eliza/deploy_designgit clone --depth 1 https://github.com/elizaOS/elizaWrote 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/elizaos/eliza/deploy_design)<a href="https://agentmods.dev/commands/elizaos/eliza/deploy_design"><img src="https://agentmods.dev/badge/commands/elizaos/eliza/deploy_design.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.00000 | $0.01044 |
| Opus 5 | $0.00000 | $0.00522 |
| Sonnet 5 | $0.00000 | $0.00209 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
DEPLOY_DESIGN 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 6d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
elizaos deploy — Design Doc
Status: implemented trigger path. The CLI queues cloud deployments, can attach a custom domain, and polls public deployment status. Local build/upload, first-run credential prompting, deploy logs, and watch mode remain follow-up boundaries.
Goal
Ship a single command that takes a generated elizaOS project (template.json
present in cwd) and deploys its linked Eliza Cloud app, optionally bound to a
custom domain.
Command surface
elizaos deploy [--app-id <id>] [--domain <host>] [--dry-run] [--verbose]
--app-id <id>— Eliza Cloud app UUID. If omitted, resolved from.elizaos/template.json(values.appId/values.cloudAppId) or, failing that, by name match againstGET /api/v1/apps.--domain <host>— Custom external domain to attach after the deploy goesREADY. Must match the same regex enforced byPOST /api/v1/apps/[id]/domains:^([a-z0-9]([a-z0-9-]*[a-z0-9])?\.)+[a-z]{2,}$. Subdomain rule is enforced server-side.--dry-run— Print the planned sequence and exit 0. No network calls.--verbose— Echo local deploy settings to stderr.
Auth flow
The CLI reads ELIZAOS_CLOUD_API_KEY, ELIZA_CLOUD_API_KEY,
ELIZACLOUD_API_KEY, or ~/.elizaos/credentials.json. Requests are sent with
Authorization: Bearer <key>. The API base defaults to
https://api.eliza.app/api/v1; override with ELIZA_CLOUD_API_BASE_URL,
ELIZAOS_CLOUD_API_BASE_URL, ELIZACLOUD_API_BASE_URL, or
ELIZA_CLOUD_BASE_URL.
Deploy sequence
- auth check — load credentials and send Bearer auth with cloud requests.
- app lookup — resolve
--app-id,.elizaos/template.json, or a single owned-app name match. - trigger deploy —
POST /api/v1/apps/[id]/deploywith an empty body, letting the cloud service use the app's linked repository and stored env config. - attach domain (only when
--domainset) —POST /api/v1/apps/[id]/domainswith{ domain }. Server returns the verification TXT record + DNS instructions when needed; the CLI prints them. - poll status —
GET /api/v1/apps/[id]/deploy/statusevery 5s up to 10min. Terminal states:READY,ERROR. - print URL — final line includes the returned
vercelUrlwhen present and the custom domain when requested.
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.
- 6d ago First seen · 72 lines · 0 tokens per session scan A 0b4531e2be1a
DEPLOY_DESIGN is a command published in the GitHub repository elizaOS/eliza (19,253 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,044 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-08-30.
Other commands, from other repositories
dashboard-server-tunnel-off
Disconnect the public tunnel. Usage /dashboard:server-tunnel-off.
dashboard-server-tunnel-status
Tunnel status + public URL. Runs locally, no LLM.
dashboard-server-config
Dashboard server config (secrets redacted). Runs locally, no LLM.
estimate-cost
Estimate AWS costs for planned infrastructure or analyze current spending.
validate-template
Validate CloudFormation template for syntax, security, and best practices.
optimize-nginx
Analyze and optimize nginx configuration for performance, security, and best practices.