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 skills add elizaOS/eliza --skill eliza-cloudgit 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/skills/elizaos/eliza/eliza-cloud)<a href="https://agentmods.dev/skills/elizaos/eliza/eliza-cloud"><img src="https://agentmods.dev/badge/skills/elizaos/eliza/eliza-cloud/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/elizaos/eliza/eliza-cloud"><img src="https://agentmods.dev/badge/skills/elizaos/eliza/eliza-cloud.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk fail
- NVIDIA SkillSpector pass
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.00191 | $0.03892 |
| Opus 5 | $0.00096 | $0.01946 |
| Sonnet 5 | $0.00038 | $0.00778 |
| Haiku 4.5 | $0.00019 | $0.00389 |
Grade A, and why
eliza-cloud 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 13d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eliza Cloud
Use this skill whenever Eliza Cloud is enabled, linked, or the task involves building an app that could use Cloud as its backend.
Default Stance
Treat Eliza Cloud as the default managed backend before inventing separate auth, billing, analytics, or hosting. In this repo, Cloud already supports:
- app registration and API keys
appId-based app auth flows- cloud-hosted chat, media, agent, and billing APIs
- app analytics, user tracking, domains, and credits
- creator monetization, app charge requests, affiliate links, x402 payment requests, and payout redemptions
- Docker container deployments for server-side workloads
- on-demand cloud tunnel provisioning for agents through Headscale-backed Tailscale sessions
Read These References First
references/cloud-backend-and-monetization.mdfor apps, auth, billing, and earningsreferences/apps-and-containers.mdfor deployment, domains, and container workflowreferences/app-platform-lifecycle.mdfor the unified app platform contract, current frontend-hosting reality, and app lifecycle orderreferences/payments-and-promotion.mdfor app charges, x402 requests, local billing proxy aliases, payout redemptions, promotion assets, advertising, image/video/music/TTS generation, and parent-agent Cloud commands
Skill Pairing
Use build-monetized-app alongside this skill for any new Cloud app that
should earn money. build-monetized-app owns the build, deploy, monetize, and
custom-domain offer flow; eliza-cloud owns the current Cloud backend surface,
existing-app management, app charge requests, x402 requests, affiliate earnings,
payout redemptions, media/promotion, and account-bound parent-agent commands.
Spawned code agents should load or request both skills for Cloud app builds.
Default Build Flow
For new agent-built apps, defer to build-monetized-app: register a Cloud app,
publish the frontend, deploy a container only if the app needs server-side code,
enable monetization, and then offer a custom domain.
What ships with it
4 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.
- 13d ago First seen · 229 lines · 191 tokens per session scan A c67684d407b3
eliza-cloud is a skill published in the GitHub repository elizaOS/eliza (19,326 stars, last pushed today), licensed MIT. It adds 191 tokens to every session and 3,892 once invoked, about $0.0010 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 skills, from other repositories
oss-alternatives
Find actively maintained open source alternatives to any paid SaaS tool or commercial API. Use this skill whenever a user mentions wanting to replace, swap out, self-host, or find a free/open source version of a paid tool — including but not limited to tools like Datadog, Algolia, Twilio, Stripe, Auth0, Segment…
wegent-knowledge
Knowledge base management and search tools for Wegent. Provides capabilities to list, create, update, and search knowledge bases and documents using RAG retrieval. Use this skill when the user wants to manage knowledge bases, documents, or search for information programmatically.
01-bootstrap
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
tech-design
A guided process for writing a backend technical design from a product requirements document or feature description. A technical design explains how a feature should work in code and services.
api-debug
Debug REST, GraphQL, webhook, and OAuth/API-key integrations with layered request, auth, schema, and response checks.
game-networking
Design, implement, test, secure, and profile multiplayer game networking across engines, including authority, replication, prediction, rollback, lobbies, reconnects, and adverse network conditions.