Borrowing it
Nothing to install: this file belongs to ric03uec/clawrium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ric03uec/clawrium/main/AGENTS.mdgit clone --depth 1 https://github.com/ric03uec/clawriumWrote 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/instructions/ric03uec/clawrium/agents-md)<a href="https://agentmods.dev/instructions/ric03uec/clawrium/agents-md"><img src="https://agentmods.dev/badge/instructions/ric03uec/clawrium/agents-md/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/instructions/ric03uec/clawrium/agents-md"><img src="https://agentmods.dev/badge/instructions/ric03uec/clawrium/agents-md.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.09360 | $0.09360 |
| Opus 5.5 | $0.03744 | $0.03744 |
| Sonnet 5.5 | $0.01872 | $0.01872 |
| Haiku 4.5 | $0.00936 | $0.00936 |
Grade A, and why
clawrium AGENTS.md 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 24d 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 — 774 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clawrium
How It Works
Clawrium is a CLI tool (clawctl) that manages AI agent fleets across your local network. Point it at any machine, and it handles deployment, configuration, and lifecycle management via SSH and Ansible.
Your Machine (clawctl CLI)
│
├── Host A ──> zeroclaw instance
├── Host B ──> openclaw instance
└── Host C ──> nemoclaw instance, zeroclaw instance
Why
- Single pane of glass: Manage all agents from one CLI instead of SSH-ing to each host
- Consistent lifecycle: Same commands for install, configure, start, stop, remove across all agent types
- Secrets management: Secure API key storage with per-agent isolation
- Fleet visibility:
clawctl agent getshows status of all agents across all hosts
Who Is This For
- Homelabbers: Run multiple AI assistants on spare hardware
- Teams: Standardize agent deployment across developer machines
- Experimenters: Try different models/agents without manual setup on each host
Quickstart
# Install
uv tool install clawrium
# Add a host (see docs/host-preparation.md for the xclm setup commands)
clawctl host create 192.168.1.100 --user xclm --alias mybox
# Install an agent
clawctl agent create <agent-name> --type openclaw --host mybox
# Configure and start
clawctl agent configure <agent-name>
clawctl agent start <agent-name>
# Run a command against the agent's native CLI on its host
clawctl agent exec <agent-name> -- --version
# Install a skill onto the agent (catalog: skills/)
clawctl skill registry get
clawctl skill registry describe clawrium/tdd # Inspect a skill before installing
clawctl agent skill add <agent-name> --from-template clawrium/tdd
clawctl agent sync <agent-name>
# Check fleet status
clawctl agent get
Installation Source of Truth
Install instructions live in docs/installation.md. This is the canonical source — when updating install steps:
- Edit
docs/installation.mdfirst. - Mirror the body verbatim to
website/docs/installation.md. Keep the Docusaurus frontmatter and the mirror-warning HTML comment at the top of that file; everything below them must matchdocs/installation.mdexactly. - The README's install section is intentionally brief (just the two
uv tool install/uvxcommands). Only update it if those commands change.
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.
- 24d ago Changed 7003279dd684
- 1mo ago Changed · +28 lines · +455 tokens per session e1c18a60dfe0
- 1mo ago Changed · -10 tokens per session 8a0a1f263adf
- 2mo ago First seen · 746 lines · 8,915 tokens per session scan A c322a70c9574
clawrium AGENTS.md is an instructions file published in the GitHub repository ric03uec/clawrium (67 stars, last pushed 13d ago), licensed Apache-2.0. It adds 9,360 tokens to every session, about $0.0374 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.