ZeroClaw is a Rust-based runtime for running a personal AI assistant on a user's own machine, with connections to language-model providers, communication channels, and external tools. It is for people who want to operate an assistant across channels such as Discord, Telegram, email, voice, webhooks, or a command line while keeping control of its data and credentials. The catalogue add-ons provide workflows and agents for using ZeroClaw.
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 agents/zeroclaw-labs/zeroclaw/overviewgit clone --depth 1 https://github.com/zeroclaw-labs/zeroclawWrote 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/agents/zeroclaw-labs/zeroclaw/overview)<a href="https://agentmods.dev/agents/zeroclaw-labs/zeroclaw/overview"><img src="https://agentmods.dev/badge/agents/zeroclaw-labs/zeroclaw/overview.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 | $0.00000 | $0.01004 |
| Opus 5 | $0.00000 | $0.00502 |
| Sonnet 5 | $0.00000 | $0.00201 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
overview 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 5d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents
Agents are the star of a ZeroClaw deployment. Everything else in this book, the providers, the channels, the security profiles, the skills, the memory, exists so that an agent can use it. This section is the showcase; the rest of the docs are the credits.
{{#include ../_snippets/concept-multi-agent.md}}
An agent is a join
An agent is not a program you install. It is a named row, [agents.<alias>],
that joins two halves:
- Config references (the relational side): pointers to things configured elsewhere, a model provider, a risk profile, a runtime profile, channels, skill / knowledge / MCP bundles, cron jobs. Each is a dotted alias. The agent owns none of these; it points at them, and many agents can point at the same one or diverge freely.
- Filesystem components (the on-disk side): a per-agent workspace directory, a memory backend, and an identity (personality) source. This is where the relational graph meets a concrete directory tree.
Config references (relational) Filesystem (on-disk)
────────────────────────────── ──────────────────────
- model provider - workspace/
- risk profile - memory store
- runtime profile agents.<alias> - identity / personality
- channels ──▶ (the join) ◀──
- peer groups
- skill / knowledge / MCP bundles
- cron jobs
The agent points at the references on the left, owning none of them: many agents may share one or diverge freely. It owns the filesystem half on the right.
Each reference is a link back to its own section, the credits: model providers live in Model Providers, the profiles in Security & Autonomy, channels in Channels, peer groups in Peer Groups, bundles in Tools.
Multi-agent from the jump
There is no privileged "the agent." The runtime holds a map of agents keyed by alias; a single-agent install is just a map of size one. You do not start with one bot and bolt on more later, you add agents and wire each one, and they coexist from the first line of config.
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.
- 5d ago First seen · 91 lines · 0 tokens per session scan A f409b1524750
overview is an agent published in the GitHub repository zeroclaw-labs/zeroclaw (32,731 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,004 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 agents, from other repositories
comparator
Compare two outputs WITHOUT knowing which skill produced them.
implementer
Milestone executor. Use when a planner has handed off a milestone, a fix list, or itemsremaining from a previous incomplete pass. Codes, tests, repairs. Returns what's done, what's remaining, and a completion score. Never replans, never judges.
planner
Planning agent. Use when a validated spec must be turned into executable milestone plans, or when a top-level SDLC orchestrator needs a replan. Writes plans and decisions only. Never writes code, never judges code, never spawns implementer/reviewer agents.
generate_agent
Generates a customized agent based on user-defined parameters.
Explore
Fast read-only codebase & docs exploration. Returns structured findings, never raw file dumps.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.