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/ldclabs/anda-bot/agents-mdgit clone --depth 1 https://github.com/ldclabs/anda-botWhat 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.01246 | $0.01246 |
| Opus 5 | $0.00623 | $0.00623 |
| Sonnet 5 | $0.00249 | $0.00249 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
anda-bot 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 2d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for coding agents working in this repository. This file applies to the
entire tree unless a more specific AGENTS.md is added in a subdirectory.
Project Overview
Anda Bot is a local-first Rust AI agent with long-term memory, subagents, a TUI,
voice support, browser integration, cron automation, and IM channel runtimes.
The main binary is anda, implemented by the Rust package anda_bot.
The repository also contains:
chrome-extension/: Svelte + TypeScript Chrome Side Panel client.website/: SvelteKit marketing/support site.docsite/: Docusaurus documentation site with localized docs.skills/: runtime skill packages distributed with the project.scripts/: release/install helper scripts.
Development Rules
- Keep changes scoped to the subsystem requested. Avoid broad refactors unless they are necessary to make the requested behavior correct.
- Prefer existing project patterns over new abstractions. This codebase already has clear boundaries for config, daemon startup, engine tools, channels, transcription, TTS, cron, and the TUI.
- Do not commit secrets, tokens, generated local state, or user data. Runtime
state normally belongs under
~/.anda; repository examples must use placeholders. - When changing public behavior, update the relevant docs and examples. The
top-level
README.mdandREADME_cn.mdare paired and should stay in sync. - If user-facing docs under
docsite/docs/change, keep localized counterparts aligned where they already exist, especiallydocsite/i18n/zh-Hans/.... - Use
rgfor search and focused reads before editing. Do not assume module boundaries from filenames alone.
Rust Workspace
- Rust sources live under
anda_bot/src/; the workspace root isCargo.toml. - The package uses Rust edition 2024 and workspace-managed dependencies.
- Put shared dependency versions in the root
Cargo.toml, then reference them fromanda_bot/Cargo.toml. - The executable entrypoint is
anda_bot/src/main.rs; daemon lifecycle is inanda_bot/src/daemon.rs; config parsing lives underanda_bot/src/config/. - Engine-facing behavior is mostly under
anda_bot/src/engine/; IM channel behavior is underanda_bot/src/channel/; cron is underanda_bot/src/cron/. - Prefer typed structs,
serde/serde_saphyr, and existing request metadata helpers instead of ad hoc JSON/string parsing. - When adding persisted fields to DB-backed structs, check schema versions, indexes, compatibility defaults, and tests.
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.
- 2d ago First seen · 140 lines · 1,246 tokens per session scan A 50d6094026c3
anda-bot AGENTS.md is an instructions file published in the GitHub repository ldclabs/anda-bot (23 stars, last pushed 25d ago), licensed Apache-2.0. It adds 1,246 tokens to every session, about $0.0062 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
Browser4 CLAUDE.md
Instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
spring-ai-agentcore AGENTS.md
Instructions for spring-ai-community/spring-ai-agentcore, covering agents.md, project overview, architecture, key components and artifact store classes.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
deckforge AGENTS.md
Instructions for tph-kds/deckforge, covering deckforge agent entry point, code intelligence, read order, default routing and non-negotiable implementation rules.
fast-browser CLAUDE.md
Claude Code instructions for m4ttstack/fast-browser, covering fast browser plugin, where a change belongs, fork branch: use fast-browser-runtime, releasing a new runtime and re-pinning this repo: use the script.
agentoscope AGENTS.md
Instructions for rafaelcg/agentoscope, covering agentoscope — agent instructions, what this is, layout, commands and conventions.