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 dappros/ethora-mcp-server --skill ethora-quickstartgit clone --depth 1 https://github.com/dappros/ethora-mcp-serverWrote 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/dappros/ethora-mcp-server/ethora-quickstart)<a href="https://agentmods.dev/skills/dappros/ethora-mcp-server/ethora-quickstart"><img src="https://agentmods.dev/badge/skills/dappros/ethora-mcp-server/ethora-quickstart/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/dappros/ethora-mcp-server/ethora-quickstart"><img src="https://agentmods.dev/badge/skills/dappros/ethora-mcp-server/ethora-quickstart.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.00061 | $0.00672 |
| Opus 5.5 | $0.00024 | $0.00269 |
| Sonnet 5.5 | $0.00012 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
ethora-quickstart 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 10d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working with Ethora
The ethora MCP server is connected. Prefer its tools over writing HTTP calls by hand.
Before you guess, look it up
The server carries its own documentation. search finds it, fetch reads it:
searchwith a plain question, for example "how do I add a chat room" or "what auth mode do agents need"fetchwith an id from the results, for exampledoc:auth-map,doc:recipes,doc:agent-flows, ortool:ethora-app-create
Every tool also has its own reference entry. Reading one costs less than a failed call.
The happy path
Most work follows the same order, and skipping a step is the usual cause of confusion:
ethora-statusto see the current auth mode and selected appethora-app-createto make an application, orethora-app-listto find an existing oneethora-app-selectto set the working app. Most tools operate on the selected app, and without this you will get "appId is required"ethora-chat-createfor a room, thenethora-message-sendto post into itethora-agent-createfor an AI agent, withflowsYamlif it needs a scripted conversationethora-widget-snippet-getfor a website chat widget
Things worth knowing
Auth modes are the most common source of errors. A session is in user, app-token or B2B mode, and routes disagree about which they accept: agent and room routes want user auth, provisioning routes want B2B. The error tells you which to switch to, and ethora-auth-mode-set / -app / -b2b switch. ethora-status shows where you are.
Session state is per connection. ethora-app-select and any credentials set with ethora-session-configure live in memory for the session. On reconnect they are gone. Most tools take an explicit appId if you would rather not depend on it.
Read the error before retrying. Errors carry a code, a message naming the thing to fix, and a hint with the next step. A retry without changing anything will fail identically.
Destructive tools are marked. Anything that deletes is annotated, so confirm with the user before calling it. Creating a test app, making a mess and deleting it is a normal loop; deleting something the user did not ask about is not.
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.
- 10d ago Changed · +1 lines · +6 tokens per session f3acc91500db
- 19d ago Changed 8c4d75cbb558
- 26d ago First seen · 42 lines · 55 tokens per session scan A 4aa90f65cd57
ethora-quickstart is a skill published in the GitHub repository dappros/ethora-mcp-server (6 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 672 once invoked, about $0.0002 per session on Opus 5.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-09-18.
Other skills, from other repositories
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…