Borrowing it
Nothing to install: this file belongs to yuanchuan/aivo. 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/yuanchuan/aivo/main/CLAUDE.mdgit clone --depth 1 https://github.com/yuanchuan/aivoWrote 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/yuanchuan/aivo/claude-md)<a href="https://agentmods.dev/instructions/yuanchuan/aivo/claude-md"><img src="https://agentmods.dev/badge/instructions/yuanchuan/aivo/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.1 | $0.00767 | $0.00767 |
| Opus 5 | $0.00383 | $0.00383 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
aivo 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 8d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
aivo is a Rust CLI providing unified access to multiple AI coding assistants (Claude, Codex, Gemini, OpenCode, Pi) with local API key management. Supports OpenAI-compatible providers, GitHub Copilot, OpenRouter, Ollama, native APIs, and OAuth accounts.
Build & Test
cargo build # Debug build
cargo test --features __internal_test_fast_crypto # All tests (reduced PBKDF2 iterations)
cargo clippy && cargo fmt # Required clean before committing
- After code changes,
cargo build && cargo install --path . --debugbefore testing the binary — never test a stale build. - Tests are hermetic: a pre-main sandbox (
tests/support/mod.rs) points$HOMEattarget/.aivo-test-home/<pid>, so tests can never touch the real config.
Git & Release
- Squash merge to main; never commit unless asked.
- Release: bump version in
Cargo.toml, fmt/clippy/test, stage onlyCargo.toml+Cargo.lock+CHANGELOG.md(nevergit add -A), commitchore: release vX.Y.Z, push main, wait for CI green on all three runners (#[cfg(windows)]code is invisible to Linux/macOS clippy), then tag. Never tag before CI is green — a failed release can't be re-cut on the same tag.
Architecture
src/main.rs → src/commands/* (one module per subcommand: run, start, code, keys, serve, …) → src/services/* (key/session/stats stores, process launching, provider routers, wire-format bridges Anthropic ⇄ OpenAI ⇄ Gemini, OAuth flows).
Keys are AES-256-GCM encrypted in config.json under $AIVO_CONFIG_DIR (default ~/.config/aivo). Sentinel base_url values "copilot"/"ollama" mark special provider types. Exit codes: 0 success, 1 user error, 2 network, 3 auth.
Conventions
- Match existing CLI help text formatting exactly; verify interactive-UI edge cases (keyboard handling, empty input, single item, long strings).
- Comments: concise, why-only. Don't comment obvious code.
- Restate the question in fully concrete terms, making every implicit detail explicit. Then answer.
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.
- 8d ago First seen · 45 lines · 767 tokens per session scan A 501336045288
aivo CLAUDE.md is an instructions file published in the GitHub repository yuanchuan/aivo (192 stars, last pushed yesterday), licensed MIT. It adds 767 tokens to every session, about $0.0038 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.