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 instructions/mezmo/aura/claude-mdgit clone --depth 1 https://github.com/mezmo/auraWrote 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/mezmo/aura/claude-md)<a href="https://agentmods.dev/instructions/mezmo/aura/claude-md"><img src="https://agentmods.dev/badge/instructions/mezmo/aura/claude-md.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.05043 | $0.05043 |
| Opus 5 | $0.02521 | $0.02521 |
| Sonnet 5 | $0.01009 | $0.01009 |
| Haiku 4.5 | $0.00504 | $0.00504 |
Grade A, and why
aura CLAUDE.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 4d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Project Documentation
If
CLAUDE.local.mdexists in this directory, read it first — it contains current session state.
Overview
AURA is a TOML-based configuration system for composing Rig.rs AI agents with MCP tools and RAG pipelines.
Current Status: Production Ready
All major features complete:
- Bounded streaming with custom aura events
- Rig 0.28 upgrade with ProviderAgent architecture
- Configurable MCP header forwarding (
headers_from_requestwith static TOML fallback) - Request-scoped MCP progress and cancellation
- Client disconnect detection with MCP
notifications/cancelled - Multi-agent orchestration mode with coordinator/worker architecture and DAG execution
Pending: Upstream Rig PRs - StreamingPromptHook fix + Content-Type header fix
Quick Start
# Build
cargo build --release
# Start web server (default config.toml)
cargo run --bin aura -- webserver
# Start with orchestration config
CONFIG_PATH=configs/example-math-orchestration.toml AURA_CUSTOM_EVENTS=true cargo run --bin aura -- webserver
# Build and run CLI (HTTP mode — connects to a running `aura webserver`)
cargo run -p aura-cli -- --api-url http://localhost:8080
# Build and run CLI (standalone mode — no server needed, default when --api-url absent)
cargo run -p aura-cli -- --config configs/my-agent.toml
# Run integration tests (local, requires Docker)
make test-integration-local # base integration
make test-integration-orchestration-local # orchestration integration
make test-integration-sre-orchestration-local # SRE orchestration integration
Project Structure
aura/
├── crates/
│ ├── aura/ # Core library (agent builder + orchestration)
│ ├── aura-cli/ # The `aura` binary: interactive client + `webserver` mode
│ ├── aura-config/ # TOML parsing and configuration
│ ├── aura-events/ # Shared SSE event types (lightweight, no agent deps)
│ ├── aura-web-server/ # OpenAI-compatible API + shared server entry point
│ └── aura-test-utils/ # Shared testing utilities
├── compose/ # Docker Compose (integration + orchestration overlays)
├── configs/ # Integration test and example configurations
├── deployment/ # Helm charts and K8s manifests
├── docs/ # Architecture and protocol documentation
├── examples/ # Example and reference configurations
└── .makefiles/ # Modular Make targets (rust, docker, node, aura)
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.
- 4d ago First seen · 262 lines · 5,043 tokens per session scan A 4af8c07c9744
aura CLAUDE.md is an instructions file published in the GitHub repository mezmo/aura (284 stars, last pushed today), licensed Apache-2.0. It adds 5,043 tokens to every session, about $0.0252 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 instructions, from other repositories
ii-agent CLAUDE.md
Instructions for Intelligent-Internet/ii-agent, covering ii-agent project guide, project overview, architecture, domain structure and orm base & id conventions.
ii-agent AGENTS.md
Instructions for Intelligent-Internet/ii-agent, covering ii-agent contributor guide, quick start, repository map, mandatory rules and architecture.
siclaw CLAUDE.md
Instructions for scitix/siclaw, covering siclaw — operating manual for claude, what this project is, critical architecture invariants, 🔴 local mode: shared filesystem and 🔴 skill bundle contract.
siclaw AGENTS.md
Instructions for scitix/siclaw, covering siclaw project instructions, project shape, before risky edits, verification and stable boundaries.
ai-dial-core CLAUDE.md
Claude Code instructions for epam/ai-dial-core, covering claude.md, build & run, set credentials via environment variables, build (skip tests) and run all tests.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.